Navigate
Deskpro Support
  • Register

  • or
  • Login
    Need a password reminder?
  • English
or
Contact Us
  • Get in touch

    Send us an email

  • Submit Feedback

    Feedback and suggestions submitted by customers like you

  • Start a chat session

  • Knowledgebase Read help articles
  • Guides Product documentation
  • News News & updates
  • Feedback Custom suggestions
  • Downloads Browse our downloads
  • Contact Us We are here to help
Admin Guide
Download PDF

  • Introducing Deskpro
    • Deskpro Features and Benefits
    • Deskpro basic concepts
    • Account Types
    • Deskpro Interfaces
  • Creating Your Helpdesk
    • Cloud vs. On-Premise
    • Cloud Sign-Up
    • Custom Domains
    • Setting Basic Details
    • Disabling the Helpdesk
  • Launching Your Helpdesk
    • Personalize your Helpdesk
    • Organize with Departments
    • Set up your Agents
    • Decide on User Channels
    • Triggers for Automation
    • Extra Customization options
    • Launch the Helpdesk!
  • Importing Data
    • Helpdesk Data Importer: Zendesk
    • Helpdesk Data Importer: Kayako
    • CSV User Import
    • Import/Export via API
  • Managing and Deleting Personal Data
    • How To: Delete Knowledgebase Articles
    • How to: Delete Chats
    • How to: Delete Tickets
    • How to: Delete Users
    • How to: Delete Agents
    • How to: Export User Data
    • How to: Delete Guide Topics
    • How to: Delete Downloads
    • How to: Delete News Posts
  • Agents
    • Creating Agents
    • Agent Permissions
    • Permission Groups
    • Agent Teams
    • Logging in as an Agent
    • Monitoring Agents
    • Satisfaction Survey
    • Managing Agent Passwords
    • Editing Agent Profiles
    • Deleting an Agent
    • IP Whitelisting
    • Admin Access Log
  • Departments
    • Departments Overview
    • Managing Ticket Departments
    • Using Departments
    • Department Permissions
  • Email Accounts
    • Adding Ticket Email Accounts
    • Email Accounts and Triggers
    • Department/Email Links
    • Email Handling Options
    • Running an email-only helpdesk
    • Monitoring email accounts
    • Dealing with spam
  • Ticket Fields
    • Categories
    • Priorities
    • Workflows
    • Products
    • Custom fields
    • Field validation and display
    • Ticket form layouts
    • Ticket ref codes
  • Automating the Helpdesk
    • Triggers
    • Trigger examples
    • SLAs
    • Macros
    • Escalations
    • Satisfaction survey request
    • Round robins
    • Setting urgency automatically
    • Incoming Webhooks
    • Displaying IDs for items
    • Actions guide
    • Sending SMS alerts
  • CRM and usergroups
    • Usergroup permissions
    • User registration
    • Managing user passwords
    • Custom CRM fields
  • Portal
    • Basic portal settings
    • Portal branding and design
    • Customizing portal content
    • Advanced portal editing
    • Enabling Guides
  • Multi-Branded Portals
    • Setting up a New Brand
    • Feedback in Multibrand
    • Multi-Brands
    • Tickets in Multi-Brands
    • Agent Permissions in Multi-Brands
    • Ticket Triggers in Multi-Brands
    • Escalations in Multi-Brands
    • SLA’s in Multi-Brands
    • Snippets in Multi-Brands
    • Snippet Variables in Multi-Brands
    • Reporting in Multi-Brands
  • Chat
    • Chat setup
    • Multi-language chat
    • Chat departments
    • Chat queues
    • Chat embed
  • Editing Templates
    • Introducing templates
    • Twig syntax basics
    • Email templates
    • Portal templates
    • Useful template variables
    • Variables in custom phrases
  • Localization
    • Date & time settings
    • Languages
  • Deskpro Apps
    • App permissions
    • Authentication apps
    • Gravatar
    • Share Widget
    • Resolve User Hostnames
    • Google Analytics
    • Highrise
    • HipChat
    • Microsoft Translator
    • JIRA
    • Salesforce
    • Twilio SMS
    • Clickatell SMS
    • SendGrid
    • Trello
    • Zapier
  • Authentication and SSO
    • Agent and user authentication
    • Understanding SSO options
    • Auto agent
    • Grant usergroup
    • Multiple usersources
    • Filtering a usersource
    • Importing user data
    • Active Directory setup
    • LDAP setup
    • JSON Web Token setup
    • SAML setup
    • Database auth setup
    • OneLogin setup
    • Okta setup
    • Google+ setup
    • Wiacts Nopassword setup
  • Integration
    • Using web hook actions
    • Using the Deskpro API
    • Creating widgets & apps
  • Labels
    • Introduction to Labels
    • Managing labels
    • Merging labels
    • Setting label colors
    • Label permissions
  • Agent Interface Options
    • Automatic ticket locking
    • Setting ticket defaults
    • Time log and billing
    • Problems & incidents
    • Custom filters
    • Ticket archiving
    • Ticket purging
  • Anti-Abuse Options
    • Login lockout
    • Portal rate limiting
    • Email rate limiting
    • CAPTCHA settings
  • Exporting Data
    • Exporting data via API
  • Billing and Licensing
    • Cloud licensing
    • On-Premise licensing
  • Appendix
    • Deskpro Terminology

