Building a Ticket Intake Checklist for an Outsourced MSP Dispatcher

A practical intake checklist that turns vague support requests into tickets a dispatcher can route and an engineer can act on.
Share:
A coordinator routes a checked ticket through a funnel to three technical staff.

On this page

Is your website helping your business?

Let’s find opportunities to make it work harder for you.

Quick answer

A ticket intake checklist lists the minimum information a ticket needs before a dispatcher routes it: who is asking, the affected service, the business impact, the observed symptom, a way to call back and who owns the next step. Each field should change what happens next, and a ticket missing any field is not ready to route.

  • Count how often tickets arrive missing each item for a couple of weeks, then put the most-missed questions first.
  • Dispatchers apply written priority rules and must not assume the cause or downgrade a ticket because the requester sounds calm.
  • If the requester cannot be reached, route to the named owner with a note of what was tried.

A ticket intake checklist lists the minimum information a ticket needs before a dispatcher routes it: who is asking, what service is affected, the business impact, what was observed, how to reach the requester, and who owns the next step. This article is for MSP owners and service managers who want vague requests fixed at the door, not by an engineer later.

An illustrative scenario

This is a hypothetical example, not a Web Design Davao client case.

A message arrives in the support queue: “Email isn’t working, please fix.” There is no name beyond an address, no indication whether it affects one person or the whole office, and no phone number. An engineer picks it up, spends ten minutes working out who is asking and what is wrong, and then discovers the problem is one user’s mailbox. A checklist at intake would have asked those questions first, and routed the ticket accordingly.

Minimum ticket context

Decide the least a ticket must contain to be routable. For most service desks that is the requester, the affected service, the business impact, the observed symptom, a way to call back and the person or queue it is routed to. Establish first which of these your ticketing system can capture as structured fields, and which will arrive as free text that the dispatcher has to extract. What you do not yet know is how often tickets arrive missing each item. Count that for a couple of weeks and you will know which questions to put first.

Keep the checklist short. Each field should change what happens next. If an item does not alter routing or the engineer’s first action, it belongs in a later step.

Priority routing

Priority is a decision your client agreement and your own service rules govern, so the dispatcher applies the rule and does not set it. The business impact and the observed symptom are the inputs. “One user cannot open attachments” and “no one in the office can send email” may share a symptom but not an impact, and your written rules should send them to different places.

State clearly what the dispatcher must not assume. They should not assume the cause, should not assume that a similar earlier ticket has the same fix, and should not downgrade a ticket because the requester sounds calm. If the information needed to apply the rule is missing, the next step is to ask for it, not to choose a priority.

Missing-information follow-up

When a ticket fails the checklist, define who follows up and how. The dispatcher contacts the requester using the callback details, asks only for the missing items, and records the attempt. If the requester cannot be reached, the ticket goes to the named routing owner with a note of what was tried, so someone makes a decision instead of the ticket sitting.

Set a rule for how many attempts and over what time before escalation, and keep that rule with the service manager. In the scenario, the dispatcher phones the number on the account, learns that only one person is affected, records the symptom as the requester described it, and routes the ticket at the matching priority.

Ticket intake checklist

Fill in one per ticket, at the point a request enters the queue. The dispatcher completes it; the service manager reviews a sample each week. A completed record shows that the ticket had enough context to route, not that the diagnosis is right.

Blank copy

Requester Affected service Business impact Observed symptom Callback details Routing owner
           
           

Illustrative completed row (hypothetical)

Requester Affected service Business impact Observed symptom Callback details Routing owner
Front-desk user at a customer office Email, one mailbox One person cannot send; others unaffected “Message stays in outbox” as described by the user Direct number confirmed by phone Standard queue, next available engineer

If any field is blank, the ticket is not ready to route. Use the follow-up rule above.

Where the checklist runs out

Some tickets will not fit. A requester may refuse to give a callback number, or describe something that touches security or a change that needs authority. The dispatcher does not guess or try to resolve it. They pass the ticket to the routing owner with what they have, and say plainly what is missing. Technical and security decisions stay with qualified staff.

Your next action

Take the last twenty tickets that needed a follow-up question, and note which of the six fields was missing. Make those fields mandatory first.

To discuss a dispatcher role, the skills involved, working hours and how review would work, talk to 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 information must a support ticket have before it is routed?

The requester, the affected service, the business impact, the observed symptom, callback details and the routing owner. Each field should change routing or the engineer’s first action. If any field is blank, the ticket is not ready to route and the dispatcher follows up.

Who sets ticket priority, the dispatcher or the service rules?

The dispatcher applies the rule; they do not set it. Your client agreement and written service rules govern priority, using business impact and the observed symptom as inputs. If the information needed is missing, the next step is to ask for it, not choose a priority.

What happens when a requester cannot be reached?

The ticket goes to the named routing owner with a note of what was tried, so someone makes a decision instead of the ticket sitting. The service manager sets the rule for how many attempts and over what time before escalation.

Related reading

MORE IDEAS FOR YOUR NEXT STEP

Keep exploring.

Ready for a website with a clearer purpose?

Let’s talk about what your business needs next.

Secret Link