TICKET MANAGEMENT
Publish a Daily ARR-Weighted Queue Snapshot to Notion
Each morning, joins the open Zendesk queue against Salesforce ARR to recompute a revenue-weighted work order.
How it runs
The automated pipeline, trigger to output.
- TriggerMorning schedule triggers the run
- ActionFetch open Zendesk tickets with timestampsZendesk
- ActionAttach Salesforce ARR per ticket accountSalesforce
- LogicBlend ARR and wait time into weighted rank, flag aging high-ARR
- OutputPublish ranked snapshot table to NotionNotion
What it does
Produces a single, shareable view of what support should work today, ordered by revenue at risk rather than ticket age. Every morning it pulls the open Zendesk queue, attaches each ticket's Salesforce ARR, computes a weighted rank that blends ARR with wait time, and publishes the result as a Notion table the team can open with their coffee.
When to use it
Use it when you want a daily standup artifact that aligns the team on revenue-weighted priorities and surfaces high-value tickets aging past their target. Good for support managers who prefer a planning snapshot over real-time re-sorting.
How it works
- 1A morning schedule triggers the run.
- 2Open Zendesk tickets are fetched with their created timestamps.
- 3Each ticket's account ARR is pulled from Salesforce.
- 4A scoring step blends ARR and wait time into a weighted rank and flags high-ARR tickets exceeding their wait target.
- 5The ranked table, with aging flags highlighted, is written to a Notion page for the day.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect NotionPages, databases, comments.
- 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
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.
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
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.
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.