CUSTOMER SUPPORT
Weekly Detractor Sweep and Follow-Up
Every Monday it scans the past week's Intercom conversations for detractor signals, summarizes each at-risk customer, and schedules personalized check-in calls to win them back.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Monday schedule
- ActionPull last 7 days of Intercom chatsIntercom
- ActionScore threads for detractor signalsOpenAI
- LogicKeep only at-risk conversations
- ActionSchedule check-in call holdsGoogle Calendar
- OutputEmail ranked digest to support leadGmail
What it does
Catches the detractors who never filled out a survey. On a weekly schedule it sweeps recent Intercom conversations for negative sentiment and unresolved frustration, builds a ranked save-list, and proactively books check-in calls before those customers churn quietly.
When to use it
Use it when survey response rates are low and you suspect silent detractors. It complements real-time CSAT triggers by catching dissatisfaction expressed in chat rather than in a rating.
How it works
- 1A scheduled trigger runs every Monday morning.
- 2The flow pulls the last seven days of closed Intercom conversations.
- 3An OpenAI step scores each thread for detractor signals and writes a short why-they're-at-risk summary.
- 4A filter keeps only conversations above the risk threshold.
- 5For each at-risk customer it places a check-in call hold on Google Calendar spread across the week.
- 6A consolidated digest with summaries and proposed make-goods is emailed to the support lead via Gmail.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 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.