AASA Labs
Documentation

Escalation Guard Documentation

Escalation Guard helps agents send cleaner escalations from the Zendesk ticket sidebar. Admins create templates, agents complete the required context, and the app writes a private internal note with routing tags.

Overview

Escalations slow down when the receiving team has to ask for missing details. Escalation Guard gives agents a structured form before they escalate, so the handoff includes the context another team needs to act.

Each template can include required questions, optional fields, and routing tags. When an agent submits the form, Escalation Guard adds a private note to the ticket and applies the configured tags.

Escalation Guard does not replace Zendesk triggers or views. It helps standardize the handoff. Your Zendesk workflow can then use the tags to route, notify, or report on escalations.

Install

  1. Install Escalation Guard from the Zendesk Marketplace.
  2. Leave the templates_json setting blank unless ASA Labs support gives you a template file.
  3. After install, open Escalation Guard from the Zendesk left navigation bar.
  4. Review the starter template.
  5. Save your template settings.
  6. Open a ticket and test the app from the sidebar.
Admin setup happens from the Zendesk left navigation bar. Agents use Escalation Guard from the ticket sidebar.

Quick start

  1. Open the Template Builder.
  2. Choose a starter template or create your own.
  3. Add the questions agents should answer before escalating.
  4. Mark the most important questions as required.
  5. Add one or more routing tags.
  6. Save the template.
  7. Create a Zendesk view or trigger that uses the routing tag.

Start with one common escalation path first. Once agents are using it cleanly, add the next template.

Templates

Templates are the escalation forms agents choose from. A template should map to a real workflow, not a broad category that means different things to different teams.

Common examples include manager review, billing review, product issue review, account access review, customer complaint, or executive escalation.

Use names agents already understand. "Billing review" is usually better than "Financial exception workflow."

Required context

Required fields prevent agents from submitting an escalation before the key details are filled in. Use them for context the receiving team always needs.

Field typeGood use
TextShort answers such as order ID, account ID, or decision needed.
Long textSummaries, investigation notes, or what the agent already checked.
DropdownKnown choices such as escalation reason, priority, or team.
CheckboxSimple confirmations, such as "policy reviewed" or "customer verified."
NumberAmounts, counts, or other numeric values.
Keep templates short. If every field is required, agents may stop trusting the form. Required should mean truly needed.

Routing tags

Routing tags are added when an agent submits an escalation. Most teams use those tags for Zendesk views, triggers, automations, and reporting.

For example, a billing escalation template might add a billing review tag. A Zendesk trigger can then notify the billing team, move the ticket to a billing group, or make the ticket appear in a billing review view.

Simple trigger example

  • Condition: ticket contains the escalation tag.
  • Action: assign the ticket to the right group, notify a team, or add it to a view.
Escalation Guard adds tags. It does not remove existing tags or decide where the ticket should go.

Field mapping

Pro admins can map answers from the escalation form into Zendesk ticket fields. This is useful when the same information should appear in reporting, views, or other workflows.

Agents still complete one escalation form. Escalation Guard can then write the internal note, apply routing tags, and update mapped ticket fields.

Field mapping is optional. Many teams can start with internal notes and routing tags, then add mapping later if they need cleaner reporting.

Internal note

When an agent submits an escalation, Escalation Guard posts a private internal note on the ticket. The note includes the template name and the agent's answers.

Agent NameInternalSaturday 23:29

⚠️ Escalation Guard — Billing / Refund Exception

Request type: Refund request

Amount: 84.27

Order, invoice, or transaction ID: INV-10482

Customer claim:
Customer says they were charged twice after retrying payment and is asking for one charge to be refunded.

Policy or payment history checked:
Payment history shows two posted charges for $84.27.

Decision needed: Approve refund for the duplicate charge.

The note is meant to be readable by the receiving team. Blank optional fields are skipped so the note does not get cluttered.

Plans

FeatureLitePro
TemplatesOne active templateMultiple templates
Required fieldsIncludedIncluded
Routing tagsIncludedIncluded
Internal notesIncludedIncluded
Ticket field mappingNot includedIncluded
Import and exportNot includedIncluded

FAQ

Does Escalation Guard use AI?

No. Escalation Guard does not use AI or machine learning.

Does Escalation Guard send data to an external service?

No. Escalation Guard runs in Zendesk and does not send escalation data to an external backend.

Does it route tickets automatically?

No. The app applies tags and writes the note. Your Zendesk triggers, automations, or views handle routing.

Can agents submit an escalation with missing required fields?

No. Required fields must be completed before the escalation can be submitted.

Can I customize the templates?

Yes. Admins can create and edit templates from the Template Builder.

Can I use Escalation Guard without field mapping?

Yes. Many teams start with templates, required fields, internal notes, and routing tags only.

Will Escalation Guard remove existing ticket tags?

No. It adds configured escalation tags and leaves existing ticket tags in place.

Back to Escalation GuardPrivacy PolicyTerms