CUSTOMER SUPPORT
Stale Macro Usage Impact Report for Support Leads
Cross-references your drifting Zendesk macros with how often each one was actually sent to customers.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule fires
- ActionPull macros citing deprecated docsConfluence
- ActionPull 30-day macro usage countsZendesk
- LogicRank by send volume, keep high-impact
- ActionWrite executive impact summaryOpenAI
- OutputEmail report to support leadsGmail
What it does
Knowing a macro is stale is only half the picture — you also need to know how much it is hurting you. This joins the list of drifting macros with their real usage counts so leads fix the high-traffic offenders first instead of chasing macros nobody sends.
When to use it
Run it monthly for support leadership planning. When you have a backlog of dozens of flagged macros, this tells you which three to fix this week because they went out to hundreds of customers, versus the ones safe to defer.
How it works
- 1A monthly schedule starts the report build.
- 2Pull macros that reference deprecated or archived Confluence pages.
- 3Pull each macro's application count over the last 30 days from Zendesk usage data.
- 4Branch: rank by usage and keep macros above a meaningful send-volume floor.
- 5Use OpenAI to write a concise executive summary with the top offenders and recommended fix order.
- 6Email the prioritized impact report to the support leads distribution list.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect GmailRead, draft, send, label.
- 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
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.