CUSTOMER SUPPORT
Macro Content Freshness Auto-Rewrite Proposer
Compares the text of each Zendesk macro against the current version of the Confluence articles it cites, detects where the macro's wording contradicts the latest docs.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled freshness sweep
- ActionPull macros and current source docsZendesk
- ActionFetch live Confluence page textConfluence
- LogicScore and keep high-drift macrosOpenAI
- ActionDraft revised macro bodyOpenAI
- OutputQueue rewrites in Airtable for reviewAirtable
What it does
Beyond broken links, macros go stale in their wording — quoting old pricing, removed steps, or renamed features that still match a live page. This compares each macro's actual prose to the current Confluence source and proposes a rewritten macro where they have diverged.
When to use it
Use it after a product change, pricing update, or feature rename, when the docs were updated but the macros that paraphrase them were not. It catches semantic drift that a pure link check misses.
How it works
- 1A scheduled run begins the freshness sweep.
- 2Pull each macro and the current text of the Confluence pages it references.
- 3Use OpenAI to compare the macro wording against the live doc and score how far it has drifted.
- 4Branch: keep only macros above the drift threshold.
- 5Use OpenAI to draft a revised macro body aligned with the current doc.
- 6Append the proposed rewrites to an Airtable review queue for an editor to approve or reject.
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 AirtableBases, tables, views, automations.
- 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.