CUSTOMER SUPPORT
Weekly Macro Miner: Cluster Resolved Tickets into Draft Canned Replies
Every week, pulls the last 7 days of solved Zendesk tickets, clusters the ones answered with similar free-text replies.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionFetch tickets solved in last 7 daysZendesk
- ActionCluster near-duplicate reply textOpenAI
- LogicKeep clusters with 3+ tickets
- ActionDraft macro title and body per clusterOpenAI
- OutputCreate review cards in NotionNotion
What it does
Finds the answers your agents keep retyping. Once a week it scans recently solved tickets, groups the ones whose resolution replies say essentially the same thing, and turns each cluster into a ready-to-edit macro draft — title, suggested body, and the example tickets it came from — parked in Notion for a lead to approve.
When to use it
When your team resolves the same questions by hand instead of with macros, and nobody has time to audit the backlog to find the patterns. Run it as a standing weekly ritual so the macro library grows from real answers, not guesswork.
How it works
- 1A weekly schedule fires the run.
- 2Fetch all tickets solved in the last 7 days from Zendesk, including the agent's public reply text.
- 3Send the replies to OpenAI to cluster near-duplicate answers and label each cluster by intent.
- 4Filter out clusters with fewer than 3 supporting tickets so only repeatable answers advance.
- 5For each surviving cluster, have OpenAI draft a clean macro title and body from the example replies.
- 6Create one Notion card per draft with the suggested macro and links to source tickets for review.
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.