Front desk

A complaint that arrives in a chat window is already a complaint

Practices design a complaints procedure and then receive complaints somewhere else. The message that begins "I waited forty minutes and nobody told me anything" is not a request for the procedure; it is the complaint, arriving where the patient happened to be. Treating it as a misdirected enquiry is how a solvable annoyance becomes a formal letter.

It does not become a complaint when it reaches a form

The clock starts when the patient writes, not when the right department receives it. An assistant that replies "please use our complaints form" has told someone already angry to do more work, and a proportion of them will do something else instead. Take it where it lands, in their words, and make the handover the assistant's problem rather than theirs.

Verbatim beats summary, and the timestamp matters

Whoever handles this next needs what was actually said, not a paraphrase of its sentiment. Keep the patient's own wording, the time it arrived, and any detail that fixes the event in the diary, because a complaint about a specific afternoon is answerable and a complaint about a general impression is not. This is also the difference between a record you can act on and one you can only apologise for.

Do not concede the facts, and do not deny them either

An apology that accepts a version of events the practice has not checked is a liability, and a defence of events nobody has checked is worse. The line that works in both directions is an apology for the experience and a commitment about the process: sorry that the visit went that way, here is who will look at it, here is when. Write that sentence once and let the assistant use it.

Route to a person, not to a queue

"The relevant team has been notified" is where complaints go to die, and patients can tell. Name the role that will respond and the day by which it will happen, then make sure that is true. A complaint handled by a named person on a stated day rarely escalates; the same complaint acknowledged by nobody in particular frequently does.

Frequently asked questions

Should an AI assistant handle complaints at all?
It should receive them and route them, and it should not attempt to resolve them. Receiving is genuinely useful: it captures the words and the time, it tells the patient what happens next, and it stops the complaint being lost between channels. Resolution needs someone who can read the file and make a decision.
Can it apologise on the practice's behalf?
For the experience, yes; for the facts, no. "I am sorry your visit went that way" is safe and human. "I am sorry we kept you waiting forty minutes" accepts a version of events nobody has checked yet, and that acceptance can follow the practice into a formal process.
What about a complaint that suggests a patient was harmed?
That stops being a complaints-process question immediately. Anything suggesting harm, a safeguarding concern or a clinical error needs a person and a phone number now, not an acknowledgement and a timescale. Decide which words trigger that before the assistant goes live.
Does logging complaints in one place help?
It is usually the first time a practice can see that eleven people complained about the same thing. Individually each was handled and closed; together they are a process defect, and the pattern is invisible while the complaints live in separate inboxes.
Which languages can a patient complain in?
English, Hebrew and Russian, detected from the message. A patient who has to complain in someone else's language usually does not complain, which looks like satisfaction and is not.

Get in touch

Leave your details and we will reply. You do not need a sales call to get an answer.