As support teams grow, escalation paths multiply.
Engineering. Finance. Tier 2. Vendors. Regional teams.
Without structure, the escalation dropdown quickly becomes a long list that agents need to scroll through every time they escalate a ticket.
Escalator solves this by letting you organize escalation paths into folders and sub-folders directly inside Zendesk. Instead of a flat list, you get a clear hierarchy that reflects how your support organization actually works.
Why structure matters
When escalation paths are unorganized, agents often:
• Scroll through long lists to find the right path
• Select the wrong escalation by mistake
• Duplicate escalation paths without realizing it
• Avoid escalation altogether because it feels messy
Folders solve this by grouping related escalation paths together so agents can immediately see where a ticket should go.
Folder structures that work well
There’s no single “correct” structure. The best setup mirrors how your team operates.
1. Internal vs external
A common pattern is separating internal teams from vendors.
Under internal teams:
Technical support
Engineering
Finance
Customer success
Under external vendors:
Payment providers
Shipping partners
Hardware suppliers
This makes it instantly clear whether an escalation stays inside your Zendesk account or goes outside the organization.
2. By department
Some teams prefer grouping by business function:
Billing
Logistics
Product
IT
Compliance
This works well if your support team regularly escalates across departments.
3. By product
If you support multiple products or services, escalation paths can be grouped by product line.
For example:
-
Product A
Tier 2
Vendor X
-
Product B
Tier 2
Vendor Y
This keeps workflows separated and easier to manage.
When to use sub-folders
Sub-folders are helpful when you have more than 4–5 escalation paths in a single category.
Use sub-folders when:
You have multiple vendors under one type (for example, multiple payment gateways)
You separate regional teams (APAC, EMEA, US)
You distinguish between Tier 2 and Tier 3
You want to group legacy or rarely used escalations
For example, internal teams with tiers:
Another example, vendors grouped by type:
If a folder becomes long enough that agents need to scroll, it’s usually time to introduce a sub-folder.
Keep it simple. Two levels are usually enough.
Naming escalation paths clearly
Folders help organization, but clear naming helps agents move faster.
Instead of generic names like:
• Tech
• Support
• Vendor escalation
Use names that show exactly where the ticket will go:
• Engineering – Bug investigation
• Finance – Billing dispute
• Vendor – Stripe
• Shipping – DHL escalation
An agent should be able to glance at the name and know the destination immediately.
Where this fits in Escalator
Escalator lets administrators:
• Create folders and sub-folders
• Organize escalation paths into a hierarchy
• Move or sort escalation paths easily
• Keep internal teams and vendor workflows separated
You don’t need to rebuild workflows. You simply organize them.
For configuration details, see the Escalation/ sub-ticket management section in the Escalator user guide.
Bring structure to your Zendesk escalations
As support operations grow, a flat escalation list doesn’t scale.
Folders and hierarchy help agents find the right escalation path faster, reduce mistakes, and keep workflows organized.
Explore Escalator's product page to see how structured escalation paths can simplify complex support workflows.
Install Escalator from the Zendesk Marketplace to start your free 14-day trial.
Comments