The email arrives on a Tuesday afternoon: "Your request has been closed." The printer in the nurses' station jammed again last week, someone from IT fixed it, and now the ticket is marked done. Whether the problem is actually gone is a different question, and the ticket system cannot answer it without you.
Most closed tickets get no response at all. That is understandable, since everyone is busy, but it means your IT provider mostly hears from you when something is on fire. Short, specific feedback after a ticket closes is one of the cheapest ways to get better service, and it takes about two minutes.
Feedback gets vague when everything is lumped into "it was fine" or "it was bad." Try to judge three different things on their own.
The fix. Did the problem actually stay solved? A password reset that works is a fix. A printer that jams again on Friday is not.
The manner. Were you kept informed? Did the technician explain what they did in words you could follow? Were your staff treated with respect, including the night aide who called in frustrated?
The pattern. Is this the second or third time you have reported something similar? A single ticket looks like bad luck. Three tickets about the same room or the same system is a signal that something underneath has not been found.
The pattern is the piece administrators most often miss, because each ticket is closed on its own and nobody is looking across them.
Useful feedback names a date, a place and an effect. Compare these two:
"IT was slow and the problem keeps happening."
"The Wi-Fi in the east hall dropped twice during the 2 a.m. med pass last week. The ticket was closed after a restart, but it happened again Thursday."
The second one tells your provider where to look, when it happens and why it matters to your staff. It also helps them decide whether this is a one-off or a design problem with coverage in that hall.
Include the impact on care or operations if there was one: a delayed med pass, a billing run that had to wait, a family member who waited at the front desk. That is how a provider learns what to prioritize.
When a closed-ticket survey or email lands, run through these questions before answering:
Is the original problem still gone, or has it come back?
Did the person who fixed it tell you what the cause was, even briefly?
Were you or your staff told what to do if it happens again?
Has this same kind of issue been reported before, in this room or on this system?
Was anything left half done, like a loaner device not returned or a setting someone said they would change later?
Is there one thing that would have made this go faster, such as a clearer way to report it or a name to ask for?
If the answer to the first or fourth question is troubling, say so plainly. If everything went well, say that too, and name the technician if you can. Specific praise tells a provider which habits to keep.
If the problem returns, ask to reopen the original ticket, or at least reference it by number. A new ticket with no history makes the next technician start from zero. A reopened one carries the notes, what was already tried and the dates, which is exactly what a root-cause search needs.
It also gives you a record. If you have to escalate, you can point to three tickets over six weeks rather than a feeling that "it's always broken."
Some feedback does not belong in a ticket survey. If you notice slow response during after-hours calls, repeated issues with one system, or confusion about who to call, bring it to a scheduled check-in with your provider. Many providers can pull a list of your tickets by category, location or system, and that list often shows what individual tickets hide.
A monthly or quarterly review works well for this. Ask for:
The most common ticket types over the period
Any location or device that appears more than once
Requests that stayed open longer than expected, and why
What the provider recommends changing to reduce repeat issues
You do not need to be technical to read that list. You only need to ask what stands out.
Feedback works best when it is a habit, not a verdict. Mention what improved, not only what failed. Tell department heads to give the same kind of detail so you are not the only voice. And if a technician was rude, dismissive or careless with resident information, say so directly and promptly, because that is something your provider will want to address rather than discover later.
UnityCare IT welcomes specific feedback on closed requests and uses repeat tickets to look for the underlying cause rather than treating each one in isolation. We can review your ticket history with you on a regular schedule and recommend changes that reduce repeat issues. Our help desk includes after-hours support, so feedback about night and weekend experiences is just as useful to us.
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
Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas
Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support