TeamsWork Community

We’re glad you’re here.

This space is for TeamsWork users to discuss the product, ask questions, report bugs, share feature requests, and exchange tips and best practices for using TeamsWork apps inside Microsoft Teams.

Whether you’re looking to improve a workflow, suggest a new idea, or clarify something about how the product works, this is the place to start the conversation. We encourage open discussions and real experiences from users across different teams and roles.

You can now start a dedicated Teams chat directly from any sales record in CRM as a Service. Add your teammates as chat participants, start the chat, and it appears in Teams as a thread dedicated to that opportunity. No switching between apps — replies from Teams and from the CRM both land in the same thread in real time.

Has anyone had a chance to try it yet? Would love to hear what you think!

If your team uses CRM as a Service for RFQs, feasibility checks, and post-sales support, here are a few ways to get more from it inside Microsoft Teams. Especially in manufacturing, where one customer journey often involves sales, operations, internal review, and after-sales follow-up, a few setup decisions can make a big difference in how smoothly the process runs.

• Set up pipeline stages to match your actual sales flow

  Manufacturing deals often move through inquiry, qualification, feasibility review, proposal, negotiation, and handover. Reflecting that directly in your pipeline makes it easier for everyone to track progress and manage handoffs.

  

• Use the same customer record for both sales and post-sales

  If your team handles warranty claims, service requests, or follow-ups after the deal closes, keeping them tied to the same customer record helps preserve the full history in one place.

Hi everyone! Fast response time doesn’t just happen by chance. It usually comes from using the right features intentionally. Here are several Ticketing as a Service capabilities that can help your team keep requests moving and avoid unnecessary delays.

SLA Tracking

Response targets can be clearly defined through SLA rules. Ticketing as a Service automatically tracks both First Response Time and Resolution Time, calculating deadlines based on working hours. This helps teams quickly see which tickets need attention, so response targets are easier to meet.

SLA Notifications and Escalation

When a ticket is approaching its SLA deadline, the system can notify the team so it can be handled before the target is missed. If an SLA is breached, escalation rules can alert specific team members to step in quickly and resolve the issue.

Priority and Categorization