Skip to main content
You run the desk. Structure the team, keep XLAs and dispatch healthy, watch the numbers, and drive adoption — that’s the job, and Thread gives you the levers for every part of it. This is your course: four lessons that take you from setting up teams and pods to reading analytics, running QA, and rolling Thread out across the desk, plus the skills and ritual built for a service manager’s week.

The course

Work these in order — each ends with a link to the next. The first two are configuration you set once; the last two are habits you run every week.
1

Set up the desk

Service team structure, Inbox teams and pods, and the Views your team lives in. Read →
2

XLAs & dispatch

Response timers, auto-dispatch profiles, available-for-dispatch, and business hours. Read →
3

Analytics & QA

Magic Analytics, View insights, CSAT, and a repeatable QA loop. Read →
4

Roll out & drive adoption

Change management, enablement, and the rituals that make adoption stick. Read →

Your starter kit

The Skill Library has a deep bench of QA and analytics skills built for running a desk. Start with these — then press ⌘K and search for any management task (“staffing”, “sla breach”, “reopen”) to find the rest.

Weekly Ops Report

A desk-wide performance read, packaged for your weekly review.

SLA Analytics

Track XLA attainment and explain where time is going.

Tech Performance Review

A fair, data-backed read per technician before a one-on-one.

Ticket QA Review

Automate ticket QA against your own rubric.

Weekly QA Digest

The week’s QA misses, summarized and ready to coach on.

Queue Hygiene Score

Grade the board and see exactly what needs cleanup.

Your ritual

Lead daily ritual

A daily read on the desk — XLA risk, aging work, sentiment dips, and where to intervene before it becomes a fire.
Open Magic Analytics and your team Views first thing, run the lead daily ritual, and end the week with the Weekly Ops Report. The desk you can see is the desk you can run.

Your first 30 days: the adoption ramp

Thread gets sharper the more your desk uses it. Every resolved ticket feeds Contact and Client Intelligence, trains the Triage Agent, and improves the analytics you manage from. Your team’s adoption compounds into your visibility.

Pro tips & FAQ

Structure first: service team structure, then Inbox teams, then the Views each team works from. Route and measure only after the shape of the desk is set — everything downstream keys off it.
Newly synced members are added to existing Views manually. As the manager, add them from the View’s member settings, or have your admin do it — new hires won’t inherit Views automatically.
XLA clocks respect business hours and closures. If timers keep running when the desk is closed, your business hours or holiday calendar isn’t set — fix that before you trust any XLA number.
Run Ticket QA Review and Tech Performance Review so every conversation is grounded in the same rubric and the same data. Consistency is what makes coaching land.
Both. Your Thread Customer Success Manager brings the change-management playbook; you own the day-to-day habits on the desk. The rollout lesson covers how to split it.