CUSTOMER SUPPORT
Reopen Cohort Export to Snowflake
Daily, it identifies all bot-resolved-then-reopened Intercom conversations, enriches them with reopen latency and final outcome.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionPull resolved and reopened conversations from IntercomIntercom
- ActionCompute reopen latency and final outcome
- LogicNormalize and drop incomplete records
- OutputUpsert cohort table into SnowflakeSnowflake
What it does
Each day it builds a tidy dataset of every false deflection — bot resolved, customer reopened — with how long the reopen took and how the conversation ultimately ended, and loads it into Snowflake so analysts can model deflection quality alongside the rest of the warehouse.
When to use it
Use it when your data team owns deflection metrics and wants the raw cohort in the warehouse rather than a prebuilt report. It feeds dashboards, CSAT joins, and retention analysis.
How it works
- 1A daily schedule fires.
- 2Pull the prior day's bot-resolved and reopened conversations from Intercom.
- 3Compute reopen latency and resolve the final disposition for each conversation.
- 4A logic step normalizes records into a flat schema and drops incomplete rows.
- 5Upsert the cohort into a Snowflake table keyed by conversation ID and date.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.