The technician’s course for Thread: a six-lesson path to working tickets in Inbox with Super Magic, plus a starter kit, ritual, and 30-day ramp.
You work the queue. Thread’s job is to get you to resolution faster — less typing, less context-switching, more fixing. This is your course: six short lessons that take you from your first reply to chained AI workflows, plus the skills and rituals built for your day.
The Magic Library has hundreds of technician skills. Start with these — then press ⌘K and search for any task (“reset password”, “vpn”, “printer”) to find the rest.
Client Reply
Draft the client reply in your house voice.
Ticket Research Co-pilot
Cited, evidence-based research before you touch the ticket.
Start with Super Magic. On every ticket, ask it for the history and the likely fix and let it draft the reply — before you look anything up by hand. Log the time with TimePad so the work lands in your PSA.
Your first move on a ticket is asking Super Magic, not opening the PSA.
Week 2
Let the AI carry the context. Contact Intelligence before a first reply, Magic Recap on every handoff, sentiment to catch an account going sideways early.
You start a reply already knowing the history — you never re-read a thread from the top.
Week 3
Work the queue, not the ticket. The Views you live in, Beast Mode to move through the board, Planner for your day, XLA steppers so nothing ages out unseen.
You never wonder what to pick up next.
Week 4
Chain it. One Super Magic run across a whole set of tickets, approvals sent from the composer, and the knowledge articles you actually used refined so the next tech inherits them.
You close a ticket in a sentence, and you’re teaching someone else to.
Thread gets smarter the more your team uses it. Every ticket resolved in Inbox feeds Contact Intelligence, builds knowledge articles, and sharpens the Triage Agent. Your adoption compounds for the whole desk.
Turn on the Aa editor so Ctrl+Enter sends, then write multi-line replies fearlessly.
Recap before every handoff; check Recent Threads and Contact Intelligence before every first reply.
Dictate long Super Magic requests instead of typing them.
Use an internal note when you need a Flow to re-evaluate a thread — notes reliably trigger the PSA webhook update that Flows listen for.
I'm missing contacts, boards, or statuses from my PSA
Run the thread-level PSA Sync first. If it’s workspace-wide, an admin can run a manual sync from Admin → Integrations → PSA → PSA Sync. Syncs can take up to an hour.
I'm new and I can't see any Views
Newly synced members must be added to existing Views manually — ask your admin or team lead to add you.
I changed something but the Flow/automation didn't fire
Flows evaluate when a thread is updated (reply, note, status change, board change) after the flow exists. Add an internal note to nudge a thread through. Webhooks are near-real-time but not 100% guaranteed.
Who do I ask when I'm stuck?
Your team’s Thread admin first, then these docs. Your company’s Thread Customer Success Manager is also working with your admins throughout onboarding.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.