CUSTOMER SUPPORT
Detect missing macros from manually-written resolutions
When an agent solves a ticket with a fully hand-typed reply, checks whether the answer matches any existing macro and, if not, asks the CEO agent to draft a new macro candidate…
How it runs
The automated pipeline, trigger to output.
- TriggerTicket marked solved in ZendeskZendesk
- LogicSkip replies sent from a macro
- ActionAgent judges if reply is reusable
- LogicBranch on reusable vs one-off
- ActionLog macro gap and candidateSupabase
- OutputOpen Linear issue for docs ownerLinear
What it does
Catches the macros you don't have yet. Every time an agent writes a resolution from scratch instead of using a macro, it asks whether that answer should have been a macro and, when it should, drafts one as an org task for review.
When to use it
Use it to grow your library organically from real agent work, especially for newer or fast-changing products where canned answers lag behind reality.
How it works
- 1A ticket moving to solved in Zendesk triggers the run.
- 2Check whether the closing reply came from an existing macro; skip if it did.
- 3For hand-typed resolutions, have the CEO agent compare the reply against the macro library to judge whether it represents a reusable pattern.
- 4Branch: if it's a one-off, log nothing and stop.
- 5If it's reusable, the agent drafts a candidate macro and records the gap with the source ticket in Supabase.
- 6Open a Linear issue assigning the new candidate to the docs owner for finalization.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect SupabaseTables, auth, storage, edge functions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.