Lesson 2 of 4 · about 6 min
Your first AI wins: 5 everyday tasks
When you finish, you can use AI for troubleshooting plans, error explanations, user replies, articles and script review.
Stuck? Ask the AI tutorWin one: a troubleshooting plan
Weak prompt: “Wi-Fi not working.” Strong prompt: “A user's Windows laptop connects to office Wi-Fi but has no internet. Other devices work. It began after a system update yesterday. List likely causes, ranked, with one safe check for each, and mark steps that could disrupt other users.” Context makes the list useful.
Check each suggestion against what you can observe. Run the least risky check first. If the assistant suggests resetting network settings, ask what that changes before you do it. You are the one touching the machine.
Win two: understand an error message
Weak: “What is this?” with a paste. Strong: “Explain this error for a new technician: what it usually means, three common causes, and what to check first. Do not give commands that change settings.” Remove usernames, machine names and internal addresses before pasting.
Cross-check with the product's own documentation. Error codes can change meaning between versions, and an assistant may mix them up. Use the explanation to know where to look, then confirm in a trusted source.
Win three: a calm reply to a frustrated user
Weak: “Write an email to an angry user.” Strong: “Write a short, calm reply to a user whose email sync has failed twice. Acknowledge the delay, say I will call them at three this afternoon, and avoid jargon.” You supply the real promise. Never let a draft promise something you cannot do.
Read it aloud. Does it sound like you? Cut anything that sounds like a script. People want to feel heard first and informed second. One warm sentence matters more than three technical ones.
Win four: a knowledge article from messy notes
After you solve a problem, notes are usually scattered. Weak: “Clean this up.” Strong: “Turn these notes into a knowledge article with symptom, cause, numbered fix steps, how to confirm it worked, and when to escalate. Write for someone in their first week.” Remove private details first.
Then follow the steps yourself, as if you were the reader. If a step is vague, fix it. Add the product version. A good article saves the next person from asking the same question, and that is how a help desk gets better.
Win five: review a script before you run it
Never run a script you do not understand, whether it came from a forum or an assistant. Ask: “Explain this script section by section. What does it change? What could go wrong on the wrong machine? How can I test it safely and undo it?”
Test in a lab or on one non-critical device first. Look for commands that delete, overwrite or change permissions. If the explanation includes words you do not know, look them up. Small, reversible steps are the habit of a careful administrator.
Practice now
- Write a strong troubleshooting prompt for a problem you saw last week, with device, symptom, timing and recent changes. Compare the AI's ranked causes with what you found.
- Turn the notes from one solved problem (no private details) into a knowledge article with an AI tool, then follow the steps as a beginner would and fix anything unclear.
Use any AI assistant you have. Do not paste private, client or patient information into it.
Check yourself
1. What should you remove before pasting an error message into an AI tool?
2. Before running a script an assistant wrote, what is best?
3. What goes into a reply to a frustrated user that only you can provide?
Ask the AI tutor
Ask anything about this lesson, in any language. The tutor is an AI: it can be wrong, and it never needs your personal details.
AI-drafted. Checked by an automated validator and a separate AI reviewer; a person has not read every lesson. Translations and tutor answers are AI-made. Found a mistake? Tell us. AI can be wrong. General information only, not professional advice. Not affiliated with any AI company named. Current University is not accredited.