The death of the “have you tried turning it off and on again?” email thread
Most IT tickets spend their first hour collecting facts IT already has. Context-aware support starts from those facts instead.
· 3 min read · The TodaysBru teamYou know how this email thread goes.
“I can’t change my laptop password.” Twenty minutes later: “Have you tried restarting? Are you on a Mac or Windows?” An hour later: “Restarted. Mac.” Then: “Which version?”
By the time anyone starts troubleshooting, half the morning is gone. Almost none of that time went into fixing the problem. It went into collecting facts IT already had, in an asset spreadsheet or a device record that the ticketing system never looked at.
Generic advice for a specific problem
A traditional ticket arrives with an email address and a subject line, and nothing else. So the help desk falls back on generic advice: Windows steps for a Mac user, a browser fix for a browser the company doesn’t use, a request for log files the employee has no idea how to export. Every wrong guess adds another round of email, and employees learn to dread contacting IT.
Start from what IT already knows
When an employee asks TodaysBru for help, it checks IT’s own records before it answers:
- Their devices and operating system. The laptops and phones assigned to them in IT’s asset records, so it already knows whether they’re on macOS, Windows, ChromeOS, iOS, or Android.
- Your standard software. The browser, VPN, and other tools the company has standardized on, including the version when IT has recorded one.
- Your knowledge base. The articles that apply to that setup, cited under the answer.
Ask “I need to reset my laptop password” as a MacBook user and you get the Mac steps (System Settings > Touch ID & Password), taken from your Mac article. The Windows steps don’t appear, and nobody asks which laptop you have. If the records are wrong and the employee says they’re on something else, TodaysBru goes with what they say. If it can’t tell and the steps differ by system, it asks once.
Why it matters
- No diagnostic back-and-forth: the first reply is an answer, not a questionnaire.
- Answers that fit: the steps match the employee’s device and your company’s tools, so they work the first time.
- Better handoffs: when a person does need to step in, the whole conversation is already attached to the ticket, so nobody re-explains anything.
Stop asking, start resolving
“Turn it off and on again” will always be a good IT joke. Spending an hour on email to learn which laptop someone uses is the expensive part. Keep your asset records current, and let the help desk use them from the first message.
See how the rest of a request is handled in AI chat that answers first, or read the Help guide to set up your assets and knowledge base.