CUSTOMER SUPPORT
Route AI-drafted README troubleshooting sections through Slack approval
Drafts a README troubleshooting section from recurring Intercom themes, posts it to a Slack channel with approve/reject buttons.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule for theme review
- ActionFetch and theme Intercom conversationsIntercom
- ActionDraft highest-impact troubleshooting sectionOpenAI
- ActionPost draft to Slack with approve/reject buttonsSlack
- LogicBranch on reviewer's approve or reject
- OutputPublish approved section to READMEReadMe
What it does
It adds a human gate between AI drafting and publishing. The workflow proposes a troubleshooting section based on recurring Intercom issues, then sends the full draft to Slack where a docs owner approves or rejects it. Approved drafts publish to README automatically; rejected ones are discarded with the reviewer's note logged.
When to use it
Use it when you want the speed of auto-drafting but refuse to publish machine-written docs unreviewed. Ideal for teams with brand-voice or accuracy standards on public documentation.
How it works
- 1A schedule triggers a weekly review of recurring Intercom conversation themes.
- 2Intercom conversations from the period are fetched and themed by OpenAI.
- 3OpenAI drafts the highest-impact troubleshooting section.
- 4The draft is posted to a Slack channel with approve and reject actions.
- 5A logic branch waits on the reviewer's choice.
- 6On approve, the section publishes to README; on reject, it is discarded and the note recorded.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect ReadMeAPI docs, changelog, auth.
- 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.