TICKET MANAGEMENT
Reprioritize Zendesk Tickets by Account ARR on Create
When a Zendesk ticket is created, looks up the requester's account ARR in Salesforce and bumps the ticket priority so high-revenue customers get triaged first.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Zendesk ticket createdZendesk
- ActionLook up requester account ARR in SalesforceSalesforce
- LogicMap ARR to target priority tier
- LogicOnly override if target outranks current priority
- OutputUpdate Zendesk priority and add override noteZendesk
What it does
Every new Zendesk ticket arrives with the priority the customer (or a default rule) set. This workflow ignores that and re-derives priority from the dollar value of the account behind the requester, so a paperwork question from a $500k account never sits below a feature request from a free trial.
When to use it
Run this when your queue is sorted purely by submitter-selected priority and your top accounts keep getting buried. It is ideal for support teams that have ARR in Salesforce but no revenue signal inside Zendesk.
How it works
- 1A new ticket in Zendesk fires the trigger and passes the requester email.
- 2The flow queries Salesforce for the matching Account and reads its annual contract value.
- 3A branch maps ARR to a target priority: above $250k becomes Urgent, $50k-$250k becomes High, below stays as submitted.
- 4If the computed priority outranks the current one, the flow updates the Zendesk ticket priority and adds an internal note explaining the ARR-based override.
- 5The final step writes the original and new priority to the ticket so agents see why it moved.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.
