[object Object]

Slack and MS Teams integrations for Freshdesk and Freshservice ship as marketplace apps. Most teams install, get a flood of notifications, and mute the channel within a week. The fix is curation, not volume.

Notify on signal, not state change

A new ticket assigned is a signal. A field update on the same ticket is noise. Configure your integration to fire only on:

  • New ticket in priority bucket
  • SLA at 50% and 90%
  • Reply from VIP customer
  • Status change to Resolved or Reopened

One channel per workflow, not per product

A single #freshdesk channel becomes a graveyard. Split into #support-vip, #support-sla-risk, #support-resolutions-celebration. The signal density per channel is what makes them readable.

Two-way actions from chat

Both Slack and Teams integrations support inline actions: reply, change status, assign. Train agents to use these for quick acknowledgment. Saves a context switch.

Slack message thread:
  /freshdesk reply 4421 "Thanks, looking into this now"
  /freshdesk status 4421 in_progress
  /freshdesk assign 4421 @jane

Approvals in Teams adaptive cards

Freshservice change approvals in Teams render as adaptive cards. The approver clicks Approve or Reject without leaving Teams. The change record updates with the approval action and the Teams user identity.

Channel-to-ticket conversion

A Slack thread can become a Freshdesk ticket via /freshdesk create. Useful when a customer-facing conversation lands in your internal channel and needs official tracking.

OAuth and SSO

Both integrations support SSO. Map Slack/Teams identities to Freshworks agents at install time. Without this mapping, inline actions fail with “user not found.”

// User mapping config
{
  "slack_user": "U045GH2Z1",
  "freshdesk_agent_id": 9921,
  "freshdesk_email": "[email protected]"
}

What to do this week

Audit which events fire to each channel, split into purpose-specific channels, train agents on inline action commands, and verify the SSO user mapping completeness.

[object Object]
Share