A service manager's daily and weekly routine

Three passes through the day

At the start of the shift, review incidents, urgent unowned work, callbacks already promised and tickets approaching your agreed response or resolution boundary. Compare that work with the people available today. Leave, site visits and project bookings belong in this check.

Keep the opening pass short enough that dispatch can start assigning work. Adam Hannemann makes the case for a separate triage step.^[2] A ticket needs an impact, enough context to start and a receiving owner. "Oldest" is a useful sort order, but age alone does not determine urgency.

Around the middle of the day, look for changes: a new absence, a client reply that changes impact, or an escalation with no next step. Keep stable assignments stable. When work moves, the receiving owner should accept the handoff instead of finding an unexplained ticket in their queue.

Before the shift ends, check commitments due before the next queue review. Confirm the client knows the next step and the after-hours owner can find the context. Use a secure access reference when needed; ordinary ticket notes should contain no credentials.

A fictional queue note

Ticket S-142 has a callback promised before 11:00. The assigned engineer is on an onsite visit until noon. Dispatch will confirm a callback window with the client and assign the available engineer. The service manager will check the handoff at the midday pass.

That is a usable action. "Watch aging tickets" is a concern with no owner or completion test.

Once a week, stop dispatching long enough to manage

Group repeat faults, reopened work, escalations and missed commitments. Choose a specific investigation: "Why did the finance application's update produce repeat tickets, and did the deployment check miss a dependency?" Bring the previous investigation back before opening another one.

Include the team's working conditions. Does the same engineer absorb every escalation? Is project work borrowing the person who covers the queue? Who needs training or a clearer standard? The MSP KB describes different desk structures.^[1] Use the duties your team actually has, rather than copying an organization chart. Adam's service-manager role discussion also extends beyond being the senior technician.^[3]

In Autotask, ConnectWise PSA or HaloPSA, start from ticket ownership, status, priority, promised dates and time-entry coverage. Verify your version's fields and views. Autotask's documented time-entry fields include work date, hours and ticket/task references.^[4] Join by reference rather than matching free-text ticket titles. Keep private management notes outside client-visible service records.