CUSTOMER SUPPORT
Weekly Unanswered-Intent Clusters to Notion
Every week, pulls Zendesk tickets that closed without a matching macro, clusters them by intent with an LLM.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFetch tickets solved in last 7 daysZendesk
- LogicKeep only tickets with no macro applied
- ActionCluster intents and suggest article titlesOpenAI
- LogicRank clusters by volume
- OutputPublish coverage-gap digest to NotionNotion
What it does
Finds the recurring questions your help center does not yet answer. It scans the last week of Zendesk tickets, keeps only those resolved without an applied macro, groups them into intent clusters, and writes a ranked digest to Notion showing volume, example tickets, and a suggested article title per cluster.
When to use it
Run it as a standing weekly ritual when you want a steady, data-driven backlog of help-content work instead of guessing what to document. Ideal for support leads doing weekly content planning.
How it works
- 1A weekly schedule fires the workflow.
- 2Zendesk returns tickets solved in the last 7 days.
- 3A filter keeps only tickets where no macro was applied (the true coverage gaps).
- 4OpenAI clusters the ticket subjects and first messages into labeled intent groups, each with a one-line summary and proposed article headline.
- 5A ranking step sorts clusters by ticket count so the biggest gaps surface first.
- 6The digest is written as a new Notion page with a table of clusters, counts, and example ticket links.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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.