Escalations

23/03/2017 22/05/2018

Escalations run actions once a ticket has spent a set amount of time in a certain state.

They are useful to ensure that tickets are dealt with promptly. For example, you could use an escalation to increase the urgency of older tickets, or to automatically assign tickets that have gone unresolved for too long to a manager.

If you’re struggling to work out how to implement a particular automation, it’s also worth searching the Deskpro Knowledgebase, as we regularly add examples based on customer requests.

Creating an escalation

Create a new escalation by going to Tickets > Escalations and clicking Add.

Note

A new escalation will only apply to tickets that are created after you make it and after you enable it.

When you create an escalation, you define what state a ticket must be in for elapsed time to count:

auto_escalation-setup.png

  • The ticket has been open for: total time the ticket has existed without being resolved.
  • The user has been waiting: total time the ticket has been awaiting agent, continuously since the most recent status change; for example, if the status is changed from awaiting agent and then back again, the clock resets.
  • The total time the user has been waiting: cumulative time the ticket has been awaiting agent over its whole life.
  • The agent has been waiting for: how long the ticket has been awaiting user, resets if the status changes; useful to detect tickets where the user stopped replying before the problem was resolved.
  • The ticket has been resolved for: time elapsed since the ticket was resolved.
  • The ticket has been on hold for: time elapsed since the ticket has been put on hold.

You also set how long the ticket must spend in that state for the escalation to apply.

../_images/escals-length.png

You can also set extra criteria that the ticket must meet for the escalation to run. For example, if you specify a department, the escalation will apply only to tickets in that department.

../_images/automating-escalation-criteria.png

You then define the actions that run when the ticket has run up the correct elapsed time and meets any criteria.

../_images/automating-escalation-actions.png

Increase urgency after user has waited a day

This is a simple example escalation to increase the urgency of Support department tickets if the user has been waiting more than a day.

../_images/escals-example1.png

Note that, instead of setting the urgency to a particular value, we increase the urgency by 3 (up to the maximum of 10).

Follow up automatically when a user stops replying

This is an example of how you can use an escalation to send a follow-up email if a user stops replying before the ticket is resolved.

In Admin > Tickets > Escalations, make an escalation like this:

../_images/escals-auto-reminder.png

Set any criteria for the escalation. For example, you might only want to send the reminder email for tickets in the Support department.

../_images/escals-auto-reminder2.png

For the escalation action, we want, for example, to send an email to the user. None of the default templates is right, so we need to choose from custom Email templates or just create a new one.

../_images/escals-custom-template.png

Email templates are built up from the phrases in Setup > Languages. This means you can edit the phrase in a single place and have it update all the email and portal templates that include it.

If you’re only using one language on your portal, and don’t plan to enable any more in future, you don’t need to use a custom phrase - you can just enter the email text directly.

To make a suitable custom template, open another admin window and look through the templates for similar built-in emails (Tickets > Email Templates) to find phrases you can re-use.

Any custom text you need to add should be added as a custom phrase under Setup > Languages; click your main language and select Edit Phrases, then All Custom Phrases and click the Add Custom Phrase button in the top right.

Here’s an example of a custom phrase:

../_images/escals-custom-reminder-phrase.png

Create the phrase (with the same ‘filename’) in each language you have installed.

Here’s an example reminder template, referencing the custom phrase:

Subject:

{{ phrase('user.email_subjects.tickets_re') }}

Body:

{{ phrase('user.emails.greeting') }}
<br /><br />
{{ phrase('custom.ticket_reminder') }}
<br /><br />
<dp:ticket-messages />
{% if app.isPortalEnabled() %} <br /><br />
{{ phrase('user.emails.ticket_access_ticket_online') }}
<a href="{{ ticket.link }}">{{ ticket.link }}</a> {% endif %}

Now save the escalation.

Comments (0)

Add a comment

To prove you are a human, please tell us the text you see in the CAPTCHA image


Quick Jump
  • Deskpro Support
  • Knowledgebase
  • Guides
  • News
  • Downloads
  • Feedback
  • Contact Us
Top
Helpdesk software provided by Deskpro