Requests everywhere, and nobody sure who is handling them
Most major manufacturers now offer remote care through their patient apps. A patient can send a message saying their aids sound tinny in restaurants, and the dispenser can respond with an adjustment or a remote session. It is a good service. It also creates a new stream of work.
Requests arrive in the manufacturer portals, one per brand. Others come by email to the clinic's general address, or as phone messages. Some are for dispensers who are on leave. Nobody has a single list of what has been asked and what has been answered.
Why remote requests get lost
- Each manufacturer's remote care portal is separate, so a clinic fitting several brands has several places to check.
- Patients also email or phone about the same problem, creating duplicates.
- Requests go to the fitting dispenser, and wait when that person is away.
- Some requests need a remote session, some a clinic visit, and some a call first. That sorting is done in someone's head.
- What was done remotely is not always noted in the patient record.
What an unmanaged queue costs
Patients who wait for a response and assume the clinic is not interested. Dispensers who come back from leave to a pile of old requests. Duplicate effort when the same issue is handled twice. And gaps in the patient record, which matter when the patient next comes in.
| Request arrives by | Today | With one queue |
|---|---|---|
| Manufacturer app | Checked when someone remembers | Pulled in or flagged daily |
| General inbox | Sorted into the queue, linked to the patient | |
| Phone message | Note on the desk | Logged by reception into the queue |
| Web form | Often not offered | Available and goes straight in |
How we build the request queue
- Every request route is brought into one queue. Email and web form requests go in directly. Phone requests are logged by reception in a few clicks. Where a manufacturer portal sends notifications, those are captured too, or a daily check prompt is set for each portal.
- Each request is matched to the patient and their devices, and duplicates from the same patient are grouped.
- Requests are sorted into types your team defines, such as sound quality, physical fit, connectivity or a fault, so the right person picks each one up.
- When the fitting dispenser is away, requests pass to a named colleague rather than waiting.
- The dispenser chooses the response: a remote session, a call, or a clinic appointment. Bookings are made from the queue and confirmed to the patient.
- What was done is recorded against the patient, so the next clinician can see the history.
- A simple view shows open requests and how long they have been waiting.
Adjustments themselves stay in the manufacturer's fitting software and in the dispenser's hands. We organise the requests and records around them.
Patterns become visible too. If several patients fitted with the same model ask about the same thing in the weeks after fitting, the queue shows it, and your team can decide whether to adjust the first-fit approach or add a note to the follow-up appointment.
What remote care feels like afterwards
Patients get a response, even when their dispenser is on holiday. Dispensers see one queue instead of several portals and an inbox. Requests are routed to remote sessions or visits sensibly. The record shows what was done. The clinic can offer remote care confidently, because it can see it is being handled.
Is remote care getting away from you?
- You fit several brands and check several remote care portals.
- Patients email and phone about the same adjustment request.
- Requests wait while a dispenser is on leave.
- What was done remotely is not always written up.
- You could not say how many remote requests are open right now.