AI AGENTS
Low-CSAT Intercom ticket triggers a recovery callback script
When an Intercom conversation closes with a low CSAT rating, an agent generates an empathetic spoken apology-and-recovery voicemail with ElevenLabs and logs it to a Postgres…
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation closed with CSAT ratingIntercom
- LogicKeep only ratings at/below detractor threshold
- ActionAgent drafts empathetic recovery script from complaint
- ActionRender apology script to audioElevenLabs
- ActionInsert callback row into Postgres queue (pending)Postgres
- OutputPending callback available for agent/dialerPostgres
What it does
Catches unhappy customers the moment a low satisfaction score lands in Intercom, then produces a tailored spoken recovery message and schedules a human callback. It pairs the audio with the original complaint so the agent dialing has full context.
When to use it
When you want service recovery on detractor ratings to be fast and consistent — every low CSAT becomes a tracked callback with a ready apology script, instead of getting buried in the inbox.
How it works
- 1An Intercom conversation closes and a CSAT rating is recorded.
- 2A logic step filters to ratings at or below your detractor threshold.
- 3The agent reads the conversation and the rating reason, then writes an empathetic recovery script.
- 4ElevenLabs renders it to audio in a calm, sincere voice.
- 5The script, audio URL, and customer contact are inserted into a Postgres callback_queue table with status pending.
- 6The pending callback row is the output for agents or a dialer to pick up.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect ElevenLabsText-to-speech, voice cloning.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.