Super Magic is the AI teammate inside Thread. It searches your knowledge base, pulls client and
device history, drafts notes and client updates, and takes action on tickets — from changing
priority to running a skill. The better your prompt, the better the output.
This page covers how to ask, then gives you a library of prompts grouped by what you’re trying to
get done. Everything in a code block is ready to copy.
If you’re ever unsure how Super Magic works, ask Super Magic. It will read the manual for you.
Where to use it
Almost every prompt below works in both places. The only difference is context.
How to talk to Super Magic
Start from where you are. Inside a ticket it already sees the thread, contact and client — point at “this ticket”. From the tab, name the client, ticket or technician.
Say exactly what you want. “Help me with this” is vague. “Summarize this thread and suggest a priority level” names the task and the output.
One job per prompt for bigger work. Break multi-step goals up: triage, then troubleshoot, then draft the note. Chain them as you go.
Name the format when it matters. Ask for “5 clarifying questions”, “a step-by-step plan”, “an internal note”, or “a client-facing update” and you’ll get output shaped for that purpose.
Use action verbs to make changes. Change, assign, move, close, escalate, schedule, log tell Super Magic to act on the ticket rather than talk about it.
Stay in the driver’s seat. Super Magic drafts and can act, but you decide what reaches the client or changes the ticket. Read drafts before sending; confirm before closing.
Iterate. If the first pass is off, say what to change: “make it more concise”, “less technical for the client”, “add the reboot step”.
Swap in the real details. Replace [client name], [technician] and [error message] with actual values.
Anatomy of a sharper prompt
Same intent, better result. The pattern never changes: name the task, point at the ticket, say what you want back.
The prompt library
Ticket triage and intake
Troubleshooting and resolution
Notes and documentation
Ticket management and updates
These change the ticket, so read what comes back before you confirm.
Scheduling and time
XLA and priority monitoring
Security incidents
One ticket, start to finish
The same ticket carried from intake to close in seven prompts. A good template for building your
own flow — and you can chain these rather than entering them one at a time.
Once these feel natural you’ll write your own. The pattern never changes: name the task, point at
the ticket, and say what you want back.
Next step
Browse the Magic Library for prebuilt jobs that go further than a
single prompt, and see Super Magic tools for everything
it can reach. 
Magic Library