CUSTOMER SUPPORT
Front Draft Pre-Warmer with Live Order Lookup
When a Front conversation lands, looks up the customer's order and payment status in Stripe.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Front conversation receivedFront
- ActionLook up customer charges and refunds in StripeStripe
- LogicBranch on Stripe customer match
- ActionDraft order-aware reply with OpenAIOpenAI
- OutputSave reply as Front draftFront
What it does
For ecommerce and billing inboxes, this enriches each new Front conversation with the customer's real Stripe order and payment data, then drafts a reply that references their actual charge, refund, or subscription state. Agents get a draft that already knows the account.
When to use it
When most of your tickets are "where's my order" or "why was I charged" and agents waste time cross-referencing Stripe before they can answer. Pre-warming the draft with live data collapses that lookup into one step.
How it works
- 1A new Front conversation triggers the flow.
- 2The customer's email is matched against Stripe to retrieve their latest charges, refunds, and subscription status.
- 3A branch checks whether a Stripe customer was found.
- 4If found, OpenAI drafts a reply referencing the specific order and payment state; if not, it drafts a request for account details.
- 5The reply is saved as a Front draft on the conversation for the agent to edit and send.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect StripeCustomers, subscriptions, payments.
- 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
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.