CUSTOMER SUPPORT
Mine a Discord Support Channel for Recurring Questions to Document
On a daily schedule, scans a Discord support channel for questions the community keeps asking, deduplicates against existing ReadMe docs.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionFetch messages from Discord channelDiscord
- ActionExtract and group questions with OpenAIOpenAI
- ActionCheck ReadMe for existing coverageReadMe
- LogicKeep recurring undocumented questions
- OutputOpen GitHub docs issuesGitHub
What it does
Keeps your community support channel from being the only place an answer lives. Each day it reads new messages in a Discord support channel, identifies recurring questions, checks whether ReadMe already documents them, and files a GitHub issue for each undocumented question so it enters the team's normal workflow.
When to use it
Use this when a lot of real support happens in Discord and good answers get buried in scrollback. It converts that tribal knowledge into tracked documentation work instead of letting the same question resurface every week.
How it works
- 1A daily schedule fires the run.
- 2Pull the last day of messages from the Discord support channel.
- 3OpenAI extracts distinct questions and groups repeats, ignoring chit-chat.
- 4Search ReadMe for existing coverage of each grouped question.
- 5A logic step keeps only questions that recur and have no doc.
- 6Open a GitHub issue per gap, labeled docs, with the question and linked Discord messages.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ReadMeAPI docs, changelog, auth.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 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
Flag Live Intercom Chats With No Help Article and Alert Slack
When an Intercom conversation closes, checks whether the customer's question is already covered by a help article.
Negative VIP CSAT to Owner Callback Scheduler
When a VIP submits a low Intercom CSAT rating, drafts a recovery note with an LLM and books a callback on the account owner's Google Calendar within their working hours.
CEO Agent: Mine Last Month's Tickets and Publish a Deflection Plan
Monthly, an agent investigates the top recurring Zendesk ticket themes, drafts and publishes the highest-confidence help articles to ReadMe.
Daily VIP Sentiment Digest for Account Owners
Each morning, pulls the prior day's Intercom conversations for VIP accounts, summarizes the overall mood per account with an LLM.
VIP Reply Sentiment Watcher with Account-Owner Escalation
Scores every inbound Intercom reply from a VIP customer for frustration and, when it crosses the anger threshold, pings the account owner in Slack with the conversation link…
Frustrated VIP Reply to Linear Escalation Ticket
When a VIP customer's Intercom reply reads as angry, opens a prioritized Linear issue with the conversation transcript, sentiment score, and account owner assigned.
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.