CUSTOMER SUPPORT
Intercom repro completeness check with escalating follow-up loop
Scores inbound Intercom bug conversations for reproduction completeness and runs a timed follow-up loop.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Intercom bug conversationIntercom
- ActionScore repro completeness, list gaps (LLM)OpenAI
- LogicBranch: complete enough to hand off?
- ActionAsk for missing fields, tag awaiting-reproIntercom
- LogicScheduled re-check: reminder, then close stale
- OutputClose or hand off conversationIntercom
What it does
When a customer reports a bug in Intercom, the workflow scores the conversation for repro completeness and, if it falls short, sends a friendly message asking for the exact gaps. A scheduled checker then nudges again after a wait window and finally closes stale, never-completed reports so they don't clog the inbox.
When to use it
Use it for chat-first support where bug reports arrive as casual messages that rarely include steps or environment. It chases the details politely instead of leaving half-formed reports open forever.
How it works
- 1A new Intercom conversation classified as a bug triggers the run.
- 2An LLM scores the message against the repro rubric and lists missing fields.
- 3A branch decides whether the report is complete enough to hand off.
- 4If incomplete, Intercom sends a templated ask for the named missing fields and tags the conversation `awaiting-repro`.
- 5A scheduled re-check looks at conversations still tagged `awaiting-repro`: it sends one reminder, and on the second pass with no reply it closes the conversation with a courteous note.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
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.