CUSTOMER SUPPORT
Detect an Intercom issue spike and flag the missing README troubleshooting section
Monitors Intercom conversation volume per issue topic, and when a topic spikes above baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled sampling of Intercom topic volume
- LogicCompare current volume to rolling baseline
- ActionSearch README for existing topic sectionReadMe
- ActionDraft starter section if coverage missingOpenAI
- OutputAlert docs owner in Slack with spike stats and draftSlack
What it does
It catches documentation gaps the moment they start hurting. The workflow tracks Intercom conversation volume by topic, detects when a topic spikes above its normal baseline, then searches README to see whether a troubleshooting section already exists. If it does not, it drafts a starter section and alerts the docs owner that coverage is missing.
When to use it
Use it when a sudden surge in tickets usually means a release broke something or a doc is stale, and you want an early warning rather than a weekly retrospective.
How it works
- 1A schedule samples Intercom conversation volume by topic at a regular interval.
- 2A logic step compares current volume against each topic's rolling baseline.
- 3Spiking topics pass; steady ones are dropped.
- 4README is searched for an existing troubleshooting section on the topic.
- 5If none exists, OpenAI drafts a starter section seeded from the spike's conversations.
- 6A Slack alert goes to the docs owner with the spike stats and the draft link.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect ReadMeAPI docs, changelog, auth.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.