CUSTOMER SUPPORT
Build a Macro Library from Last Week's Closed Conversations
On a weekly schedule, clusters resolved Front conversations into recurring question types and writes a clean.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionExport past week's resolved Front conversationsFront
- ActionCluster by intent and draft a macro per clusterOpenAI
- LogicDrop clusters below minimum volume
- OutputWrite proposed macros to Coda review tableCoda
What it does
This workflow turns a week of resolved support traffic into a curated set of proposed macros. It clusters closed conversations by topic, drafts one polished canned reply per cluster, and lands them in a Coda table where a lead can approve, edit, or reject before they become official templates.
When to use it
Use it when your canned-reply library is stale or thin and you want it to grow from what your team actually answers. Ideal for support leads doing a weekly macro review instead of hand-writing templates from scratch.
How it works
- 1A weekly schedule triggers the run.
- 2The flow exports the past seven days of resolved Front conversations.
- 3An OpenAI step clusters them by intent and drafts a representative canned reply for each recurring cluster, with a suggested title and tags.
- 4A filter drops clusters below a minimum volume so you only review patterns worth templating.
- 5Each surviving draft macro is written as a new row in a Coda review table with status "Proposed" for sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect CodaDocs, packs, automations.
- 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
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.