The Agent Who Is Not on the Payroll
A ticket here can only be assigned to an employee record. That is fine until you notice how many of the people who actually answer tickets are not employee records — the owner, the systems administrator, the agency covering nights, the contractor on a six-month engagement.
The short version
If your support desk is staffed by anybody other than your own payrolled staff, check how your system models an assignee before you check anything else about it. Assignment that runs through an employment record is a reasonable design and a quiet constraint, and it is the kind of constraint that only shows up on the day you try to hand a ticket to the person covering the weekend.
Two things in a business system look interchangeable and are not: a person who works here and a person who can log in. Most of the time they overlap so heavily that nobody has to think about it. A support desk is one of the places where they come apart.
Here, a ticket is assigned to an employee record. The system also keeps a note of that employee's login, but you do not choose the login — it is copied across from whichever employee you picked. Every list, filter and count follows from that one decision.
The people who cannot be given a ticket
Anybody with a working account and no employment record. They can sign in, they can hold every permission you grant them, they can read the queue, reply, close and reopen. They cannot appear in the assignee list, because the list is built from employees.
That set is larger than it sounds, and it is worth naming the people in it:
- The owner or director who answers the difficult ones personally, and who is often not on the payroll as an employee in the system's sense.
- The systems administrator who set the workspace up and holds the most permissions of anybody in it.
- An outsourced or agency desk covering evenings, weekends or a language you do not staff internally.
- A contractor on a fixed engagement, given a login for the duration and deliberately never entered into HR.
- A colleague in a shared service centre belonging to a sister company in the group.
Every one of those is an ordinary way to staff a desk, and several of them are the normal way to staff one outside of a large in-house team.
The queue is visible to them, the work is doable by them, and the ticket cannot be put in their name.
And the mirror image, which is stranger
The rule runs the other way too, and produces something odder. An employee record does not have to have a login attached — plenty of people who work for you have no reason to sign in to anything, and the system is right to allow that.
Such an employee can be assigned a ticket. The assignment saves and the ticket shows their name. What does not happen is the note of their login, because there is not one.
And the "my tickets" view — the screen every agent actually works from — is built on that note rather than on the employee. So a ticket assigned to an employee with no account is assigned, is visible on the ticket itself and in the queue, and appears in nobody's personal list. It is not lost. It is just not in front of anyone.
Where the two records diverge
Employment record
What assignment is built on
- Chosen from the assignee list
- Shown on the ticket
- Counted in queue statistics
- May exist with no login attached
Login account
What "my tickets" is built on
- Copied from the employee, never chosen
- Drives the personal work list
- Drives the "assigned to me" count
- May exist with no employment record
A person sitting in both columns — most of your staff — never encounters any of this. The behaviour only becomes visible at the two edges, and the edges are where contractors, agencies, owners and non-computer-using staff live.
Why a design like this happens, and why it is defensible
Not by accident. Routing work to an employment record is the right call for most of what a business system does, because it is the record that knows about departments, managers, working patterns, leave and cost. Assigning work to a login instead would mean the desk could not answer "who is on leave", "whose team is this", or "what does this person cost".
The trade is that the desk inherits the employment model's boundary. Everything HR knows about, the desk can route to. Everything HR does not know about, it cannot — and a support function is unusually likely to be staffed from outside HR's view.
The honest way to describe it is not "assignment is broken". It is: assignment is a question about employment, and your desk may not be.
Working with it as it stands
-
Create employment records for the people who answer tickets
Including the contractor and the agency lead. This is the workaround and it is a real one — the record does not have to imply anything about employment terms, and it makes the person routable, reportable and countable.
-
Link a login to every one of them
The step people skip, and the one that decides whether the ticket lands in a personal work list or only in the queue. An employment record with no account attached is assignable and invisible.
-
Check the unassigned count means what you think
A ticket counts as unassigned only when neither the employee nor the login is set. A ticket assigned to an accountless employee is not in that count and not in anybody's list, which is the one place a ticket can genuinely go quiet.
-
Audit the queue by assignee once a month
Fifteen minutes, and it catches both edges: work parked with somebody who left, and work parked with somebody who cannot see it.
What AWRA OpsHub does today
- Assignment to an employee record, with the queue, the counts and the ticket itself all reading from it consistently.
- A personal work list per agent, driven by the linked login, so an agent opens one screen rather than filtering the queue.
- Department queues as well as individual assignment, so work can sit with a team before it sits with a person.
- An unassigned view and count, treating a ticket as unassigned only when neither the employee nor the login is set.
- A per-category service clock, choosing between elapsed time and your organization's working hours, so a Thursday evening ticket is measured the way your business actually operates.
More we can add to your workspace
- Assignment to a login that has no employment record, so an owner, administrator or outsourced agent can hold a ticket in their own name.
- A personal work list for an employee with no linked account, which is the one route by which an assigned ticket reaches nobody's screen.
- Round-robin or load-balanced routing, so a new ticket picks its own owner from a rota.
- An escalation engine, moving a ticket up a chain on its own when a clock runs out.
- A warning at the point of assignment when the chosen person has no login, which is the cheapest of these and catches the quiet failure.
Where we point you to a specialist
- Routing work through the employment record stays the right default and we would keep it. It is what lets the desk know about departments, managers and leave, and an assignee model built on logins alone would give that up for a narrower kind of flexibility.
- Whether an agency contractor should hold an employment record in your systems is a question for your own HR and data-protection practice. We make the record possible; deciding who belongs in it is yours.
- We would push back on routing tickets to a shared or generic login as a way around this. A queue owned by everybody is owned by nobody, and it is the failure mode a personal work list exists to prevent.
Assignment to any account, a warning on an unreachable assignee, and rota-based routing are scoped work we can quote on.
Three, in the order they are worth doing
The second one is the cheapest and prevents the only genuinely silent failure described on this page.
Assignment to any account
An assignee list that includes logins without an employment record, so an owner, administrator or outsourced agent can hold a ticket in their own name, be counted in the queue statistics, and see it in their own work list.
A warning on an unreachable assignee
A note at the point of assignment when the chosen person has no login — so the ticket still routes, and the person routing it knows it will stay off every personal work list.
Rota and load-based routing
A new ticket picking its owner from a rota or from who currently has the least open work, rather than waiting for a person to distribute the queue by hand each morning.
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 any part of your desk is staffed from outside your own payroll, the first item is the one to raise.
Talk to us about your support deskThree questions for any help desk you are evaluating
Can a contractor with a login be assigned a ticket?
What you will hear
Yes, usually said quickly.
How to read it
Ask them to do it in front of you with an account that has no HR record behind it. This is a two-minute test and it separates the products that model an agent from the products that model an employee.
What happens to a ticket assigned to somebody who cannot log in?
What you will hear
Rarely considered.
How to read it
The answer you want is a refusal or a warning. The answer you will often get is that it saves silently, which is ours today, and it is the one way a ticket leaves the queue without reaching a person.
Does the unassigned count include tickets nobody can see?
What you will hear
A pause.
How to read it
Worth the pause. An unassigned count is the number most desks manage by, and a ticket that is technically assigned and practically invisible is excluded from it — which is precisely backwards.
List everybody who answers a ticket
Then check how many of them are employment records in your system. If the two lists differ, the difference is the part of your desk your reporting cannot see.
Talk to us about helpdesk routing