CUSTOMER SUPPORT
Front Macro Auto-Suggester: Draft Reply from Best-Match Macro
When a new inbound conversation lands in a Front inbox, this picks the best-matching macro from your library, drafts a reply by filling its variables from the message.
How it runs
The automated pipeline, trigger to output.
- TriggerNew inbound conversation in Front inboxFront
- ActionRead message thread and customer metadataFront
- ActionFetch macro library from NotionNotion
- ActionScore macros and draft filled replyOpenAI
- LogicIf confidence below threshold, tag needs-manual and stop
- OutputSave reply as Front draft for the ownerFront
What it does
Every inbound Front conversation gets an instant first-pass reply waiting in the draft box. The workflow reads the customer message, ranks your macro library by relevance, fills the chosen macro's placeholders with details pulled from the thread, and saves it as an unsent Front draft so a human always makes the final call.
When to use it
Use it when your team answers a high volume of repetitive support questions from macros but agents lose time finding the right one and hand-filling names, order numbers, and dates. Best for inboxes where reply quality is template-driven and a human still presses send.
How it works
- 1A new conversation arriving in the watched Front inbox triggers the run.
- 2The full message thread and customer metadata are read from Front.
- 3The macro library (stored in Notion) is fetched so the model can score every macro against the message.
- 4OpenAI selects the single best macro and rewrites it, substituting variables drawn from the conversation.
- 5If model confidence is below threshold, the conversation is left untouched and tagged "needs-manual".
- 6The filled reply is written back as a Front draft assigned to the conversation owner.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect NotionPages, databases, comments.
- 3Connect OpenAIModels, embeddings, files.
- 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.