Support handling has routine parts that can be automated, and issues that need more attention, which can be escalated. This piece is about ticket automation and escalation in Odoo Helpdesk.
The edition note
Ticket automation and escalation are part of Odoo Helpdesk, an Odoo Enterprise application, not in Community. This piece describes them as they work in the Helpdesk application.
Ticket automation: handling the routine
Some of the handling of support tickets is routine and repeatable, the routine steps in how tickets are processed, things that do not genuinely need a person's judgement each time. Ticket automation is the automating of that routine handling: routine steps in processing tickets made to happen automatically, so they do not have to be done by hand each time. Ticket automation handles the routine, repeatable part of support, so the support team's attention goes to the part that genuinely needs them, the genuine resolving of customers' issues.
The honest limit of automation
As with automation everywhere, the honest limit applies: ticket automation is for the routine, not for the genuine work of support. The genuine resolving of a customer's issue, understanding it, addressing it, often communicating with the customer, needs people, their judgement, their genuine attention. Automation should handle the routine steps around that, not try to replace the genuine support work. A customer whose issue is handled entirely by automation, with no genuine human attention, is poorly served. Ticket automation, used well, frees the support team for the genuine work; used to try to automate the genuine work, it does not serve customers.
Ticket escalation: issues that need more
Escalation is, in a sense, the opposite of automation: it is the recognising that some issues need more attention, not less. Some support issues are not resolved at the level they were first handled, or are taking too long, or are genuinely difficult, and they need to be escalated, raised to a higher level of attention, to someone more senior, more specialised, more able to resolve them. Ticket escalation in Odoo Helpdesk is the means by which an issue that needs more attention is escalated, so it gets it.
Why escalation matters
Escalation matters because, without it, an issue that needs more attention can simply sit, unresolved, at a level that cannot resolve it, with the customer left waiting. Escalation ensures that an issue that is not being resolved, or is genuinely difficult, or is breaching its SLA, is raised to where it can be dealt with, rather than being stuck. Escalation is, in particular, connected to SLAs: an issue at risk of breaching its SLA is a candidate for escalation, so it gets more attention before the standard is breached. Escalation is how a support operation makes sure the issues that need more genuinely get more.
Automation and escalation together
Ticket automation and escalation together help a support operation direct its attention well. Automation handles the routine, so attention is not consumed by it. Escalation makes sure the issues that need more attention get it. Between them, they help support attention flow to where it is genuinely needed: not consumed by routine, and concentrated on the difficult issues that need it. Used well, within the honest limit on automation, they make a support operation more responsive and better at resolving the issues that matter.
The takeaway
Ticket automation and escalation in Odoo Helpdesk, part of the Enterprise Helpdesk application, help a support operation direct its attention. Ticket automation handles the routine, repeatable parts of processing tickets, within the honest limit that it is for the routine, not the genuine support work. Ticket escalation raises issues that need more attention, the unresolved, the difficult, the SLA-at-risk, to where they can be dealt with. Together they keep support attention flowing to where it is genuinely needed. For how we approach Odoo, see our ERP practice.