Why dispatch is different in Thread

Dispatch has always been the same three jobs: figure out what a request actually is, decide how urgent it is, and get it to the right person before it goes stale. Thread doesn’t remove those jobs — it moves where they start. In most service desks the dispatcher is the first human to touch a raw request and has to gather the details before anything can be routed. In Thread, that first touch has already happened.

​

The Triage Agent works intake before you do

The Triage Agent is conversational AI that responds to every new chat and email request the moment it arrives, 24/7. By the time a thread reaches your board, it has usually already:

• Replied instantly, so the customer isn’t waiting on a human to say “we’ve got it.”
• Asked the clarifying questions you’d normally chase — who’s affected, what changed, how urgent, what access is needed.
• Set a category (type / subtype / item) and a priority from the impact and urgency signals in the conversation.
• Resolved the routine ones outright — password nudges, status checks, simple how-tos — and closed them in your PSA before they ever hit your queue.

What reaches you, then, isn’t raw intake. It’s a queue of already-scoped work that needs a human’s judgment: which tech, which tier, which order, and what’s about to breach. That’s the shift — from gathering to orchestrating.

​

The board is real-time, and so is the PSA

Everything you do on the board syncs to your PSA — ConnectWise, Autotask, or HaloPSA — in real time over webhooks. Assign a thread, change its status, drop it on a day in Planner, and it lands in the PSA automatically. You don’t dispatch in one system and reconcile in another; you dispatch in Inbox and the PSA stays in lockstep. That real-time board is what makes proactive dispatch possible. Because open threads, statuses, and XLA timers update live, you can see load building on one tech and a deadline tightening on another as it happens, and rebalance before either becomes a problem — instead of finding out at the standup.

​

Structure your desk so routing is obvious

Good dispatch starts with a board that mirrors how your desk is actually organized. Thread supports the common service models directly, and the routing decisions get easier once the board matches the org. Pick the model that fits your desk and build the Views around it — the service team structure guide walks through each one. The rest of this course assumes you’ve got a shape in mind, because “where does this go?” is a lot faster to answer when the board already tells you.

​

Next

You know what changed. Now learn the board you’ll orchestrate from all day.