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.

CategoryTicket Management
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Zendesk ticket createdZendeskZendesk
  • 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 noteZendeskZendesk

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

  1. 1A new ticket in Zendesk fires the trigger and passes the requester email.
  2. 2The flow queries Salesforce for the matching Account and reads its annual contract value.
  3. 3A branch maps ARR to a target priority: above $250k becomes Urgent, $50k-$250k becomes High, below stays as submitted.
  4. 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.
  5. 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.

  1. 1
    Connect ZendeskTickets, queues, knowledge base.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.