CUSTOMER SUPPORT
Make-Good Follow-Up No-Reply Chaser
Tracks detractors who received a make-good offer and, if there's no reply within three days, sends a gentle reminder and books a fallback call so recovery attempts don't go cold.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionQuery make-goods sent 3+ days agoAirtable
- LogicKeep only non-responders
- ActionDraft warm reminder noteOpenAI
- ActionHold fallback recovery callGoogle Calendar
- OutputSend reminder and mark record chasedGmail
What it does
Closes the loop on recovery offers. After a make-good email is sent to a detractor, this checks back in three days; if the customer hasn't responded, it sends one tactful nudge and reserves a fallback call slot so the save attempt actually lands instead of dying in an inbox.
When to use it
Use it as the second half of any detractor-recovery play. Pair it with a make-good drafter so offers that get ignored are automatically chased exactly once before the agent steps in.
How it works
- 1A daily schedule trigger runs each morning.
- 2The flow queries Airtable for make-good records sent three or more days ago.
- 3A logic step checks each record's reply status.
- 4For non-responders, an OpenAI step drafts a short, warm reminder referencing the original offer.
- 5A fallback recovery call is held on Google Calendar in case they want to talk.
- 6The reminder is sent from Gmail and the Airtable record is marked chased so it's never nudged twice.
Set it up
What you configure once, before turning it on.
- 1Connect AirtableBases, tables, views, automations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect Google CalendarEvents, attendees, availability.
- 4Connect GmailRead, draft, send, label.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.