CUSTOMER SUPPORT
Front Order-Aware Draft: Pull Stripe Facts Before Suggesting a Macro
When a billing question hits a Front inbox, this looks up the customer's Stripe payment and subscription state, picks the macro that matches their actual account situation.
How it runs
The automated pipeline, trigger to output.
- TriggerNew conversation in billing Front inboxFront
- ActionRead customer email and questionFront
- ActionLook up charges, subscription, and refund window in StripeStripe
- LogicIf no Stripe record, tag verify-identity and skip
- ActionSelect account-matched macro and fill with real figuresOpenAI
- OutputSave order-aware reply as Front draftFront
What it does
Billing replies fail when the macro doesn't match the customer's real account state. This workflow fetches the customer's Stripe data first — last charge, subscription status, refund eligibility — then chooses and fills the macro that actually fits, so the suggested draft references the right amounts and dates instead of generic placeholders.
When to use it
Use it for billing and subscription inboxes where the correct answer depends on whether a payment succeeded, a card failed, or a refund window is still open. Removes the agent's manual hop into Stripe.
How it works
- 1A new conversation in the billing Front inbox triggers the run.
- 2The customer email and question are read from Front.
- 3Stripe is queried for the customer's charges, subscription, and refund window.
- 4OpenAI selects the macro matching the actual account state and fills it with real Stripe figures.
- 5If no customer record is found in Stripe, the conversation is tagged "verify-identity" and skipped.
- 6The order-aware reply is saved as a Front draft for the agent to 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
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.