Anyone who has opened a support case knows the frustration of a reply that asks for information you thought you already provided. "Please describe the issue." "Which user is affected?" "Can you send a screenshot?" Each exchange adds hours or days. When the system in question is your electronic health record, those delays affect care and staff time.
A well-written case does not guarantee a fast fix, but it removes the most common source of delay: missing information. Here is a practical approach to writing vendor support cases that get answers, using general principles that apply to PointClickCare and any other clinical software vendor.
Spend a few minutes on groundwork:
Reproduce the problem if you can, and note the exact steps.
Check for a known issue. Look at your vendor's status page or notices.
Rule out local causes. Try another browser, another computer or another user. This tells support whether the problem follows the person, the device or the system.
Gather evidence such as screenshots and error text.
Never include more protected health information than necessary. Use resident initials or an internal identifier if the vendor's process allows it, and follow your policies about sharing PHI in tickets.
Compare "EHR not working" with "Unable to save progress note for one user, error message on submit." A specific title helps routing and lets you find the case later.
State plainly who and what is affected:
How many users or residents
Whether care is impacted, such as medication documentation blocked
Whether a workaround exists
When it began
This helps the vendor prioritize. Be honest. If everything is marked urgent, the label loses meaning.
Describe both. "I expected the note to save and appear in the chart. Instead, the page showed an error and the note was missing." The contrast clarifies the problem.
Write numbered steps that someone unfamiliar with your workflow could follow. Include the location in the software, the type of record and any particular inputs that seem relevant.
Include:
User name or ID of an affected account, according to your vendor's guidelines
Role of the user
Device type and operating system
Browser name and version
Location or facility
Network context, such as on-site Wi-Fi, wired or remote
Give exact dates and times, including time zone. These allow the vendor to find logs for the event. If it is intermittent, note when it happened and when it did not.
Attach screenshots with the full browser window visible, including the address bar and any error text. Copy error messages in full. A short screen recording can help for visual issues.
List troubleshooting steps and their results so support does not repeat them.
Impact: who, how many, care affected, workaround
Started: date and time
Keep a copy in your helpdesk so anyone on staff can use it.
Respond quickly when the vendor asks questions. Cases often stall waiting on the customer.
Keep one case per issue and reply within the same case to preserve history.
Escalate through your account representative when impact is high and progress is slow, referencing the case number and the business effect.
Record the resolution, and note any permanent fix, so the next occurrence is faster.
Track cases by date, subject, time to resolution and root cause. Patterns, such as repeated issues after updates, give you leverage in vendor discussions and help you plan.
Be courteous and factual. Support engineers are people working through a queue, and a clear, respectful case tends to get more attention than an angry one.
UnityCare IT's helpdesk often acts as the go-between with EHR and software vendors for clients, collecting the details, opening the case and following up until it is resolved, so your clinical staff can return to residents.
A helpdesk your staff can call or text when something stops working.
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