Every complaint becomes a numbered commitment

The first failure in most complaint handling is not slowness — it is that the complaint never became a record. Someone told a nurse, a branch officer, a warden. Grievance Redressal starts by making sure the thing was written down, with an identifier the person raising it can hold.

• One complaint register, whatever the door.

  A problem raised inside a voice conversation, typed on the same invitation link, walked in by a staff member, or filed by a member of the public on your own filing page — all four land as a numbered complaint in one register, on one clock. Split registers are how an organisation discovers, during an assessment, that it has two different answers to the same question.

• The number is spoken back while the person is still on the call.

  The voice agent registers the complaint mid-conversation, reads the reference number aloud and states the turnaround your organisation has committed to. The number is minted by the platform before it is spoken, so the complainant leaves the call holding something they can quote back to you.

• A public filing page, and a status lookup that gives nothing away.

  Anyone can file without an account and receives a reference code. The status page answers a wrong code, someone else’s code and a code that never existed in exactly the same way, so the lookup cannot be used to discover whether a particular complaint exists. Filer contact details are encrypted before they are stored.

Hospitals, banks and colleges are each held to a different set of hours by a different regulator, and every one of them treats a missed acknowledgment as a finding in its own right. The deadlines are configuration; what the platform contributes is that they are enforced without anyone having to remember them.

• Hospital, bank and college presets, as configuration.

  Categories, acknowledgment and resolution hours, the escalation ladder, the committee-pack label and the awareness poster arrive as a sector preset. They are settings, not a per-client build, so changing a deadline is an afternoon rather than a release.

• Acknowledged means acknowledged, with the number in it.

  The acknowledgment carries the reference number and the deadline the complainant should hold you to. The clock starts when the complaint is registered, not when somebody opens it, and an overdue case raises an alert rather than waiting for a person to notice a date.

• Escalation fires on its own, and refusal has a gate in front of it.

  The ladder is yours to define; the timer that walks it is ours. Where your sector requires a review step before a complaint may be rejected, the platform refuses to close it as rejected until that step is on the record — a rule in the database, not a reminder in a handbook.

A register that only records and closes is an expensive way to write things down. The part that changes an organisation is the loop after closure: what recurred, where, and what was changed because of it.

• A corrective action, attached to the complaint or to the trend.

  Closing a case answers what happened to one person. A corrective action answers what the organisation will change so it does not happen again — recorded against a single complaint, or against a pattern across many, with an owner and a due date.

• Repeat detection by category and by department.

  Twelve billing complaints is a number every large organisation always has. Twelve billing complaints in one ward, in one month, is a finding a committee acts on. The reports group both ways, because only the second one changes anything.

• The loop closes with the complainant, not with the file.

  A resolution note, the complainant told what was done, and a satisfaction check afterwards — the closure step ISO 10002 asks for and the one most registers quietly skip. The voice agent can book that closure call during the original conversation.

Every organisation running this loop is eventually asked to prove it ran. That request is rarely for a dashboard — it is for a register covering a period, and for one case followed end to end. Both come out of the record as it stands.

• Twelve months of complaint register, exportable.

  The register your assessor or your board committee reads, as a spreadsheet or as a document, for any twelve-month window — categories, dates, deadlines met and missed, and what was done. Produced from the record, not assembled the week before a visit.

• An evidence pack per case.

  One complaint, one document: when it arrived, when it was acknowledged, who it went to, every escalation, the resolution communicated, and the corrective action that followed. The trail is append-only, so nothing in it can be tidied up after the fact.

• Why append-only matters more than any badge.

  An assessor is not asking whether your software is good. They are asking whether the record can be trusted — whether a late acknowledgment could have been quietly made early. Events are written once and never edited, which is the property that makes the rest of this page worth reading.

There is no certificate, licence or approval a complaint platform can hold that makes your institution compliant with anything. The obligation is yours, the accreditation is yours, and the assessment is of you. What a vendor can honestly offer is that each fact you will be asked for exists, is dated, and cannot have been edited afterwards — a numbered complaint, an acknowledgment that went out on time, an escalation that fired, a resolution communicated, and a corrective action that followed.

A vendor whose pitch says their software holds your regulator’s approval, or makes you ready for an assessment on its own, is describing something that does not exist for software of this sort. Read it as a signal about the vendor.

The complaints that damage an organisation are the ones nobody writes down — the patient who tells a relative instead of the desk, the borrower who tells a call-centre agent with no way to log it. A short voice conversation in the person’s own language reaches those, and the ones that turn out to be real complaints become numbered commitments in the same register as everything else.