CUSTOMER SUPPORT
Macro Trainer Agent: Self-Directed Mining of Intercom History into a Reviewed Macro Library
An agent-driven worker that explores resolved Intercom threads, decides which recurring problems deserve a canned reply, drafts and deduplicates them against the existing library.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator starts the agent run
- ActionQuery and sample resolved Intercom conversationsIntercom
- LogicReason over threads to pick recurring problems worth a macro
- LogicDeduplicate candidates against the existing library
- OutputPublish the curated macro library to ConfluenceConfluence
What it does
This is the agent-run version of macro training. Rather than a fixed pipeline, a worker investigates your resolved Intercom history on its own: it samples threads, identifies the themes worth canning, checks each candidate against macros that already exist so it doesn't propose duplicates, and assembles a clean, deduplicated macro library. The finished set is published to a Confluence page your team can read and adopt.
When to use it
Use it for a deeper, judgment-heavy pass than a clustering pipeline gives you, especially when topics overlap, phrasing varies, and you want the worker to reason about which replies are genuinely distinct and worth maintaining.
How it works
- 1A chairman or operator kicks off the agent run.
- 2The agent queries Intercom for resolved conversations and samples across topics and time.
- 3It groups and reasons over the threads to decide which recurring problems merit a canned reply.
- 4For each candidate it checks the existing library and merges or discards near-duplicates.
- 5It writes final macro titles and bodies grounded in how agents actually resolved each issue.
- 6It publishes the curated macro library to a Confluence page for team review.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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.
