Nobody Is Next
When a ticket breaches, this product tells the agent, then their manager, then the department. What it never does is decide who should have had the ticket in the first place — and a notification after the deadline is not an escalation.
There is a question every support desk answers a few hundred times a day, and most of them answer it with a person: who takes this one?
At five tickets a day that person is fine. At five hundred, the answer is the whole system, and the fact that a human is producing it is the constraint on everything else.
What is not here
No round-robin. No load-based assignment. No skills routing. No queue that hands the next ticket to the next available agent. Assignment is a person choosing from a list, every time, for every ticket.
And no escalation engine — nothing that watches a ticket approaching its deadline and changes anything about it.
What is here, and why it gets mistaken for escalation
There is a recipient chain that fires when a ticket breaches. It notifies the assignee if they have a login. It notifies the assignee's manager, looked up through the employee record so that it works even when the agent has no login of their own — which matters, because this product was built for organisations where many staff do not.
And if neither of those produced anybody, it falls back to everyone in the ticket's department. A fallback rather than an addition, deliberately: telling a whole department every time a named agent runs late is how an alert becomes a mail rule.
That is a good chain and it is carefully built. It is not escalation. It runs after the deadline has passed, and it moves information rather than work.
Where a desk sits between telling and doing
Breach is recorded
A field on a ticket. Reportable afterwards.
Breach notifies the assignee
Someone is told, after the fact.
Breach notifies upward
Where this product sits.
Warning before the deadline
The first point at which the outcome can change.
Automatic reassignment
Work moves, not just information.
Assignment by load or skill
The ticket never sat unowned to begin with.
Everything left of the middle is a description of a failure. Only the right-hand half prevents one.
An alert on breach is a very fast way of finding out you have already lost. Escalation is what happens while there is still time to win.
Why volume is the thing that breaks it
Manual assignment does not fail gradually. It fails at a threshold, and the threshold is when the person assigning stops being able to hold the state of the queue in their head.
Below it, a human is genuinely better than a rule — they know who is good at what, who is drowning, and which customer is about to escalate for reasons no field records. Above it, they assign to whoever they thought of, which is usually the same four names, and the tickets nobody thought of sit unowned.
The unowned ticket is the one that matters here, because it is both the most likely to breach and — until the department fallback was built — the one whose breach alarm was wired to nobody.
One morning, 180 tickets, four agents, one supervisor assigning
Illustrative. The last row is the argument: manual assignment is not free, it is a salaried person doing arithmetic every morning forever.
What to do without a rule engine
-
Assign at intake, not in a sweep
Whoever triages picks an owner in the same action. A queue that is assigned in batches has a period every day where the clock runs on unowned work.
-
Make the department fallback real
Every ticket should have a department even when it has no assignee, because that is the only thing standing between an unowned breach and an alarm with no recipient.
-
Choose the SLA clock per category deliberately
Business hours or elapsed, set on the category. This is the one genuine lever available, and most desks never touch it.
-
Watch the unassigned count as a number, daily
Not a feeling. It is the leading indicator for every breach you will have tomorrow, and it is the number a rule engine would have driven to zero.
Two, and the cheap one changes more than the expensive one
The recipient chain, the deadlines and the per-category clocks all already exist. What is missing is anything that acts before the deadline rather than after it.
A warning before the deadline, not only on it
A threshold — say seventy-five per cent of the target elapsed — that fires the existing recipient chain while there is still time to act. This reuses everything already built and is the single largest change in outcome per unit of work anywhere in the helpdesk module.
Assignment by rule, then escalation by rule
Round-robin or load-based assignment at intake, and a rule that reassigns or raises priority when a ticket approaches its deadline unowned. This is the real engine, it is a larger piece of work, and it is only worth it once volume has passed the threshold where a person cannot hold the queue.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. If your desk is above a few hundred tickets a day, start with the first item.
Talk to us about routing and escalationWhat AWRA OpsHub does today
- Manual assignment to an agent or a department, and a dual assignee so an agent without a login can still own a ticket.
- A breach recipient chain — assignee, then their manager through the employee record, then the department as a fallback when neither produced anybody.
- Two independent deadlines, first response and resolution, each with its own alert and its own notified marker.
- A per-category SLA clock, elapsed or business hours.
- An alert that is retried rather than marked handled when it reached nobody.
What it does not do
- Round-robin, load-based or skills-based assignment of any kind.
- Any escalation engine. Nothing changes a ticket's owner, priority or queue automatically, ever.
- Any warning before a deadline. Every alert in the module fires on or after breach.
- Agent availability, capacity or working-hours awareness in assignment.
- A rule builder for the helpdesk specifically.
Not ours, by choice
- The recipient chain is genuinely good and we would defend it — particularly the manager lookup that works for agents without logins, and the department fallback being a fallback. It is not escalation, and calling it that would be the misrepresentation this page exists to avoid.
- Manual assignment is better than a rule below a certain volume, and we would say so to a small desk rather than sell them an engine.
- Nothing here is Nigerian or Ghanaian. Lagos and Accra are here because volume is the variable that breaks manual assignment, and these are markets where a single desk can carry a great deal of it.
Our position
Below a few hundred tickets a day, assign by hand and spend the effort on making sure every ticket has a department so no breach is wired to nobody. Above it, a person assigning is a full-time job that produces no output, and the honest answer is that this product does not yet remove it — a pre-deadline warning would be the first thing to build and it would change more than an assignment rule.
Four questions about routing
Does anything fire before a deadline?
A good answer sounds like
Yes, at a threshold.
What it actually means
The question that separates escalation from notification. Ours answers no.
What assigns a ticket if nobody does?
A good answer sounds like
A rule, or an honest nothing.
What it actually means
"It goes to a queue" means nothing assigns it. Ask what the queue does next.
Who is told when an unassigned ticket breaches?
A good answer sounds like
A department, by fallback.
What it actually means
The commonest hole in any helpdesk, and it was ours until it was fixed.
Can an agent without a login own a ticket?
A good answer sounds like
Yes, and escalation still works.
What it actually means
Matters more than it sounds anywhere a lot of staff have no company account.
Count the unassigned, every morning
It is the leading indicator of tomorrow's breaches, it costs nothing to watch, and it is the number any routing engine you eventually buy will be judged on.
Talk about support operationsFrequently asked questions
Can workflow rules assign a ticket?
Workflow rules exist in the product and are worth exploring with us for your specific case, but there is no helpdesk assignment engine and nothing that acts on a ticket approaching its deadline. Treat assignment as manual when you plan the desk.
Does priority do anything automatically?
It is a field you can filter and report on. It does not change a deadline, reorder a queue or trigger anything by itself, which is worth knowing before you build a process around it.
Is the manager notification reliable if the manager has no login?
The manager is resolved from the employee record and then needs a user account to receive the notification. The lookup works either way; the delivery needs somebody with a login somewhere in the chain, which is exactly why the department fallback exists.
