When a computer will not log in during a medication pass, the temptation is to call the helpdesk and say it is not working. Unfortunately, those three words begin a round of questions that can take longer than the fix. A well-written support request gives a technician what they need to start solving the problem immediately.
This guide is for nurses, aides, administrators and office staff. None of it requires technical knowledge, only the habit of noticing and sharing a few details.
A helpdesk technician cannot see your screen, your hallway or your cart. They rely on your description to decide whether a problem is a single computer, a whole wing or the internet connection. A good ticket lets them skip the guessing and go straight to the likely cause.
Give your name, the best phone number to reach you and the location, such as the north hall nurses' station or the business office. If the equipment has an asset tag or a name label, include it.
Describe the task, not the diagnosis. Saying I was trying to open the medication record is more useful than saying the software is broken.
Write exactly what you saw. If there was an error message, copy the words or take a photo of the screen with your phone. Messages that seem meaningless often point straight to the cause.
Note whether it began this morning, after a power flicker, after an update or after a particular action. Also say whether it ever worked before.
Ask a coworker to try the same thing. If it fails for everyone, the cause is likely a system or network problem. If it only fails for you, it is likely your account or device.
Mention restarting, trying a different computer or signing out and in. This prevents repeating steps and helps rule out causes.
Every request feels urgent to the person making it, but helpdesks must prioritize. Help them by describing impact:
Critical: resident safety or care is affected, or many people cannot work. Call rather than email.
High: one department cannot do an important task, with no workaround.
Normal: one person is inconvenienced but can work another way.
Request: a new account, a new device or a change.
Say whether there is a workaround. Telling the helpdesk that you are using paper for now lets them focus on the worse problems first.
Avoid bundling several issues into one message. Separate tickets can be assigned to different technicians and tracked independently. Similarly, avoid replying to an old closed ticket with a new problem.
Do not share your password in a ticket or by phone. A legitimate technician will never need it and will use secure methods.
Do not include resident names or health details in a ticket unless your provider has approved a secure channel. Use initials or room numbers when needed.
Do not keep trying random fixes that change settings, because it can hide the original problem.
A support process works only if staff use it. Consider these steps:
Post one phone number and one email address at every station.
Offer a simple form or a shared mailbox with a short template.
Appoint a point person on each shift who gathers issues and avoids duplicate calls.
Share recurring problems with your IT provider so root causes are fixed instead of patched repeatedly.
Review ticket trends monthly. Many repeating issues point to training needs, aging equipment or network weaknesses.
You can keep this on a card by the phone:
Name, phone, location
What I was doing
What happened, including the exact message
When it began
Who else is affected
What I tried
How urgent: critical, high, normal
Good support is a partnership. The clearer your requests, the faster fixes arrive, and the more your provider learns about patterns in your facility. UnityCare IT provides helpdesk support for healthcare organizations and is glad to provide a printable quick-reference card and short training for your staff. Just ask.
Call or text: 405-285-3845
New customers: start@unitycareit.com
Existing customers: support@unitycareit.com
Address: UnityCare Technologies, 2524 N Broadway Ste 554, PMB 947974, Edmond, Oklahoma 73034-4172