CUSTOMER SUPPORT
Stale Article Detector from Repeat Tickets
Weekly, matches recent repeat tickets against existing Notion help articles to find docs that exist but are not preventing tickets.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFetch recurring ticket intentsZendesk
- ActionMatch intents to existing Notion articlesOpenAI
- LogicSplit true gaps from stale existing articles
- ActionFlag stale articles for rewrite in NotionNotion
- OutputPost refresh list to SlackSlack
What it does
Distinguishes missing articles from broken ones. It takes recurring ticket intents, matches them against your existing Notion help center, and flags articles that already cover a topic yet still generate tickets, signaling the content is stale, unclear, or hard to find.
When to use it
Use it when your help center is already large and the real problem is quality, not coverage. It tells editors which existing pages to rewrite rather than which new ones to create.
How it works
- 1A weekly schedule triggers the run.
- 2Zendesk returns the most common recurring ticket intents from the past week.
- 3OpenAI matches each recurring intent to the closest existing Notion article, scoring how well current content addresses it.
- 4A branch separates true gaps (no match) from staleness (a match exists but tickets persist).
- 5For stale matches, the workflow updates the Notion page's review-status property to flag a rewrite.
- 6A consolidated refresh list is posted to Slack for the content owner.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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
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.