Quick answer
Before hiring another engineer, delegate rule-based dispatch work to a dispatcher: checking that tickets have a contact and affected service, applying written priority rules, assigning to the rostered engineer and sending routine updates. Keep technical decisions, such as diagnosing a fault or resetting a password, with qualified staff. If a rule is not written down, write it first.
- Note each action a ticket goes through for one or two weeks, and who did it, to size workload.
- Name who acts next for each delegated task, including what the dispatcher does when a ticket cannot be assigned.
- Complete a scorecard row per task with action, skill, permission, escalation and reviewer; no reviewer means not ready.
If your engineers spend part of each day assigning tickets, chasing updates and confirming who is on a job, that coordination work can often move to a dispatcher. Technical decisions should not. This article is for MSP owners and service managers, and it helps you decide which dispatch tasks to delegate before you add another engineer.
An illustrative scenario
This is a hypothetical example, not a Web Design Davao client case.
A small MSP has four engineers. Each morning the most senior engineer reads the new tickets, decides who takes what, and messages customers who have not given enough detail. By mid-morning that engineer has done an hour of coordination and no engineering. The service manager wants to hire a fifth engineer. Before doing so, she lists every task in the dispatch routine and asks of each one: does this need technical judgement, or does it need a clear rule and someone who follows it?
Start by sizing the dispatch workload
Write down what actually happens to a ticket between arriving and being picked up. For one or two weeks, note each action, who did it and roughly how long it took. You are looking for repeated, rule-based work: checking that a ticket has a contact and an affected service, applying the priority rules your customer agreement already sets, assigning to the engineer on the roster, and sending routine status updates.
Establish three things first. What inputs does the person doing this task already have, such as the ticket, the roster and the customer’s priority rules? What do they have to decide? And what is unknown, for example how often a ticket arrives with too little information to route? If you cannot describe the inputs, the task is not ready to delegate.
Draw the technical boundary
Dispatch and coordination are distinct from engineering judgement. A dispatcher can follow a rule that says a ticket marked as a full outage for a named service goes to the on-call engineer. A dispatcher should not decide what is causing the outage, or whether a customer’s request is safe to action.
Two things move a task across that line: the skill it needs and the permission it needs. Reading a ticket and applying a written routing rule needs neither deep technical skill nor elevated access. Resetting a password, changing a firewall rule or deciding that a fault is low risk needs both, and those stay with qualified staff or with whoever your processes authorise. Priority rules belong to the client agreement, not to the dispatcher’s opinion. If the rule is not written down, write it down before delegating, or leave the decision with the person who owns it.
Where a task could move either way, ask for the evidence an engineer would want before taking it over. For example, an escalation should arrive with the symptom as the customer described it, the affected service, the time it started and the contact to call back. That is evidence a dispatcher can gather without diagnosing anything.
Make handoff ownership explicit
For each delegated task, name who acts next. A dispatcher assigns a ticket; the engineer accepts it; the service manager reviews the pattern weekly. If a ticket cannot be assigned, say because the roster is empty or the customer has not responded, define what the dispatcher does: contact the named escalation person, record why, and do not guess.
Treat the blocked case as part of the design. In the scenario, a ticket arrives from a customer whose service is not on the agreed list. The dispatcher cannot route it by rule. The correct handling is to flag it to the service manager with the ticket details, not to pick an engineer and hope.
Dispatch role scorecard
Use this scorecard before you hire. Fill it in with the service manager and one engineer, once per role you are considering. Review it again when your processes or tools change. A completed row shows that a task has an approved action, a stated skill and permission requirement, an escalation route and a named reviewer. It does not show that the person doing it is competent; that is a separate check.
Blank copy
| Dispatch task | Approved action | Required skill | Permission | Escalation | Reviewer |
|---|---|---|---|---|---|
Illustrative completed row (hypothetical)
| Dispatch task | Approved action | Required skill | Permission | Escalation | Reviewer |
|---|---|---|---|---|---|
| Route new priority-one ticket | Assign to on-call engineer from the roster and message the customer contact that the ticket is assigned | Reads tickets and follows a written priority rule | Can assign tickets; no access to customer systems | If no on-call engineer responds within the agreed time, call the service manager | Service manager, weekly sample of routed tickets |
The service manager maintains the scorecard. If a task has no reviewer, it is not ready to delegate.
Where you will not have the answer
Some rows will stall. You may not know whether a task needs a permission you are unwilling to grant, or whether your customer agreement actually covers a type of request. Do not fill the gap with an assumption. Take the question to whoever owns the agreement or the system, record the answer, and update the row.
Your next action
Pick the five most frequent coordination tasks from your own queue and complete a scorecard row for each. Any row you cannot complete shows where your process needs a written rule before anyone, offshore or in-house, can own it.
If you want to talk through a dispatch role, the skills it needs, working hours and how review would work, you can discuss it with Web Design Davao. Roles and working arrangements are agreed individually; nothing here assumes a particular role is already available.
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
Which service desk tasks can a dispatcher take on?
Repeated, rule-based work: checking a ticket has a contact and an affected service, applying priority rules your customer agreement already sets, assigning to the engineer on the roster and sending routine status updates. Each needs a written rule and a named reviewer.
What should stay with engineers?
Anything needing technical judgement or elevated access, such as deciding what is causing an outage, resetting a password, changing a firewall rule or judging a fault low risk. Priority rules belong to the client agreement, not the dispatcher’s opinion.
What if a ticket cannot be routed by rule?
The dispatcher flags it to the service manager with the ticket details, records why and does not guess an engineer. An example is a ticket from a customer whose service is not on the agreed list.