CUSTOMER SUPPORT
Weekly deflection coverage digest to Slack
On a weekly schedule, reads the logged deflection-missed records from Postgres, ranks the top recurring topics with no good doc, and posts a prioritized coverage report to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery deflection-missed records (Postgres)Postgres
- LogicAggregate and rank topics by volume
- ActionWrite prioritized coverage summary (OpenAI)OpenAI
- OutputPost digest to Slack channelSlack
What it does
Once a week this workflow reads the deflection-missed and doc-gap records your team has been logging in Postgres, groups them by topic, and ranks where self-serve is failing most. OpenAI turns the aggregate into a short, plain-language report naming the highest-volume topics that lack a good article and the articles customers keep missing. It posts the digest to a Slack channel.
When to use it
Use this to run a recurring docs-and-deflection review without manually querying a database. It tells your content owners exactly which three or four articles to write or relocate next to cut the most repeat tickets.
How it works
- 1A weekly schedule triggers the run.
- 2The flow queries Postgres for the last week of deflection-missed and gap records.
- 3A logic step aggregates and ranks topics by ticket volume and missing-doc count.
- 4OpenAI writes a concise prioritized summary with concrete next actions.
- 5The digest is posted to the support Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.