CUSTOMER SUPPORT
Escalate repeat-complaint accounts to Slack and open a Linear issue
When an account logs its third negative Intercom conversation inside 30 days, an agent confirms the pattern, posts a war-room alert to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerNegative conversation loggedIntercom
- LogicCount negatives in 30-day window (>=3)
- ActionAgent summarizes recurring root causeOpenAI
- ActionPost war-room alert to SlackSlack
- OutputOpen Linear issue for root causeLinear
What it does
One bad ticket is noise; three in a month is a pattern. This workflow detects when the same account has accumulated multiple negative support conversations in a rolling 30-day window, has an agent summarize the through-line across them, then escalates both to people (Slack) and to engineering (Linear) so the root cause actually gets owned.
When to use it
Use it when isolated complaints are handled fine but recurring frustration from a single account goes unnoticed until they cancel. Best for high-value accounts where compounding friction predicts churn.
How it works
- 1A new negative-conversation event triggers the workflow for an account.
- 2A logic step counts that account's negative conversations in the trailing 30 days and proceeds only at three or more.
- 3A Paperclip agent reads the conversation set, identifies the common recurring issue, and writes a concise root-cause summary.
- 4It posts a churn war-room alert to the customer-success Slack channel tagging the account owner.
- 5It opens a Linear issue with the summary and links so engineering can track the underlying fix.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect LinearIssues, projects, cycles, triage.
- 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
Flag Live Intercom Chats With No Help Article and Alert Slack
When an Intercom conversation closes, checks whether the customer's question is already covered by a help article.
Negative VIP CSAT to Owner Callback Scheduler
When a VIP submits a low Intercom CSAT rating, drafts a recovery note with an LLM and books a callback on the account owner's Google Calendar within their working hours.
CEO Agent: Mine Last Month's Tickets and Publish a Deflection Plan
Monthly, an agent investigates the top recurring Zendesk ticket themes, drafts and publishes the highest-confidence help articles to ReadMe.
Mine a Discord Support Channel for Recurring Questions to Document
On a daily schedule, scans a Discord support channel for questions the community keeps asking, deduplicates against existing ReadMe docs.
Daily VIP Sentiment Digest for Account Owners
Each morning, pulls the prior day's Intercom conversations for VIP accounts, summarizes the overall mood per account with an LLM.
VIP Reply Sentiment Watcher with Account-Owner Escalation
Scores every inbound Intercom reply from a VIP customer for frustration and, when it crosses the anger threshold, pings the account owner in Slack with the conversation link…
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.