CUSTOMER SUPPORT
CEO-Driven Macro Library Curator and Auto-Publisher
An agent reviews the week's proposed macro drafts, deduplicates them against the live library, rewrites each to brand voice.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly curation schedule fires
- ActionPull macro drafts and live Zendesk libraryZendesk
- LogicAgent dedupes, merges, and rewrites to brand voice
- LogicRoute by confidence and overlap
- ActionAuto-publish novel macros to ZendeskZendesk
- OutputFile borderline macros in Notion for sign-offNotion
What it does
Turns raw macro proposals into a polished, deduplicated library without a human editing every one. The CEO agent reads each draft, decides whether it overlaps an existing macro, rewrites the wording to match your support tone and policy, and acts: high-confidence, non-overlapping macros get created in Zendesk automatically; the rest go to Notion for a human decision.
When to use it
When draft macros pile up faster than a lead can curate them, and you trust an agent to handle the obvious publishes while still escalating the judgment calls.
How it works
- 1A schedule kicks off the weekly curation pass.
- 2The agent pulls pending macro drafts and the current Zendesk macro list.
- 3It reasons over each draft: detects duplicates, merges overlaps, and rewrites the body to brand voice.
- 4Branch on confidence and overlap to route each macro.
- 5For clear, novel macros, create them directly in Zendesk and tag them as auto-published.
- 6For borderline or conflicting macros, create a Notion approval card with the agent's reasoning attached for a human to accept or reject.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect NotionPages, databases, comments.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.