AI AGENTS
Intercom SLA-Miss Auto-Reply with Tiered Remediation
When an Intercom conversation passes its response-time target, an agent classifies sentiment, picks a remediation tier.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom response-SLA eventIntercom
- ActionFetch transcript + contact attributesIntercom
- ActionAgent scores sentiment + picks tier
- LogicRoute high-anger threads to human handoff
- ActionPost tiered offer reply in conversationIntercom
- OutputTag conversation with tier + reasoningIntercom
What it does
Monitors Intercom for conversations that miss their target response time and responds proactively. The agent gauges how frustrated the customer is from the thread, chooses a remediation tier (acknowledgment, small credit, or escalation to a human specialist), and replies in-conversation — tagging the thread so leads can audit what was offered.
When to use it
Use it for live-chat support where a slow reply is itself the breach and an immediate, sentiment-aware acknowledgment beats a delayed perfect one. Best when you trust the agent to send low-tier offers unattended and only escalate the angry cases.
How it works
- 1An Intercom conversation-SLA event triggers the flow.
- 2The flow pulls the conversation transcript and contact attributes.
- 3The agent scores sentiment and maps it to a remediation tier.
- 4A branch routes high-anger threads to a human-handoff path instead of auto-replying.
- 5For the rest, the agent posts the tiered offer as a reply in Intercom.
- 6It applies a tag recording the tier and reasoning for later review.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.