Quick answer
A coordinator can run an MSP queue ageing review if you define what aged means for each ticket type and status, and where their authority stops. They find tickets waiting too long, identify the owner and blocking reason, ask for a next action and date, and escalate agreed triggers. They do not fix, close or reprioritise tickets.
- Define ageing before reviewing: time since creation, last update or time in a status, set per ticket type.
- Run one review by hand first to learn how many tickets are aged, and set thresholds from your own agreement.
- Have the coordinator record facts and hand technical questions, change requests and priority disputes to the person with authority.
A queue ageing review finds tickets that have waited too long for an update, identifies who owns the next step and chases it. A coordinator can run that review if you define what “aged” means and where their authority stops. This article is for MSP service managers whose old tickets stay old because nobody owns the follow-up.
An illustrative scenario
This is a hypothetical example, not a Web Design Davao client case.
A ticket sits in “waiting on customer” for nine days. The engineer assumed the customer would reply, the customer assumed the MSP was working on it, and no one has looked at it since. A weekly review by a coordinator, using a clear definition of ageing, would have flagged it on the second day past the agreed point and asked the owner for the next action.
Define ageing before reviewing anything
Ageing can mean time since creation, time since last update or time in a particular status. These tell you different things, and a coordinator cannot apply a rule that is vague. Choose a definition for each ticket type and status, in terms your service agreement and your own practice support. A ticket waiting on a customer may be allowed longer than one waiting on an engineer.
Establish the data you have. Your ticketing system may already show last-update time and status; check what it reports before building anything by hand. What you may not know is how many tickets are aged under each definition, so run the review once manually to find out before setting thresholds. Do not copy thresholds from elsewhere. They should reflect your agreement and your capacity.
What the owner follow-up looks like
For every aged ticket, the coordinator identifies the current owner and the blocking reason. They then ask the owner for the next action and a date. The coordinator does not tell an engineer how to fix the problem, and does not close or reprioritise a ticket on their own judgement. Their job is to make sure each aged ticket has a named person, a known reason it is waiting and a next step.
Some blocking reasons are simple, such as awaiting a customer reply or a part. The coordinator can follow those up with the customer under the agreed script. Others are technical, such as waiting on a vendor or an unknown cause, and go back to the engineer or service manager. In the scenario, the coordinator contacts the customer, records that they were waiting for the MSP, and returns the ticket to the engineer’s list with a note.
Escalation reporting
Decide what reaches the service manager and when. Typical triggers are a ticket aged beyond the escalation threshold, an owner who has not responded, or a pattern across several tickets for one customer. The report should state the ticket, how long it has aged under the agreed definition, the owner, the blocking reason and what has been tried. It should not include conclusions about cause or blame.
Record the outcome so the next review can see it. If a ticket is escalated and the service manager decides to leave it, that decision and the reason are recorded too.
Queue review worksheet
Use one worksheet per review, weekly or at whatever rhythm you set. The coordinator completes it; the service manager reviews exceptions. A completed row shows that an aged ticket has an owner, a reason and a next step, or that it was escalated. It does not show that the underlying problem is resolved.
Blank copy
| Ticket | Age definition | Current owner | Blocking reason | Next action | Escalation |
|---|---|---|---|---|---|
Illustrative completed row (hypothetical)
| Ticket | Age definition | Current owner | Blocking reason | Next action | Escalation |
|---|---|---|---|---|---|
| Ticket for a customer’s printer fault | No update for more than the agreed days while “waiting on customer” | Engineer on the account | Customer believed MSP was working on it | Coordinator calls customer, confirms details, returns ticket to engineer with date | None needed; reported in weekly summary |
Where a coordinator should stop
If the review shows a technical question, a request for a change or a conflict with the customer, the coordinator does not resolve it. They record the facts and hand it to the person with authority. If a ticket’s priority seems wrong, they raise it with the owner of the priority rule rather than changing it.
Your next action
Run one review by hand on this week’s queue, using a single definition of ageing. Note how many tickets have no clear owner or reason. That number tells you how much a coordinator would take on.
To discuss a coordinator role, the skills, working hours and review responsibilities, speak with Web Design Davao. Arrangements are agreed individually.
How Web Design Davao works
- Enquiries are generally answered within four hours during support hours (Monday to Friday, business hours), with after-hours help for emergency requests. Scope is agreed individually.
- Web Design Davao employs and manages its Davao-based staff, including HR administration and payroll, and provides them as an outsourced service to companies overseas. See how staff are managed and how staff are hired.
Frequently asked questions
What does an aged ticket mean in an MSP queue?
It depends on your definition. Ageing can mean time since creation, time since last update or time in a particular status. Choose a definition for each ticket type and status that your service agreement supports, because a coordinator cannot apply a vague rule.
What should a coordinator do with an aged ticket?
Identify the current owner and the blocking reason, then ask the owner for the next action and a date. Simple reasons, such as awaiting a customer reply, can be followed up under the agreed script. Technical ones go back to the engineer or service manager.
What should reach the service manager?
Typical triggers are a ticket aged beyond the escalation threshold, an owner who has not responded, or a pattern across several tickets for one customer. The report states the ticket, its age, owner, blocking reason and what has been tried, without conclusions about cause or blame.