Connect to IntercomSupport team exception management.
Every support team has exceptions. Most teams have no system for them.
Refunds, credits, comps, off-policy replies — judgment calls outside standard policy need a path, a record, and a reason. Supportman Approvals gives exceptions structure.
Free trial · Approvals in limited beta · See pricing
Any decision outside standard policy.
Exception management covers every judgment call that needs sign-off before an agent can proceed — not just refunds, but credits, comps, off-policy replies, escalations, and special offers.
More on the framework in why support teams need an approval process
Exceptions without structure do not scale.
Informal exception handling works when the team is small and the manager is always online. It breaks the moment volume grows or someone asks for the record.
✕ No consistency
One manager says yes, another says no — same situation, no shared criteria. Agents learn to ask whoever gives the answer they want.
✕ No record
Exceptions live in DMs and memory. When leadership asks how many off-policy credits you issued last quarter, nobody has a number.
✕ Managers interrupted
Shoulder-taps and Slack pings pull managers out of focus work. Every exception is urgent to the agent, invisible to the queue.
✕ Agents uncertain
Without a clear path, agents either over-escalate or make calls they should not. Both erode trust with customers and leadership.
Request. Decide. Document.
A workable exception system has three parts: a way for agents to request, a way for managers to decide with context, and a record of every outcome.
Module:
Request type
Details
Approval request from Sara — Refund
⏳ Refund
Requested by:
Sara
Requested:
Today at 2:14 PM
Details:
$50. Item arrived with damaged packaging
Module:
Refund
✓ Approved · Today at 2:15 PM
$50. Item arrived with damaged packaging
Agent flags the exception.
Refund above policy, off-policy reply, comp for a service failure — pick the type, add context, submit from the conversation.
Manager decides with reason.
Structured post with Approve and Deny actions. Required comment documents why this exception was granted or declined.
Exception logged.
Outcome back in Intercom. Channel history and CSV export when you need to report on exceptions over time.
Request from inbox
Agent submits from the Supportman panel in Intercom — type, context, customer situation. No DM, no summarising from memory.
Decide in Slack
Manager approves or denies in #intercom-approvals with a required comment. Full context in the message, not buried in a thread.
Stored record
Every exception on the channel log and back on the conversation. Export CSV when finance or compliance needs the trail.
Questions about managing exceptions.
What is exception management in customer support?
Exception management is how a support team handles decisions outside standard policy — refunds above threshold, credits, comps, off-policy replies, escalations, special offers. Any judgment call that needs sign-off before the agent can proceed.
How do you manage support exceptions?
Give exceptions a consistent path: agent submits a structured request with context, manager approves or denies with a required reason, decision stored where both sides can find it. Ad-hoc DMs and shoulder-taps do not scale — a dedicated workflow does.
What tools help with support exception workflows?
For Intercom and Slack teams, Supportman Approvals routes exception requests from the inbox to #intercom-approvals. Managers decide in Slack with full context. Outcomes flow back to the conversation and stay exportable for audit.
Give exceptions a system.
Connect Intercom and Slack. Enable Approvals. Every exception request structured, every decision on record.
Supportman is an independent product — not made by or affiliated with Intercom or Slack.