Support-to-CRM Escalation
Escalate high-priority Zendesk tickets into linked Salesforce cases automatically, with full conversation history attached and statuses kept in sync.
The problem
When a key customer files an urgent ticket, the account team usually finds out days later, if at all. Support agents copy ticket details into the CRM by hand, losing the conversation history along the way. Escalations depend on someone remembering to forward an email.
How it runs on Neblex
A Zendesk webhook fires when a ticket is created or its priority changes, and conditional branching filters for the escalation criteria you define, such as priority, customer tier, or keywords. The flow then pulls the full ticket thread, including comments and attachments.
Dedup matching rules link the ticket to the right Salesforce account and check for an existing open case before creating a new one. Field mapping shapes the ticket into a case with the conversation history attached, and the case link is written back to the Zendesk ticket so both teams see the connection.
Poll-based change detection keeps status in sync in both directions afterward: when the case closes or the ticket resolves, the other side updates. Per-step retries and replay from the failed step mean an API hiccup does not lose an escalation.
Step by step
Trigger on the ticket
A Zendesk webhook starts the run on creation or priority change.
Filter for escalation
Conditional branching applies your criteria: priority, customer tier, keywords.
Collect the history
The flow gathers the full conversation thread and attachments.
Create the linked case
Dedup rules match the account and existing cases, then field mapping builds the Salesforce case.
Keep both sides in sync
Poll-based change detection mirrors status between the ticket and the case until both close.
Platform capabilities used
- Webhook triggers
- Conditional branching
- Dedup via matching rules
- Field mapping
- Poll-based change detection
- Replay from the failed step
Common questions
Will this create duplicate cases?
No. Dedup matching rules check for an existing open case on the account before anything is created. Repeat updates on the same ticket flow into the existing case.
Can a human review before the case is created?
Yes. An approval step can pause the run and place the decision in the task inbox, with SLA timers and escalation if nobody acts. Most teams reserve this for specific segments and let the rest flow straight through.
What data is copied into Salesforce?
You control the mapping. Field mapping with value-aware AI suggestions proposes the field pairs, and you decide which parts of the conversation history attach to the case. The event-sourced run history records exactly what was written.
Related use cases
Usage-Based Health Scoring
Roll product usage from Snowflake into a Gainsight health score on a schedule and alert the account team in Slack when an account trends down.
IT & DevOpsITSM Automation
Automate the ServiceNow ticket lifecycle: intake from any channel, categorization, SLA-based routing, Jira handoff, and resolution updates in Slack.
AgenticSupport Triage Agent
A triage agent reads each Zendesk ticket, judges urgency and sentiment, drafts a reply, and escalates anything it is unsure about to a human for review.
Want this running on your stack?
Neblex Integration Fabric is in beta: full platform, free while in beta. Bring this workflow and we will map it to your systems.