FreshService + Microsoft Teams
Connect FreshService and Microsoft Teams to Speed Up IT Support
Automate ticket notifications, approvals, and incident alerts between your ITSM platform and where your team actually talks.
Why integrate FreshService and Microsoft Teams?
FreshService handles your ticketing, asset management, and change requests. Microsoft Teams is where your workforce spends most of its day. When these two platforms don't talk to each other, IT teams burn time switching between tools, chasing approvals manually, and relaying ticket updates by hand. Integrating FreshService with Microsoft Teams pulls ITSM workflows directly into the conversations where work is already happening.
Automate & integrate FreshService & Microsoft Teams
Use case
Real-Time Ticket Notifications in Teams Channels
Whenever a new ticket is created in FreshService, an automated message is posted to the appropriate Microsoft Teams channel, including ticket ID, priority, category, and the requester's name. Support agents can acknowledge the ticket and claim ownership directly from Teams without logging into FreshService. This cuts the lag between ticket submission and agent response, helping teams meet SLA targets consistently.
Use case
Major Incident Escalation and War Room Coordination
When a FreshService incident is raised or escalated to critical priority, tray.ai can automatically create a dedicated Microsoft Teams channel or meeting, notify the relevant stakeholders, and post a real-time incident summary. As the incident status updates in FreshService, the Teams channel gets live updates, keeping all responders on the same page. This shortens mean time to resolution (MTTR) by centralizing communication around the incident.
Use case
Change Request Approvals via Teams
Change requests submitted in FreshService can trigger interactive approval cards sent directly to designated approvers in Microsoft Teams. Approvers get all the relevant details — risk level, implementation plan, rollback procedure — and can approve or reject with a single click inside Teams. The decision is automatically written back to FreshService, updating the change request status without any manual data entry.
Use case
SLA Breach Alerts and Escalation Notifications
When a FreshService ticket is approaching or has breached its SLA deadline, tray.ai sends an urgent, formatted alert to the responsible agent and their team manager in Microsoft Teams. The notification includes ticket details, time since SLA breach, and a direct link to the ticket in FreshService. This gives IT teams a chance to course-correct before customer satisfaction takes a hit.
Use case
Employee Onboarding and Offboarding Ticket Tracking
When HR initiates an onboarding or offboarding workflow that generates a service request in FreshService, tray.ai posts a structured update to the IT operations Teams channel, tracking each sub-task's completion status in real time. Team leads get a daily summary card in Teams covering pending, in-progress, and completed onboarding tasks. Nothing falls through the cracks during high-volume onboarding periods.
Use case
Automated Daily IT Operations Digests
At a scheduled time each day, tray.ai queries FreshService for open tickets, pending change requests, and active incidents, then compiles a formatted digest card and posts it to the IT leadership channel in Microsoft Teams. The digest calls out overdue items, unassigned tickets, and tickets nearing SLA deadlines — giving IT managers an operational pulse without manual report generation.
Use case
End-User Ticket Status Updates via Teams Direct Message
When a FreshService ticket status changes — from open to in-progress, pending, or resolved — tray.ai sends an automatic direct message to the requesting user in Microsoft Teams, keeping them informed at every stage. The message includes the current status, the assigned agent's name, and an estimated resolution time if available. This cuts down on inbound 'status check' tickets and follow-up calls to the help desk.
Get started with FreshService & Microsoft Teams integration today
FreshService & Microsoft Teams Challenges
What challenges are there when working with FreshService & Microsoft Teams and how will using Tray.ai help?
Challenge
Mapping FreshService Users to Microsoft Teams Identities
FreshService tracks users by email and internal agent IDs, while Microsoft Teams uses Azure Active Directory object IDs. Without a reliable mapping layer, notifications and direct messages can fail silently or land with the wrong person — especially in organizations with complex email alias structures or shared service accounts.
How Tray.ai Can Help:
tray.ai's data transformation and lookup capabilities let you query the Microsoft Graph API to resolve a FreshService requester's email address to their Teams user ID in real time, so every notification and direct message reaches the right person regardless of alias or display name discrepancies.
Challenge
Handling High-Volume Ticket Environments Without Teams Noise
Large IT organizations can generate hundreds of tickets per day in FreshService. Pushing every ticket update to Microsoft Teams without intelligent filtering leads to notification fatigue — agents start ignoring messages, and the integration stops doing its job.
How Tray.ai Can Help:
tray.ai workflows support conditional branching and filter logic, so you can define precise rules — for example, only notifying Teams for Priority 1 and Priority 2 tickets, tickets in specific categories, or tickets assigned to particular groups. Teams channels get only the high-signal, actionable notifications worth acting on.
Challenge
Bi-Directional Data Sync and Write-Back to FreshService
Capturing approvals, comments, or status changes made in Microsoft Teams and writing them back accurately to FreshService is genuinely tricky. Teams interactions happen asynchronously, and without a structured integration layer, responses can be lost, duplicated, or fail to update the correct FreshService record.
How Tray.ai Can Help:
tray.ai handles asynchronous webhook responses from Microsoft Teams and maps them back to the originating FreshService record using stored correlation IDs. Built-in error handling and retry logic means approval responses and comments are reliably persisted in FreshService even during intermittent API failures.
Challenge
Keeping Integration Workflows in Sync with FreshService Schema Changes
FreshService lets administrators create custom ticket fields, custom statuses, and service catalog items that change over time. When that happens, hardcoded integration workflows can break silently, causing missed notifications or malformed Teams messages.
How Tray.ai Can Help:
tray.ai's visual workflow builder makes it straightforward to update data mappings when FreshService custom fields change, without rewriting code. Teams across the organization can manage and iterate on integration logic through a no-code interface, and workflow versioning means changes can be tested and rolled back safely.
Challenge
Managing Microsoft Teams Rate Limits and Throttling
Microsoft Teams and the underlying Graph API enforce rate limits on messaging, channel creation, and user lookups. In high-volume scenarios — like a major incident triggering dozens of simultaneous notifications — workflows can hit these limits and fail to deliver critical messages at exactly the moment they're needed most.
How Tray.ai Can Help:
tray.ai's workflow engine has built-in rate limit awareness and automatic retry with exponential backoff, so Teams API calls are queued and retried intelligently during throttling events. All notifications and messages get delivered, without manual intervention or custom error-handling code.
Start using our pre-built FreshService & Microsoft Teams templates today
Start from scratch or use one of our pre-built FreshService & Microsoft Teams templates to quickly solve your most common use cases.
FreshService & Microsoft Teams Templates
Find pre-built FreshService & Microsoft Teams solutions for common use cases
Template
New FreshService Ticket → Microsoft Teams Channel Notification
This template monitors FreshService for newly created tickets and immediately posts a formatted notification card to a designated Microsoft Teams channel. The card includes the ticket ID, subject, priority, category, requester, and a direct link to open the ticket in FreshService.
Steps:
- Trigger: New ticket is created in FreshService via webhook or polling
- Transform: Map ticket fields (ID, priority, subject, requester, category) into a Teams Adaptive Card payload
- Action: Post the formatted Adaptive Card to the specified Microsoft Teams channel
Connectors Used: FreshService, Microsoft Teams
Template
FreshService Critical Incident → Teams War Room Channel Creator
When a FreshService incident is escalated to Critical or Urgent priority, this template automatically creates a dedicated Microsoft Teams channel, invites the relevant IT responders, and posts the full incident details as a pinned message to kick off the response.
Steps:
- Trigger: FreshService incident status changes to Critical or priority set to Urgent
- Action: Create a new Microsoft Teams channel named with the incident ID and title
- Action: Add designated incident responders to the new channel and post incident summary as a pinned message
Connectors Used: FreshService, Microsoft Teams
Template
FreshService Change Request → Teams Approval Card Workflow
This template sends an interactive Adaptive Card to the designated change approver in Microsoft Teams when a FreshService change request moves to Pending Approval. The approver can approve or reject directly in Teams, and the response is written back to FreshService automatically.
Steps:
- Trigger: FreshService change request status changes to Pending Approval
- Action: Send an interactive Adaptive Card to the approver in Microsoft Teams with approve/reject buttons and full change details
- Action: Capture the approver's response and update the FreshService change request status and approval notes accordingly
Connectors Used: FreshService, Microsoft Teams
Template
FreshService SLA Breach Alert → Teams Direct Message to Agent and Manager
This template runs on a scheduled interval, checks FreshService for tickets that have breached or are within a configurable threshold of breaching their SLA, and sends urgent direct messages to both the assigned agent and their manager in Microsoft Teams with ticket details and a direct link.
Steps:
- Trigger: Scheduled tray.ai workflow runs at a defined interval (e.g., every 15 minutes)
- Process: Query FreshService for tickets breaching or near-breaching SLA thresholds and filter results
- Action: Send personalized direct messages to the assigned agent and team manager in Microsoft Teams with breach details and ticket deep links
Connectors Used: FreshService, Microsoft Teams
Template
FreshService Ticket Status Update → Teams Direct Message to Requester
Each time a FreshService ticket changes status, this template looks up the requesting employee's Microsoft Teams user profile and sends them a personalized direct message summarizing the update, the assigned agent, and next steps — so end users stay informed without any manual communication from the IT team.
Steps:
- Trigger: FreshService ticket status field is updated (e.g., Open → In Progress, In Progress → Resolved)
- Action: Look up the requester's Microsoft Teams user ID using their email address
- Action: Send a personalized direct message to the requester in Teams with the new status, assigned agent, and resolution details
Connectors Used: FreshService, Microsoft Teams
Template
Scheduled FreshService Daily Digest → Teams IT Operations Channel
This template runs every morning and queries FreshService for all open tickets, active incidents, pending changes, and SLA-at-risk items. It compiles the data into a structured Adaptive Card digest and posts it to the IT operations Microsoft Teams channel so the day starts with a clear picture of what needs attention.
Steps:
- Trigger: Scheduled trigger fires each morning at a defined time (e.g., 8:00 AM local time)
- Process: Query FreshService API for open tickets, active incidents, pending change requests, and SLA-breached items; aggregate counts and details
- Action: Format results into a rich Adaptive Card and post the daily digest to the designated Microsoft Teams IT operations channel
Connectors Used: FreshService, Microsoft Teams