CUSTOMER SUPPORT
Audit macros for low usage and stale wording
Monthly, compares each Zendesk macro's usage stats against recent ticket trends, flags unused or outdated macros, and files a cleanup report in Notion for the support lead.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule fires
- ActionPull macros and usage from ZendeskZendesk
- ActionPull current ticket topic trendsSupabase
- ActionFlag stale and redundant macrosOpenAI
- LogicRank findings by impact
- OutputPublish cleanup report to NotionNotion
What it does
Keeps your macro library lean. Once a month it checks which macros are actually being used, which haven't fired in ages, and which describe a product behavior that has since changed, then writes a prioritized cleanup list.
When to use it
Run it when your macro list has grown faster than anyone's appetite to prune it, and agents complain they can't find the right one. Good hygiene for teams with hundreds of macros.
How it works
- 1A monthly schedule starts the audit.
- 2Pull every macro plus its usage counts from Zendesk.
- 3Pull recent solved-ticket topic frequencies from Supabase to see what customers ask about now.
- 4Send both lists to OpenAI to flag macros that are unused, redundant, or describe outdated behavior, with a recommended action each.
- 5Rank findings by impact so the lead tackles the worst offenders first.
- 6Write the report as a new page in Notion and link it for review.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect SupabaseTables, auth, storage, edge functions.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect NotionPages, databases, comments.
- 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
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.