Overview

Freshdesk serves 60,000+ businesses and is the go-to helpdesk for budget-conscious teams that need serious multi-channel support without enterprise pricing. What makes it technically unique is something most Freshdesk integrations completely ignore: native SLA breach flags baked directly into every ticket. This MCP reads Freshdesk's actual policy-driven breach signals — fr_escalated for first response and is_escalated for resolution — and builds a full ops intelligence layer on top. No guessing. No "hasn't been updated in 24 hours" heuristics. Real breach data from your real SLA policies. Every write operation is dry-run by default. Execution requires an explicit confirm. This is built for teams that want AI assistance without handing over unchecked write access to their live helpdesk.

Key Capabilities

• Native SLA breach detection — reads Freshdesk's built-in fr_escalated and is_escalated policy flags directly from the ticket object. First response and resolution breaches are flagged with policy accuracy, not estimates. This is a technical advantage no other Freshdesk MCP offers.
• Dry-run ticket writes with confirm gate — preview status changes, priority updates, tag edits, assignee moves, and custom field updates as a clean diff before anything is applied. Execution requires confirm: true. AI cannot make unreviewed changes to live tickets.
• Multi-channel analytics — weekly digest breaks down ticket volume by channel: email, chat, phone, portal, WhatsApp, and ecommerce. Understand where your load is coming from before you staff for it.
• Canned response authoring — write a response in plain English, preview it formatted and structured, then create it across your folder library. No UI clicking, no copy-paste into the editor.
• Contact intelligence — look up any contact by email or ID to see all channels, company association, and custom fields before deciding how to handle their ticket.
• Weekly manager digest — one command generates a Monday-ready summary covering ticket volume, open and pending queue depth, priority breakdown, channel distribution, top tags, native SLA breach counts, and CSAT where your plan supports it.

Use Cases

Morning SLA sweep — run list_sla_breaches with breach_type: both to surface every ticket with a breached first response or resolution SLA. Ranked by priority, filtered by group. Work the list top-down. Per-ticket SLA investigation — use explain_ticket_sla for a complete picture: what the SLA policy targets, whether they've been breached, actual first reply time from conversation history, time remaining until deadline, and a plain-language risk verdict. Safe ticket operations — preview changes across multiple tickets with preview_ticket_update, review the diff line by line, then apply with execute_ticket_update confirm:true. No accidental overwrites. Canned response library management — browse the full library with list_canned_responses, fetch any response's HTML and plain text with get_canned_response, and create new ones from plain text specs with create_canned_response. Leadership reporting without Analytics — run weekly_support_summary for a paste-ready digest that covers everything a support manager needs on Monday morning, including actual SLA breach counts from native Freshdesk policy flags.

Who This Is For

Growing support teams on Freshdesk Growth, Pro, or Enterprise plans who want AI-assisted ops without losing control of what changes in their instance. Support managers who need breach radar without building Freshdesk Analytics dashboards. Senior agents maintaining canned response libraries across multiple folders. Team leads preparing weekly reports for leadership. Operations-minded teams running multi-channel support across email, chat, phone, and social who need channel visibility in their reporting.

This is not a read-only ticket search wrapper. It is a governed ops layer for teams where SLA accuracy matters and every write to a live ticket should be intentional.