CUSTOMER SUPPORT
Front Macro-Gap Detector: Weekly Reply Clustering
Each week, pulls the agent replies your team typed by hand in Front, clusters the repetitive ones with an LLM.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionFetch last 7 days of outbound Front repliesFront
- LogicDrop replies already sent from a macro; keep hand-typed
- ActionCluster manual replies by intent and label each groupOpenAI
- LogicKeep clusters with 5+ occurrences, rank by volume
- OutputPost ranked macro candidates to Slack for claimingSlack
What it does
Finds the answers your agents keep retyping from scratch in Front and turns them into macro proposals. It scans the past week of outbound replies, ignores anything already sent from an existing macro, groups near-duplicate manual answers into themes, and surfaces the highest-volume clusters so you can decide which ones deserve a canned response.
When to use it
Run it when your saved-reply library has gone stale and agents are clearly hand-writing the same answers over and over. Good for support leads who want a data-backed, recurring nudge instead of guessing which macros to build.
How it works
- 1A weekly schedule fires the workflow.
- 2It pulls the last 7 days of outbound Front messages and filters out replies that were sent from an existing macro, keeping only hand-typed ones.
- 3An OpenAI step embeds and clusters the manual replies by intent, then drafts a one-line label and frequency count per cluster.
- 4A logic step keeps only clusters seen 5+ times, sorted by volume.
- 5The ranked candidate list is posted to a Slack channel where a teammate reacts to claim each one for macro creation.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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.
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.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
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.