Introduction
A complaint is the cheapest market research a chamber site will ever receive. It arrives already paid for, already specific, and already pointed at the exact place where the service failed. Most clinics, wellness centres and distributors still treat complaints as an interruption to be closed rather than a signal to be mined, so the same three or four failures generate the same three or four conversations month after month.
This guide treats complaint handling as an operating system rather than a personality trait. It covers what enters the register, how intake is captured, how severity is triaged, when a complaint becomes a clinical or device event, what evidence to collect, how to word the response, what remedies to authorise, and how to turn the record into process change. The audience is operations owners and distributor service managers running chambers in clinics, wellness centres and spa settings.
The commercial case is simple. Acquisition is expensive, and a client who still cares enough to complain is far closer to staying than one who leaves quietly. A defensible recovery process protects retention, stops staff from improvising promises under pressure, and creates the contemporaneous record you would want to already have if a complaint ever leaves the front desk.
There is also a pattern-recognition benefit that only appears once the record exists. Individual complaints look like individual bad days; twenty of them plotted by chamber, shift and week reveal a training gap, a failing component or a poorly written induction that no amount of goodwill at the desk will fix. Volume alone is a poor diagnostic, which is why this guide keeps returning to classification rather than counting.
| Why complaints matter | Cost when handled badly | Gain when handled well |
|---|---|---|
| Retention | Silent churn, no second chance | Recovered clients, referrals |
| Staff confidence | Improvised promises, uneven answers | Scripted replies, calmer team |
| Clinical safety | Warning signs buried in booking notes | Early detection of patterns |
| Legal position | No record of what was said | Dated, contemporaneous evidence |
| Supplier claims | Vague fault reports, slow fixes | Precise data, faster remedy |
| Reputation | Public reviews written in anger | Private resolution first |
Two boundaries run through the whole guide. Nothing here is medical advice: anything with a clinical component is routed to the responsible clinician, not settled at reception. And recovery language must not become marketing language — what you may say about outcomes is governed by the same evidence rules as your advertising, set out in Compliant HBOT Marketing Claims.
| Reader | Primary interest | Sections to read first |
|---|---|---|
| Clinic owner | Retention and liability | Intake, remedies, register |
| Wellness centre manager | Comfort and scheduling complaints | Taxonomy, response conversation |
| Distributor service lead | Device complaints and supplier claims | Triage, investigation, reporting |
| Clinical lead | Clinical routing and red flags | Clinical versus non-clinical paths |
What Counts as a Complaint in an HBOT Service
Sites lose control of complaints because nobody defines what enters the register. Count everything and the register is noise; count only written letters and it is blind. The workable rule is broad at intake and narrow at classification: anything a client, family member, referrer or staff member raises as dissatisfaction, concern or alleged harm is logged, then classified.
Classification drives everything downstream — who answers, how fast, and which remedies are available. A complaint about cabin temperature and an allegation of injury during pressurisation share an intake form and nothing after that.
Sites often resist classifying at intake because it feels bureaucratic while a client is standing at the desk. In practice one dropdown and one owner field at the moment of receipt removes most of the rework later. What slows teams down is not classification; it is re-reading a vague note three weeks afterwards and trying to reconstruct what the client actually meant.
| Category | Typical trigger | Owner | Usual clock |
|---|---|---|---|
| Clinical | Symptoms during or after a session | Responsible clinician | Same day |
| Safety | Alleged equipment or procedural hazard | Safety lead | Immediate |
| Comfort | Noise, temperature, space, hygiene | Operations manager | 48 hours |
| Scheduling | Late start, cancelled slot, waiting | Front desk | 24 hours |
| Communication | Conflicting instructions, no callback | Operations manager | 24 hours |
| Commercial | Refund, package, pricing dispute | Site owner | 72 hours |
| Privacy | Records, photographs, confidentiality | Data lead | 24 hours |
| Device | Chamber fault, downtime, alarm | Service lead plus supplier | By severity |
Comfort complaints deserve more attention than they usually get. Mild chambers pressurise with air and deliver oxygen by mask or hood, so clients sit in an enclosed steel shell for a full session. Perceived noise, temperature drift and the feeling of enclosure are predictable friction points, not personality problems.
| Comfort trigger | Likely root cause | Fix that usually works |
|---|---|---|
| “It was too loud” | Compressor, ventilation, hard surfaces | Expectation setting, acoustic treatment |
| “I felt closed in” | No preview, no visible exit | Pre-session walkthrough, clear sightlines |
| “It got stuffy” | Ventilation rate, occupancy, textiles | Airflow check, turnover routine |
| “The mask hurt” | Fit, strap tension, hood size | Fit check, alternate interface |
| “Nobody explained” | Rushed induction | Written induction plus teach-back |
| “I was left waiting” | Slot overrun, late previous client | Buffer time, honest update |
Not every negative event is a complaint, and mixing the two corrupts both records. An internal defect found by staff is a quality issue; the same defect reported by a client is a complaint that also generates a quality issue. A clinical incident is assessed on clinical grounds regardless of whether anyone complains.
| Event | Enters complaint register | Enters incident register | Enters quality log |
|---|---|---|---|
| Client reports ear pain after a session | Yes | Yes | Yes |
| Staff notice slow pressurisation | No | No | Yes |
| Client unhappy about parking | Yes | No | No |
| Alarm sounds, session aborted, client fine | Only if raised | Yes | Yes |
| Anonymous online review about staff tone | Yes, if identifiable | No | No |
Complaint Intake Channels and the First Response
Complaints arrive through whichever door is easiest, and the easiest door is rarely the one you monitor. Front desk conversations, phone calls, messaging apps, booking-platform messages, email, review sites and referrer phone calls all carry them. If only one channel is logged, your data describes your monitoring rather than your service.
The first response has one job: establish that the message landed and that a named person owns it. It does not investigate, does not admit fault, and does not promise an outcome. Speed here is cheap and buys disproportionate goodwill.
| Channel | Visibility to the business | Capture risk | Minimum control |
|---|---|---|---|
| Front desk conversation | Low unless logged | Highest | Mandatory same-shift log entry |
| Phone call | Low unless logged | High | Written note with time and caller |
| Website form or email | High | Low | Auto-acknowledgement |
| Messaging app | Medium | Medium | Business account only, exported daily |
| Booking platform message | Medium | Medium | Daily sweep by duty manager |
| Public review | Very high | Low | Response within published window |
| Referrer or clinician | High | Low | Direct line to clinical lead |
| First-response element | Why it matters | Wording principle |
|---|---|---|
| Acknowledgement | Ends the silence that escalates anger | Name the receipt, not the fault |
| Ownership | One person, one file | “I am handling this personally” |
| Timeline | Sets expectation you can beat | Under-promise the first date |
| Next step | Shows movement | State the single next action |
| Channel | Matches how they wrote | Reply where they wrote |
| Record | Feeds the register | Log before, not after, the reply |
A short acknowledgement template prevents most escalation. It confirms receipt, names the owner, states when the client will next hear, and thanks them for raising it. It avoids three things: an apology that concedes legal fault, an explanation the investigator has not yet verified, and any statement about clinical causation.
Templates work best when they are short enough to be used verbatim at a busy desk and rigid enough that nobody improvises the risky parts. Give staff a fill-in skeleton with three blanks — reference number, owner name and next contact time — rather than a paragraph they are expected to paraphrase. Paraphrasing under pressure is where unintended admissions appear.
| Say | Avoid |
|---|---|
| “Thank you for telling us.” | “These things never happen.” |
| “I am looking into this today.” | “It is not our policy to comment.” |
| “You will hear from me by [time].” | “That is impossible with our equipment.” |
| “I have logged this under reference [id].” | “You signed a waiver, so…” |
| “I will call you, not message.” | “It was probably your sinuses.” |
Severity Triage for HBOT Complaints
Triage decides who is woken up and who waits until Monday. Severity should be assigned on facts available at intake, then revised as evidence arrives. The mistake to avoid is letting the loudest voice set the severity — volume and severity correlate weakly, and quiet clinical complaints are the ones that later look worst on the record.
Four levels are enough. Each level fixes a response clock, a decision owner and a documentation depth, so nobody has to argue about process while a client is waiting.
Severity is also allowed to move. Many complaints arrive at L1 and are reclassified upward once the clinical content becomes clear, and a few arrive at L3 and settle to L2 once the session log shows nothing unusual. Record the initial level, the revised level, and the reason for the change; an unexplained reclassification looks like downgrading even when it is correct.
| Level | Definition | Response clock | Owner |
|---|---|---|---|
| L1 Low | Service friction, no harm alleged | [TO CONFIRM] business days | Duty manager |
| L2 Medium | Repeat failure, refund in scope | [TO CONFIRM] business days | Operations manager |
| L3 High | Alleged harm, safety or device | Same day, clinical review | Clinical or safety lead |
| L4 Critical | Serious harm, media or regulator | Immediate, owner notified | Site owner, legal counsel |
Decision rights must be written down before the first serious complaint, not during it. Staff who cannot name their authority either freeze or over-commit, and both outcomes cost more than the complaint.
| Decision | Who decides | Who must be told | Escalates to |
|---|---|---|---|
| Acknowledgement wording | Duty manager | — | Operations manager |
| Refund or credit up to limit | Operations manager | Owner | Owner |
| Refund above limit | Site owner | Finance | — |
| Clinical statement | Responsible clinician | Owner | External counsel |
| Public review reply | Operations manager | Owner | Marketing lead |
| Regulator or insurer notice | Site owner | Legal | — |
Escalation paths for device complaints differ from service complaints, because the remedy may sit with the manufacturer. Capture the data the supplier will ask for at the first pass rather than after three emails.
| Escalation trigger | First action | Information to attach |
|---|---|---|
| Chamber will not pressurise | Remove from service | Session log, alarm text, photos |
| Alarm during session | Follow emergency routine | Time, pressure, operator, client state |
| Repeated fault on one unit | Open service ticket | Fault history, maintenance records |
| Suspected component failure | Quarantine part if safe | Part reference, serial number, install date |
| Injury alleged | Clinical assessment plus incident report | Full session record, witness notes |
Untreated pneumothorax is an absolute contraindication to hyperbaric exposure, and any complaint describing chest symptoms around a session is treated as clinical first and commercial second. Sites should already run a documented screening and contraindication process; where that process is thin, the HBOT Client Screening and Contraindications guide sets out the intake and decision-rights structure this guide assumes.
Clinical Versus Non-Clinical Complaint Paths
The fastest way to turn a manageable complaint into a serious one is to answer a clinical question with a service answer. Reception staff are trained to be helpful, and helpfulness pushes them into explaining symptoms, which is exactly where they should stop. The routing rule is simple: if the complaint contains a symptom, body system or treatment-outcome claim, a clinician owns the response.
Non-clinical complaints are resolved by operations using the remedy ladder. Clinical complaints are assessed by the responsible clinician, who may conclude that no clinical issue exists and hand the service elements back — but the hand-back is a clinical decision, not an operational one.
The two paths still share one file. Splitting clinical and service elements into separate records is a common mistake, because the client experiences one event and will describe it that way. Keep a single reference number with one owner, and let the clinical findings sit inside it as a dated entry, so that anyone reading the file later sees the whole picture rather than half of it.
| Signal in the complaint | Path | Who replies |
|---|---|---|
| Ear or sinus discomfort | Clinical | Responsible clinician |
| Chest symptoms, breathlessness | Clinical, urgent | Responsible clinician |
| Dizziness or nausea after session | Clinical | Responsible clinician |
| “It did not work for me” | Clinical plus expectation review | Clinician then manager |
| Rude staff, late start | Non-clinical | Operations manager |
| Billing or package dispute | Non-clinical | Site owner |
| Red-flag wording | Immediate action | Do not |
|---|---|---|
| Chest pain, breathlessness | Clinical assessment now | Reassure at reception |
| Fainting, collapse | Emergency pathway | Delay for paperwork |
| Vision or hearing change | Clinical review same day | Schedule next week |
| Symptoms worsening after leaving | Call client, clinician to speak | Send a generic email |
| Legal or regulator mentioned | Notify owner and legal | Reply without advice |
Safety complaints belong to the emergency and risk-control system rather than the service-recovery system. Where a complaint describes a hazard — an alarm, a door behaviour, an oxygen-interface problem — the site’s Chamber Safety and Emergency Plan takes precedence, and the complaint record is opened in parallel, not instead.
Investigating an HBOT Complaint Without Guessing
Most bad investigations start with a theory. Someone recognises the client or the symptom, forms a view, and then gathers evidence that fits. The alternative is duller and more defensible: define the question, list the evidence that would answer it, collect it before forming a view, and write the conclusion so a stranger could follow it.
The evidence pack should be assembled within hours, while memories and logs are fresh. Session records, device logs, staff statements and the cleaning record are the four sources that usually decide the outcome.
Write the conclusion so that it names the evidence it rests on. “The complaint is upheld because the session log shows the session started [time] late and the client was not told” is defensible; “the complaint is upheld” is not. Where evidence is missing, say so explicitly rather than filling the gap with an assumption, because a later reviewer will treat the assumption as a finding.
| Evidence source | What it can prove | Capture window |
|---|---|---|
| Session record | Time, pressure profile, duration | Immediately |
| Operator statement | What was said and observed | Same shift |
| Client statement | Their account in their words | First contact |
| Device log or alarm history | Machine behaviour over time | Before next service |
| Cleaning and turnover log | Hygiene process followed that day | Same day |
| Booking and check-in notes | Timings, who was present | Immediately |
| CCTV where lawful | Sequence of events | Before overwrite |
| Maintenance history | Prior faults on that unit | Same day |
Device complaints need the specific data the manufacturer will request. HyperbaricO2Care chambers operate at 1.1–1.7 atm across the range, with the POLARIS Duo rated to 1.75 atm, and pressurisation to treatment pressure takes roughly 5–25 minutes depending on model and protocol, so “it was slow” is only meaningful against the model’s expected profile.
| Data point | Why the supplier needs it | Where it comes from |
|---|---|---|
| Model and serial number | Identifies configuration | Chamber plate |
| Date, time, session number | Locates the event | Booking system |
| Pressure profile observed | Distinguishes fault from protocol | Operator log |
| Alarm text or code | Points to subsystem | Control panel |
| Oxygen interface used | Mask versus hood behaviour | Session record |
| Ambient conditions | Rules out environment | Room log |
| Fault frequency | Recurrence versus one-off | Maintenance file |
Service teams also need to know which statements are safe to make to a client during an open investigation. The boundary that protects the site is the same one that protects the manufacturer: describe what was observed and what is being done, and leave causation to the clinician.
| Safe to say | Not safe to say |
|---|---|
| “We have taken the chamber out of service.” | “The chamber caused your injury.” |
| “Our engineer is reviewing the log.” | “This has never happened before.” |
| “A clinician will call you today.” | “It is definitely not serious.” |
| “Here is your reference number.” | “You will be compensated.” |
Where a device fault is confirmed, the complaint file becomes the evidence pack for a warranty or service claim, and the response times, coverage boundaries and spare-part route in Chamber Warranty and After-Sales determine what the client can be told and when.
The Response Conversation and Complaint Scripts
Most escalations are caused by tone, not by the underlying failure. Clients report being argued with, being told their experience did not happen, or being handed a policy instead of an answer. A short structure keeps staff inside the boundaries while still sounding human: acknowledge, state facts verified so far, state the next step, then stop.
Written responses should be reviewed by a second person for anything at L3 or above. That review is not bureaucracy; it is the cheapest possible check against a sentence being read aloud later in a setting you do not control.
Match the medium to the severity. Low-severity service friction can be closed in writing, but anything involving an alleged symptom, a refund above the authorised band or a safety question deserves a voice call, followed by a written summary of what was said. Voice first, writing second, keeps the tone human and leaves the record intact.
| Response stage | Objective | Typical length |
|---|---|---|
| Acknowledgement | Confirm receipt and ownership | [TO CONFIRM] hours |
| Interim update | Show progress before the answer is ready | [TO CONFIRM] hours |
| Substantive reply | State findings and remedy | [TO CONFIRM] days |
| Closure | Confirm actions completed and invite return | [TO CONFIRM] days |
| Follow-up | Check the fix held | [TO CONFIRM] weeks |
| Conversation move | Example intent | Risk if skipped |
|---|---|---|
| Reflect before explaining | Show you understood | Client repeats the story |
| Separate facts from feelings | Avoid arguing about perception | Escalation |
| Give one next step | Create movement | Client chases |
| Confirm in writing | Create a record | “Nobody told me” |
| Close the loop | Prove the fix | Silent churn |
Recovery language must stay inside evidence rules even under pressure. The temptation in a recovery conversation is to over-promise an outcome to end the discomfort. That converts a service complaint into a claims problem, and it is precisely the behaviour the marketing-compliance discipline exists to prevent.
| Recovery statement | Compliance-safe alternative |
|---|---|
| “You will feel much better next time.” | “Let us review your response with the clinician.” |
| “The chamber treats inflammation.” | “Your clinician can discuss indications with you.” |
| “This never happens with our equipment.” | “We will verify what occurred and tell you.” |
| “It is clinically impossible.” | “Here is what our records show.” |
Service Recovery and Remedies for HBOT Clients
Remedies should be pre-authorised by level so that front-line staff can act within a defined band and escalate beyond it. A remedy given quickly at the point of failure costs far less than the same remedy granted three weeks later after a review was posted.
The ladder runs from explanation to corrective action to commercial gesture. Commercial gestures are last, not first: money without a fix reads as a settlement and leaves the underlying failure in place.
Explain the remedy as clearly as the remedy itself. Clients rarely remember the value of a credit; they remember whether someone told them plainly why it was being offered and what had changed as a result. A remedy delivered with a short explanation of the corrective action converts a refund into evidence that the site takes its own standards seriously.
| Ladder rung | When to use | Authorised by |
|---|---|---|
| Explanation | Misunderstanding, no failure | Any staff member |
| Immediate fix | Failure still ongoing | Duty manager |
| Corrective action | Process gap identified | Operations manager |
| Session or package credit | Service failure confirmed | Operations manager |
| Refund within limit | Client declines return | Operations manager |
| Refund above limit | Serious failure, legal exposure | Site owner |
| Remedy | Typical trigger | Watch-out |
|---|---|---|
| Apology plus explanation | Expectation mismatch | Must not admit legal fault |
| Priority rebooking | Cancelled or delayed session | Only if capacity exists |
| Complimentary add-on | Minor comfort failure | Avoid implying clinical benefit |
| Session credit | Repeat service failure | Log against the package |
| Partial refund | Material failure, client leaving | Written terms required |
| Full refund | Serious failure or clinical advice | Owner plus clinical sign-off |
Some remedies should never be offered, however tempting. Free clinical advice, guarantees of outcome, and any statement that the chamber is approved to treat a named condition create exposure far beyond the value of the complaint. HyperbaricO2Care chambers carry CE marking and are manufactured under an ISO 13485 quality management system; they are not FDA-cleared devices, and no recovery conversation should imply otherwise.
| Never offer | Reason |
|---|---|
| Guaranteed clinical outcome | Unsupportable claim |
| Diagnosis at the front desk | Outside scope and role |
| Confidentiality about a safety defect | Overrides safety duty |
| Cash without a record | No audit trail |
| Silence in exchange for money | Suppresses reportable events |
Complaint Registers, Reporting and the Learning Loop
A complaint handled and not recorded is a complaint that will happen again. The register is the smallest dataset that lets a site see patterns: by category, by staff member on shift, by chamber, by day of week, and by stage of the client journey. Patterns at that resolution are rarely visible from memory.
The register must be a single system, not a folder of emails. Each entry carries an identifier, timestamps, classification, actions, remedy, and closure reason, and it is closed only by the person who owns the outcome.
| Register field | Purpose | Required at |
|---|---|---|
| Reference number | Unique traceability | Intake |
| Date and time received | Clock measurement | Intake |
| Channel | Coverage analysis | Intake |
| Client identifier | Link to session history | Intake |
| Category and severity | Routing | Triage |
| Owner | Accountability | Triage |
| Actions taken with dates | Proof of handling | During |
| Remedy granted | Financial control | Closure |
| Root cause | Learning | Closure |
| Closure date and by whom | Audit | Closure |
| Monthly review question | What it surfaces |
|---|---|
| Which categories grew? | Emerging failure |
| Which chamber appears most? | Unit-specific fault |
| Which shift appears most? | Training or handover gap |
| Which stage of journey? | Induction or aftercare weakness |
| How many missed their clock? | Capacity or process issue |
| How many reopened? | Fix did not hold |
Metrics should be few and stable. Volume per hundred sessions, acknowledgements inside the clock, closures inside the clock, reopened complaints, and repeat-category rate tell an owner almost everything; a dashboard of thirty numbers tells them nothing.
| Metric | Definition | Target |
|---|---|---|
| Complaints per [TO CONFIRM] sessions | Volume normalised | [TO CONFIRM] |
| Acknowledged inside clock | Percentage | [TO CONFIRM] |
| Closed inside clock | Percentage | [TO CONFIRM] |
| Reopened | Percentage of closures | [TO CONFIRM] |
| Repeat category | Same cause within [TO CONFIRM] | [TO CONFIRM] |
| Recovered clients returning | Percentage | [TO CONFIRM] |
Feedback has to reach the people who can change the process. Complaint themes belong in the same review cycle as staffing, training and runbook updates; the operator training and daily routine structure in Chamber Staff Training and SOP is where corrective actions usually land.
Conclusion
Handled well, complaint handling is a retention programme that also happens to be a safety sensor. The sequence matters: define what enters the register, capture it at every door, triage on facts, route anything clinical to a clinician, investigate before concluding, respond within pre-authorised language, remedy at the lowest effective rung, and record everything so the pattern can be seen.
Sites that do this report a second benefit nobody plans for. Staff stop dreading complaints, because the process tells them exactly what to say and when to hand over. Most of the stress in complaint handling comes from uncertainty, and uncertainty is what a written process removes.
| First 30 days | Next 30 days | Ongoing |
|---|---|---|
| Publish the intake definition | Train the triage levels | Monthly pattern review |
| Assign decision rights in writing | Pre-authorise remedy bands | Quarterly script refresh |
| Build the register fields | Add complaint themes to training | Annual legal review of templates |
| Set acknowledgement clocks | Review first ten closed files | Track recovered-client return rate |
If you are specifying or re-organising a chamber room and want the service-recovery perspective on layout, acoustics, sightlines and induction flow, our team reviews plans with operators regularly. Commercial terms, shipping and after-sales structure are covered on the HyperbaricO2Care contact page, including FOB, CIF and DDP options and T/T or LC payment.
Medical disclaimer: This article is general operational guidance for businesses, not medical advice. Hyperbaric oxygen therapy should be undertaken under the supervision of qualified clinicians, and untreated pneumothorax is an absolute contraindication. HyperbaricO2Care chambers are CE-marked and manufactured under an ISO 13485 quality management system; they are not FDA-cleared devices, and no claim of FDA clearance is made. Always follow your local regulations and your responsible clinician’s judgement.