Every Intercom Release in July 2026: The Complete List
All 25 Intercom releases from July 2026, dated and grouped by product area, with a note on which ones actually need you to change a setting.
— thoughts and learnings —
Tagged: Support Ops
What's New in Intercom: The Releases Worth Changing Your Settings For
Ongoing coverage of Intercom releases, filtered down to the ones that change how work reaches your team. Currently covering summer 2026, with the settings worth changing and the numbers to start from.
How to Turn a Customer Support Dashboard Into a Weekly Operating System
Use a weekly operating loop—detect, investigate, decide, assign, and verify—to turn customer support metrics into measurable improvement.
Seven Metrics Every Customer Support Dashboard Should Show
Build a balanced support dashboard with volume, responsiveness, resolution, surveyed CSAT, response rate, satisfaction coverage, QA, and DSAT.
How to handle off-policy requests in Intercom without losing context
When a customer asks for something outside policy, the worst outcomes come from agents deciding alone. Here is how to escalate from inside the Intercom inbox without losing the thread.
How to create an audit trail for customer support decisions
A support decision audit trail means every approval, rejection, and reason is stored somewhere retrievable - not in someone's memory, and not in a Slack DM archive. Here is what to capture and how to build one that finance can use.
How to build a refund approval workflow for your support team
A refund approval workflow routes exception requests to a manager, captures the reason, and stores the record. Here is how to define your threshold, set up the request path, and keep a log finance can use.
Why "use your judgment" is not a refund policy
"Use your judgment" sounds like empowerment but produces inconsistent refunds, anxious agents, and customers who get different answers depending on who they reach. A real policy needs a threshold, an exception path, and a record.
The hidden cost of the shoulder-tap — how informal support approvals hurt teams
The shoulder-tap approval — a quick DM, a verbal yes — feels fast and trustworthy. Measured across a team over months, it is a slow leak of manager time, inconsistent decisions, and records that do not exist.
Why customer support teams need an approval process (and most don't have one)
Most support teams have no formal approval process — refund decisions, credits, and exceptions happen via DM with no record. Here is what a proper workflow needs and how to build one.
The Anatomy of a Useful Weekly Customer Support Report
Design a weekly report that shows volume, responsiveness, ratings, quality, context, and the one decision your support team should make next.
Team Report or Agent Report? Why Support Leaders Need Both
Team reports diagnose systems. Agent reports support individual development. Learn how to use both without turning support metrics into an unfair ranking.
Why Your Support Team Needs a Weekly Quality Review
Weekly support reporting creates a short feedback loop without overreacting to individual tickets. Learn what to review and how to turn it into action.
DSAT Is an Operations Signal, Not Just an Agent Score
Learn how to classify DSAT by agent, product, policy, process, tooling, and customer factors—then turn negative ratings into measurable fixes.
What to Do When a Customer Leaves a Negative CSAT Rating
A practical DSAT recovery workflow: detect the rating, review context, acknowledge impact, take ownership, resolve the issue, and capture the root cause.
How to Build a Customer Support QA Rubric Agents Can Actually Use
Create a fair, specific customer-support QA rubric with weighted attributes, observable criteria, real examples, and a repeatable calibration process.