CUSTOMER SUPPORT
Repeat-Frustration VIP Health Brief for the Account Owner
When a VIP account shows frustration across multiple recent Intercom threads, an agent gathers the conversation history and CRM context, writes a relationship health brief.
How it runs
The automated pipeline, trigger to output.
- TriggerRepeat-frustration signal on a VIP accountIntercom
- ActionGather recent Intercom thread historyIntercom
- ActionRead account context from AttioAttio
- ActionSynthesize relationship health brief with OpenAIOpenAI
- ActionLog brief as a note on the Attio accountAttio
- OutputAlert the owner in Slack with at-risk flagSlack
What it does
Detects a pattern rather than a single bad message. When the same VIP account turns frustrated across several recent conversations, an agent investigates the history, weighs it against open deals and account value, and produces a relationship health brief with recommended next moves.
When to use it
Use this for your highest-stakes accounts where one angry message is noise but a recurring trend is a churn emergency. Best when you want analysis and a recommended play, not just a forwarded transcript.
How it works
- 1A repeated-frustration signal across recent VIP replies triggers the workflow.
- 2The agent pulls the account's full recent Intercom thread history.
- 3It reads the Attio record for account value, owner, renewal date, and open deals.
- 4OpenAI synthesizes a health brief: trend summary, likely root cause, churn risk, and a recommended next action.
- 5The brief is logged as a note on the Attio account for the record.
- 6A Slack alert goes to the owner linking the brief and flagging the account as at-risk.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect AttioReal-time CRM with structured data + powerful views.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.