CUSTOMER SUPPORT
Open an Intercom follow-up when a Zoom call ends on a sour note
Detects Zoom support calls that ended with unresolved frustration and automatically creates a prioritized Intercom conversation assigned to the agent's lead for a proactive…
How it runs
The automated pipeline, trigger to output.
- TriggerZoom support call recording completesZoom
- ActionPull transcript and match Intercom contactIntercom
- ActionJudge closing sentiment and draft recovery noteOpenAI
- LogicSkip calls that ended positive or neutral
- OutputCreate prioritized Intercom follow-up for leadIntercom
What it does
Analyzes each completed Zoom support call for unresolved negative sentiment at the close of the conversation. When a call ends badly, it opens an Intercom follow-up conversation with the customer, pre-filled with context and a suggested recovery message, and assigns it to the team lead for review before it goes out.
When to use it
Use this when a frustrated call should never just end. It is for support teams that want a guaranteed proactive touch on at-risk customers, with the lead in the loop to coach the recovery rather than letting the original agent close the loop alone.
How it works
- 1A Zoom recording-completed event fires for a finished support call.
- 2The flow pulls the transcript and matches the customer to their Intercom contact.
- 3OpenAI judges the closing sentiment and drafts a recovery note if the call ended poorly.
- 4A logic step exits for calls that ended on a positive or neutral note.
- 5An Intercom conversation is created, prioritized, and assigned to the agent's lead with the draft and call summary.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect IntercomConversations, contacts, articles.
- 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.
