Cluster 04
The most sensitive conversations on this site. Callers are often older, often unwell, often talking about money and mortality in the same breath. Everything in this cluster is built around two things: saying the required words, and being able to prove you said them.
Sectors
Four sectors sit in this cluster. They differ in product and share a single characteristic: the person on the other end deserves more care than a pace metric would give them.
On the floor — Seasonal enrolment pressure, heavy inbound from advertising, and a script with required language that has to survive contact with a busy floor.
What it uses — Two-way local numbers to take the response call, IVR and ring groups to route it, required-disclosure flagging on the rubric, and QA coverage tracking so you know what proportion has actually been reviewed.
On the floor — Older customers, longer calls, real emotional weight, and a follow-up rhythm that runs over weeks rather than a single session.
What it uses — Progressive dialling so no customer answers to silence, scheduled callbacks and tasks on the lead record, and full recordings for the file.
On the floor — Subscription acquisition, retention and cancellation handling, where the claims made on a call are the whole compliance exposure.
What it uses — Prohibited-phrase flagging against your approved script, transcripts searchable by spoken words, and campaign-level evidence tying a call to the list and offer it came from.
On the floor — Inbound from people in crisis and from their families, where routing speed and the conduct of the first ninety seconds matter more than any other metric on the floor.
What it uses — Inbound routing to the right team fast, Silent Listen for training without intruding, role isolation so recordings are reachable only by people who need them, and a coaching queue that treats conduct as the primary review criterion.
Handling
A recording of a health conversation is not a general company asset. The controls here are about narrowing who can reach what, and leaving a trail when they do.
Team leads see their own team. Organisation managers see their operation. Access to recordings and call records follows that scope rather than being granted to everyone with a login.
SIP credentials are revealed per device by the account owner and can be rotated when someone leaves, so an ex-agent does not keep a working line.
Recording retention is set per account. A floor with a long dispute window and a floor with a data-minimisation policy want different answers, and the default should not decide it for you.
Disclosures
Training says the disclosure is read. QA coverage tells you whether it is. The difference is the entire value of this cluster's compliance workflow.
Build the scorecard your sector needs, change it when the rules change, and score against the script you actually approved.
Automated review flags a missing disclosure or a banned phrase and drafts a score. An authorised manager confirms anything that lands on a record.
Track the proportion of calls, agents and campaigns reviewed. Coverage is what tells you whether your programme is real or decorative.
What we do not claim
We are a telecommunications and software operator. Nothing here represents anything about coverage, eligibility, treatment, clinical outcome or health result, and our platform is not qualified to.
If a script on your floor implies otherwise, prohibited-phrase flagging is the mechanism that finds it. That is the correct place for that problem to surface — internally, in a QA review, rather than externally, in a complaint.
Questions
Keep reading
Your floor
We will come back with the build: which numbers are immediate, which need documents, which destinations have rules you need to plan around, and what the whole thing costs to run.
