Turn a resolved ticket into a knowledge base article
Ticket closed: user couldn't print to the 2nd floor printer after the Windows update. Print spooler had stopped. Fix: restarted the spooler service, cleared the queue folder, removed the printer and re-added it by hostname instead of IP. 20 minutes. Same thing hit 3 others this week. Worked on Win 11 laptops, not tested on Macs.
I work in IT help desk support. Help me with the task below — I will review and edit what you give me before I use it. Relevant context: - Role: IT Help Desk and Support Technician - Work context: You work a ticket queue, explain technical problems to non-technical users, and write the knowledge base articles nobody else wants to write. Task: Turn a resolved ticket into a knowledge base article Source material: Ticket closed: user couldn't print to the 2nd floor printer after the Windows update. Print spooler had stopped. Fix: restarted the spooler service, cleared the queue folder, removed the printer and re-added it by hostname instead of IP. 20 minutes. Same thing hit 3 others this week. Worked on Win 11 laptops, not tested on Macs. What to give me: Give me a knowledge base article with symptom, cause, step-by-step fix, how to confirm it worked, and a does-not-apply note, so a user can try the first steps themselves. Boundaries: - Use only the facts in the source material. Do not invent names, dates, amounts, or promises. - If something needed is missing, list it as a question at the end instead of guessing. - If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.
Before you use it: Follow the steps yourself or against your notes before publishing, and make sure the AI didn't add commands or menu paths you never used.