CUSTOMER SUPPORT
Cluster monthly deflection failures into doc gaps
Monthly, it groups all failed-deflection questions by topic, finds clusters where no single article answers a recurring need.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule
- ActionRead month's failed-deflection records from PostgresPostgres
- LogicCluster questions by intent; isolate true content gaps
- ActionCreate Asana task per gap clusterAsana
- OutputDraft stub article in ReadMe and link to taskReadMe
What it does
Finds the missing articles, not just the weak ones. Once a month it takes every question that escalated past the help center, clusters them by intent, and detects clusters that no existing article covers well. For each real gap it opens an Asana task and seeds a stub page in ReadMe so the docs team can start from a defined need instead of a blank page.
When to use it
Use this when failures aren't about one bad article but about content that doesn't exist yet. It converts a month of scattered failing questions into a short, deduplicated list of net-new articles worth writing.
How it works
- 1A monthly schedule starts the run.
- 2It reads the month's failed-deflection records from Postgres, including each question and the article shown.
- 3An agent clusters the questions by intent and separates true content gaps from cases an existing article should have handled.
- 4For each gap cluster it creates an Asana task in the Docs board describing the unmet need and example questions.
- 5It drafts a matching stub page in ReadMe and links it on the Asana task for the writer to flesh out.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect AsanaTasks, projects, milestones — everywhere.
- 3Connect ReadMeAPI docs, changelog, auth.
- 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 Customer Support workflows
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.
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.
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.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
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.
