CUSTOMER SUPPORT
Draft a post-resolution follow-up when a Front conversation closes
When an agent archives a Front conversation, drafts a personalized brand-voice follow-up and CSAT request, and logs the resolution summary to Notion for the support knowledge log.
How it runs
The automated pipeline, trigger to output.
- TriggerConversation resolved in FrontFront
- ActionFetch resolved thread from FrontFront
- ActionDraft follow-up and summary with OpenAIOpenAI
- OutputAttach CSAT follow-up draft in FrontFront
- OutputAppend resolution summary to Notion logNotion
What it does
Fires when an agent closes a Front conversation. It writes a short, personalized follow-up draft that confirms the fix and asks for a satisfaction rating, then attaches it in Front for a quick review-and-send. It also appends a clean resolution summary to a Notion log so recurring issues and good answers become reusable knowledge.
When to use it
Use it when you want consistent post-resolution touchpoints and a growing record of how issues were solved, without agents writing follow-ups or logging summaries by hand. Great for teams building a CSAT habit and a searchable resolution archive.
How it works
- 1A conversation is archived or marked resolved in Front, triggering the flow.
- 2The full thread and resolution are fetched from Front.
- 3OpenAI writes a brand-voice follow-up with an embedded CSAT ask, plus a concise resolution summary.
- 4The follow-up draft is attached to the Front conversation for the agent to review and send.
- 5The resolution summary is appended to a Notion support log with tags for issue type and product area.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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.