Compliance Resource
Handling Sensitive Enquiries on Automated Calls
Some calls should never be resolved by automation, and some details should never be collected on one. This guide sets out the categories, the boundaries we hold in every deployment, and how to design a graceful exit.
Two separate questions
The first question is whether automation should handle the call at all. The second is what should be captured about it. They are related but distinct, and both need an answer before go-live.
Some enquiries must reach a person immediately because the consequences of getting them wrong fall on the caller. Others can be handled, but should be recorded sparingly, because the detail creates risk without improving the outcome.
Sector rules may apply on top of the Personal Data Protection Act, particularly in healthcare, legal, financial and education settings. Confirm those with the relevant professional body or your own advisers; this page describes the general design position only.
What always reaches a person
These categories escalate immediately in every deployment we build, regardless of industry, call volume or client preference. They are not settings, and we will not remove them on request.
- Any matter concerning an individual child, including safeguarding concerns
- Clinical triage, symptoms, and whether a caller should seek treatment
- Security incidents, threats and reports of harm
- Allergen confirmation and food safety assurances
- Callers in distress or crisis
- Grievances, disciplinary matters and personal HR issues
- Regulated legal, medical, financial and immigration advice
The reason is the consequence, not the difficulty. A confident wrong answer about a symptom, an allergen or a child’s safety can cause real harm, and a caller in distress needs a person rather than a well-designed flow. Automation should route these calls quickly and quietly, without attempting reassurance, assessment or advice.
Add your own categories. Complaints, media enquiries, legal correspondence, bereavement, financial hardship and calls from named accounts are common additions, and they should be written into the flow rather than left to judgement.
Collect less, not more
Where a call can be handled, the design question becomes what to capture. The default should be the minimum that lets the right person act, with sensitive detail left to the conversation that follows.
| Caller mentions | Avoid capturing | Capture instead |
|---|---|---|
| A medical matter | Symptoms, diagnoses or treatment details | That an appointment is requested, and the service area |
| A legal problem | Case facts and admissions | Contact details and the practice area, for a solicitor to call back |
| Financial difficulty | Debt figures and personal circumstances | A request to speak with the accounts team, routed promptly |
| Identification numbers | NRIC, FIN or passport numbers, unless genuinely required | Name and mobile number for matching |
| Payment details | Card numbers spoken on the call | A route to your normal secure payment process |
| Another person’s details | Third-party information volunteered by the caller | Only what is needed to act on the caller’s own request |
Callers will sometimes volunteer sensitive detail regardless. The flow should not prompt for it, should not repeat it back unnecessarily, and the record should carry only what the receiving colleague actually needs.
Designing the exit
How the handover feels matters as much as the fact of it, particularly when the caller is worried.
Recognise early
Trigger on the first indication rather than after several questions. A caller who has already explained a distressing situation twice has been failed by the design.
Acknowledge briefly
One short, plain sentence. No reassurance about outcomes, no assessment, no suggestion that the matter has been dealt with.
Route immediately
Transfer to the named person for that category, or take a callback if nobody is available, and say clearly which is happening.
Pass minimal context
The colleague needs to know the category and the caller’s contact details, not a transcript of everything that was said.
Out of hours, an honest statement of when a person will make contact is better than a route that implies immediate help. Where a matter is genuinely urgent and your business cannot respond, the caller should be told plainly so they can seek help elsewhere.
Design checklist
- Every fixed exclusion has a trigger, a route and a named recipient
- Your own sensitive categories have been added and documented
- No prompt asks for clinical, legal, financial or identification detail unnecessarily
- Payment details are never taken within the automated flow
- Sensitive detail volunteered by a caller is not repeated back or over-recorded
- Handover wording has been read aloud and sounds calm rather than abrupt
- Out-of-hours routes state honestly when a person will make contact
- Every exclusion has been tested with indirect and emotional phrasing
- Staff receiving these calls know they are on the list and why
Frequently asked questions
Can we configure the receptionist to handle clinical questions?
No. Clinical triage and symptom assessment reach a person in every deployment we build. If a provider offers to remove that boundary, treat the offer itself as information about how they manage risk.
What if escalating slows the call down?
For these categories, speed matters less than the caller reaching someone who can genuinely help. Optimise the routine calls instead, where efficiency costs nobody anything.
Can the receptionist take a card payment?
We do not design flows that capture card details in conversation. Route callers to your existing secure payment process instead.
How do we handle a caller who is upset but not in crisis?
Judgement calls belong with people. Set a low threshold for handover and let your team decide, rather than tuning the flow to keep difficult calls inside automation.
Should sensitive calls be recorded?
Consider whether recording serves a purpose you can state, and whether a shorter record would do. The general position is covered in PDPA and call recording.
How do we know the exclusions actually work?
Test each one deliberately, including indirect phrasing, before go-live and after every change, using the approach in testing before go-live.
Related reading
Related call design guidance is collected in the AI receptionist resources library.
Tell us which calls must never be automated
We will build the flow around those boundaries, and show you what happens when a caller raises one of them.