At about 8 desk people, the model calls for a service manager or working lead. It adds dedicated dispatch around 10. Define team lead responsibilities between those points as real work with authority and cover, while the lead still belongs to the technical pool. Count desk people, not everyone on payroll.
I'd start with what the lead can decide when a ticket needs an owner. Give them authority to move work within the agreed priority rules, then state which decisions need management. The new title comes without a second pair of hands.
Give the Lead Control of the Next Assignment
Below the dedicated-dispatcher point, the model has a team lead dispatch from the pool. That means someone must watch assignment decisions while also contributing technical work. Make that responsibility visible rather than expecting the most experienced technician to notice every unowned ticket.
Queue orchestration isn't a job description. State who assigns the next ticket and who can change the assignment. A technician needs to know whether the lead's direction settles the decision or merely starts another conversation with the owner.
Set the priority rules before a conflict arrives. Base the lead's decision on the agreement and the recorded business impact. Where those rules don't settle the conflict, identify the manager who can decide instead of having the lead negotiate policy while a client waits.
Keep the assignment record in the PSA. A side message can explain the decision, but the ticket still needs its accountable person and next action. The point is to let the next colleague understand the work without finding the lead first.
Write the Working Lead’s Checklist
Use a short role sheet that names the lead's responsibilities and the boundary of each one. The owner approves the authority it grants. Match the sheet to the people actually available on your desk rather than adding a separate title for every task.
| Responsibility | Named Owner and Action | Authority Boundary |
|---|---|---|
| Assignment | The working lead assigns unowned tickets and records the next responsible person. | The lead follows the agreed priority and coverage rules. |
| Reassignment | The working lead moves a ticket when the assigned person cannot complete the next step. | The lead records the reason and confirms the receiving technician can take it. |
| Technical Escalation | The assigned technician records the investigation and asks the technical escalation owner for the required help. | The escalation owner decides technical direction within their competence and authorization. |
| Blocked Work | The working lead identifies the missing decision and sends it to the person who can make it. | The service manager handles exceptions beyond the lead’s delegated authority. |
| Coaching | The working lead identifies a repeatable skill or process gap and arranges practical guidance. | The service manager retains the formal people-management decisions assigned to that role. |
| Client Updates | The ticket owner keeps the promised client update current. | The account owner handles relationship or commercial decisions outside the ticket. |
| Absence Cover | The service manager names the backup lead and confirms the handoff. | The backup receives the necessary access and delegated authority before covering. |
A small desk may give the same person technical escalation and dispatch duties. Write both down anyway, because one can interrupt the other. Don't assume that appointing the strongest engineer makes the work compatible with their existing ticket load.
Paul Green questions whether a service desk manager must be a technician and emphasizes resource planning and communication. That's his role-design suggestion, rather than a rule for choosing your working lead. Assess the actual assignment and coaching duties instead of treating technical seniority as a complete selection process.
Make an Escalation a Handoff Someone Can Use
Keep responsibility explicit when a technician asks for help. If the original technician remains the ticket owner, say so and identify what they must do after receiving advice. If ownership transfers, change the PSA assignment and confirm that the receiving person accepts the work.
Require enough investigation detail to support the next decision. The technical lead can then distinguish a missing skill from missing access or an external dependency. Reassigning the ticket without that distinction can move the delay without resolving it.
Give the working lead a way to decline an interruption that belongs elsewhere. They can route the request to its proper owner and preserve the current assignment. They don't have to become the default owner of every unanswered question merely because they can usually help.
Keep incident leadership separate when the situation requires it. Nick and Jeni Clift distinguish incident direction from technical remediation and ordinary business operations. In their practitioner advice, the incident lead needs to focus on that work; your ordinary desk still needs someone accountable for its queue.
Test the Role Against Available Time
Put the lead's technical commitments beside the dispatch cover they must provide. Identify which tasks can pause and which cannot. A lead in an agreed client change needs someone else to make urgent assignment decisions during that work.
The model's smaller pooled desk absorbs lead dispatch without another person, a stipend, or extra minutes in its calculation. That's a modeling choice, not proof that your dispatch work takes no time. Observe the interruptions in your own desk before setting the lead's remaining technical expectations.
Don't invent a fixed ticket target for the new lead from their old technician output. First record which responsibilities have moved to them and what technical work remains. Check the work displaced by coordination rather than judging the lead as if nothing changed.
James Bier recommends making the next role and agreed progression criteria visible to technicians, while recognizing that some want to stay in their current role. Use that practitioner advice when discussing the appointment. A person can be a valuable senior technician without wanting responsibility for other people's work.
Separate the Dedicated-Dispatch Decision
At about 10 desk people, inspect the dedicated-dispatcher role the model adds. It is a different decision from naming a working lead around 8. Don't describe that point as an automatic requirement to make every technical lead a full-time manager.
List what would move from the working lead to dispatch and what stays with technical escalation. Check that the intended dispatcher has a complete job and reliable cover. Keep technical judgment with a person equipped to make it, rather than transferring every unresolved ticket with the scheduling duties.
A larger title doesn't settle the handoff. The technician still needs to know who decides assignment and where technical help comes from. Publish the changed decision route when you move the duties, then check that the board reflects it.
Keep account management outside this job. The model separates the managed relationship from service management. The lead should know how to route a commercial issue without accepting a new client commitment on the desk's behalf.
Check What the Board Does Differently
My test for the role is simple: what does this do to the board on Monday morning? The answer should identify a decision someone can now make or a handoff someone can now complete. A new title alone doesn't provide either.
Use the existing board to inspect unclear assignments and tickets waiting for technical help. Record why each was blocked before treating it as evidence that you need a new person. A missing permission needs an authority decision, while a genuinely unavailable skill needs a different response.
Before appointing the lead, agree the role sheet and name the backup. Walk through an assignment conflict using your actual priority rules. Then adjust the technical work allocated to the lead so the responsibilities you just assigned can be carried out.
mspoutpost.com/articles/team-lead-responsibilities-at-an-msp-service-desk
Written by Megan Friesen
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.