CUSTOMER SUPPORT
Front Macro Gap Miner: Find Repeated Questions With No Macro
On a weekly schedule, this clusters Front conversations that had no good macro match, drafts proposed new macros for the top recurring themes.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionPull unmatched and low-confidence conversations from FrontFront
- ActionCluster by intent and rank by volumeOpenAI
- ActionDraft candidate macros for top clustersOpenAI
- ActionFile proposed macros in Notion review databaseNotion
- OutputSend approval digest to SlackSlack
What it does
It mines a week of Front conversations to surface questions agents keep answering from scratch because no macro fits. It clusters the unmatched threads by topic, drafts a candidate macro for each high-frequency cluster, and routes the proposals for human approval — turning your support backlog into a self-improving macro library.
When to use it
Use it when your macro coverage is stale and agents free-type the same answers repeatedly. Run it as a recurring review so the library grows from real demand, not guesswork.
How it works
- 1A weekly schedule triggers the run.
- 2The past week's conversations flagged "needs-manual" or low-confidence are pulled from Front.
- 3OpenAI clusters them by intent and ranks clusters by volume.
- 4For each top cluster, the model drafts a reusable macro with variable placeholders.
- 5Proposed macros are written to a Notion review database with example threads attached.
- 6A Slack digest lists the proposals and their frequency for the lead to approve.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
Flag Live Intercom Chats With No Help Article and Alert Slack
When an Intercom conversation closes, checks whether the customer's question is already covered by a help article.
Negative VIP CSAT to Owner Callback Scheduler
When a VIP submits a low Intercom CSAT rating, drafts a recovery note with an LLM and books a callback on the account owner's Google Calendar within their working hours.
CEO Agent: Mine Last Month's Tickets and Publish a Deflection Plan
Monthly, an agent investigates the top recurring Zendesk ticket themes, drafts and publishes the highest-confidence help articles to ReadMe.
Mine a Discord Support Channel for Recurring Questions to Document
On a daily schedule, scans a Discord support channel for questions the community keeps asking, deduplicates against existing ReadMe docs.
Daily VIP Sentiment Digest for Account Owners
Each morning, pulls the prior day's Intercom conversations for VIP accounts, summarizes the overall mood per account with an LLM.
VIP Reply Sentiment Watcher with Account-Owner Escalation
Scores every inbound Intercom reply from a VIP customer for frustration and, when it crosses the anger threshold, pings the account owner in Slack with the conversation link…
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.
