TICKET MANAGEMENT
Forecast aging Intercom conversations and open ClickUp follow-ups before they breach
Every 30 minutes, projects which open Intercom conversations will exceed first-response or resolution SLA based on reply cadence.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 30 minutes
- ActionFetch open Intercom conversations with reply timestampsIntercom
- LogicProject time-to-breach from reply cadence
- LogicKeep conversations within warning window
- ActionOpen or update ClickUp follow-up tasksClickUp
- OutputPost at-risk list to SlackSlack
What it does
This workflow watches open Intercom conversations and forecasts which ones are drifting toward an SLA miss based on how their reply cadence is trending. Instead of waiting for the SLA timer to fire, it projects time-to-breach from the gap since last agent reply and the conversation's response history, then creates a tracked follow-up so nothing silently ages out.
When to use it
Use this when support runs in Intercom but work and accountability live in ClickUp, and conversations breach because they quietly stall between replies. It bridges the conversation and the task systems.
How it works
- 1A schedule fires every 30 minutes.
- 2Pulls open Intercom conversations with timestamps of last customer and agent messages.
- 3Projects each conversation's time-to-breach from reply cadence and the applicable SLA target.
- 4A branch keeps conversations forecast to breach within the warning window.
- 5Creates or updates a ClickUp follow-up task for each at-risk conversation with a deep link and deadline.
- 6Posts the at-risk conversation list to Slack for the team lead.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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 Ticket Management workflows
Enrich Discord bug reports with Sentry errors before filing in Linear
Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
Weekly reopen-by-agent coaching digest
Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.
Escalate repeat reopens to a Linear bug
Detects when the same underlying issue reopens across multiple tickets, uses an AI agent to cluster them by root cause.
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.