Business case and benefits
- Helpline director
- A · Accountable
- Product owner
- R · Responsible
- Solutions architect
- C · Consulted
- Technical PM
- C · Consulted
- Engineers
- I · Informed
- Safeguarding lead
- C · Consulted
- DPO
- I · Informed
- Security
- I · Informed
Advisers spend their time with the caller, not the paperwork. Approved guidance is to hand, notes are drafted, and possible risk is flagged to the adviser and supervisor as it is said. People make every safeguarding decision.
At a glance
An illustrative scenario. The numbers are typical examples, not a client case study. The cloud services and UK rules were checked on 9 November 2026.
A national charity helpline answers people at difficult moments by phone, webchat and email. Trained advisers, many of them volunteers, listen, give information from the charity's approved guidance, find local services, and write up each contact in the case system. A supervisor on each shift supports advisers and steps in when a contact raises a safeguarding concern.
Most contacts are not about risk. But some are, and the signs are rarely stated plainly. A caller mentions in passing that they have been stockpiling tablets, or a young person on webchat says something about an adult at home that only makes sense later in the conversation. Advisers do this well, but they are also searching for guidance, looking up services by postcode and typing notes. After a hard call, the write-up is often thin, and emails wait in a queue in the order they arrived.
Supervisors can only listen to a few calls at a time. Case notes vary in quality, which matters when a referral is questioned later or a serious incident is reviewed. And the guidance and local services directory change often enough that advisers keep their own lists, which go out of date.
Agree these, and measure the baseline, before anything is built. Example targets are typical, not promises.
Adviser time spent writing up after the contact ends.
ExampleDown by a third
A monthly audit of notes against the helpline's recording standard, including how a disclosure and the action taken were recorded.
ExampleUp, against the baseline audit
From a monthly review of contacts with no flag, how many should have had one. Reported honestly, never hidden behind an average.
ExampleKnown, reported and falling
Too many and supervisors stop looking; too few may mean the rules are too narrow.
ExampleWithin an agreed band, reviewed monthly
From the moment a concern is raised to a supervisor joining or being consulted.
ExampleDown, measured on reviewed contacts
Callers who said no to transcription, and whether the service they got was the same.
ExampleEvery one
Cross-sector rules are on the UK regulation map.
Trustees are responsible for keeping people safe, with clear systems for reporting concerns to the police or social services as soon as they are suspected, and policies reviewed after every serious incident and at least yearly. The AI's role, limits and failure modes belong in the safeguarding policy, approved by trustees.
Serious incidents, including significant harm to beneficiaries and significant data breaches, are reported promptly. Trustees stay accountable even when they delegate the report. A person decides; the AI's logs and the signed case note support the decision. Charities registered in Scotland or Northern Ireland follow OSCR's or CCNI's equivalent rules.
Local authorities lead child protection and adult safeguarding enquiries; the helpline's job is to recognise, record and refer. The designated safeguarding lead decides on referrals under the helpline's protocol. Wales, Scotland and Northern Ireland have their own frameworks, so the protocol and the guidance the assistant shows follow the caller's nation.
The Act (2026) creates a duty for people in regulated activity with children in England to report known child sexual abuse to the police or local authority. It isn't in force yet, and the government will publish guidance first. Check whether any helpline roles fall within it, and make sure the case system records a disclosure and the report made clearly.
Contacts reveal health, sex life and criminal allegations. That means a DPIA, an Article 9 condition such as the safeguarding condition in the Data Protection Act 2018, and a lawful basis; the Data (Use and Access) Act added safeguarding vulnerable individuals as a recognised legitimate interest. Callers are told at the start and can say no without any change to the service. Audio and transcripts are kept only until the note is signed, in a UK region, and never used to train providers' models.
MHRA guidance on digital mental health technologies says software that assesses or predicts risk in mental health can be a medical device. Keep the intended purpose narrow and written down: the AI highlights what was said against the helpline's own indicators, for a trained person. It gives no risk score about a person and makes no clinical judgement. Get a regulatory view in discovery.
Showing AWSAzuresovereign / on-prem services. Switch with the toggle; every diagram and table on this page follows it.
01Channels
02Intake
03Intelligence
04Orchestration
05Systems of record
06People
| Layer | AWS | Azure | Sovereign / on-prem |
|---|---|---|---|
| Telephony and chatMost helplines keep their telephony. What matters is a live audio stream the AI can read; agree in discovery what your telephony supplier offers. | Amazon Connect (London), or your existing telephony | Azure Communication Services (UK data location), or your existing telephony | Your existing telephony platform |
| SpeechTest on distressed speech, crying, whispering, regional accents and young callers. Avoid features that process speech outside the UK. | Amazon Transcribe streaming (en-GB, London) | Azure Speech in Foundry Tools (real-time, UK South) | Open-weight speech models (e.g. Whisper) on your own GPUs |
| Drafting and reasoningUse models deployed in the UK region; some are only offered through cross-region or global processing. | Amazon Bedrock | Microsoft Foundry | Open-weight models served with vLLM on your own GPUs, or IONOS AI Model Hub |
| Guidance and services (retrieval)Only approved, versioned guidance and the verified services directory, each answer citing its source. | Bedrock Knowledge Bases | Foundry IQ, built on Azure AI Search | OpenSearch, or PostgreSQL with pgvector |
| Agent runtimeAgentCore Runtime, Gateway and Policy are listed for London. The original Bedrock Agents closed to new customers on 30 July 2026. | Amazon Bedrock AgentCore | Foundry Agent Service | An open-source agent framework (e.g. LangGraph) on Kubernetes |
| Risk indicator flagsTwo layers: plain phrase rules the safeguarding lead owns, and a model that catches indirect wording. Neither produces a score about the person. | Amazon Bedrock, plus Contact Lens real-time rules if you use Amazon Connect | Microsoft Foundry, plus your phrase rules | An open-weight model plus your phrase rules |
| Personal data redactionRedacts transcripts kept for quality review. | Amazon Comprehend PII detection | Azure Language in Foundry Tools (PII detection) | Open-source PII detection (e.g. Presidio) |
| Workflow | AWS Step Functions | Logic Apps or Durable Functions | Temporal, or n8n |
| Alerts and eventsSupervisor alerts are delivered and acknowledged; an unacknowledged alert repeats. | Amazon EventBridge, SQS | Event Grid, Service Bus | Apache Kafka or RabbitMQ |
| GuardrailsKeeps drafts to approved guidance; no clinical or legal advice. | Bedrock Guardrails | Azure AI Content Safety | Open-source guardrails (e.g. NeMo Guardrails, Llama Guard) |
| Identity, keys, data protectionAdvisers see their own contacts; supervisors see alerts for their shift. | IAM Identity Center, KMS, Macie | Entra ID, Key Vault, Purview | Keycloak or your existing Active Directory; OpenBao or HashiCorp Vault; an HSM |
| Monitoring and auditLog every flag, alert, acknowledgement and dismissal with its reason, and the guidance versions shown. | CloudWatch, CloudTrail | Azure Monitor, Log Analytics | Prometheus, Grafana, OpenTelemetry |
| UK data residencySome of the most sensitive data a charity holds. Keep it in the UK. | eu-west-2 (London) | UK South / UK West | Your own UK data centre, or a UK/EU provider (IONOS AI Model Hub runs in Germany) |
On a phone, the table shows the platform you pick. Sovereign / on-prem means open, portable components you can run in your own data centre or with a UK or European provider; IONOS is shown as one example, and others exist. What sovereign cloud means →
Many organisations keep core systems and sensitive data on their own servers. This is how the same design works across both.
Stays on-prem
The case management system, the safeguarding log and the helpline's telephony stay where they are. Signed case notes live only in the case system. The AI never becomes the record of what a caller said.
Uses cloud AI
Live transcription, retrieval of guidance and services, note drafting and risk flags run in a UK cloud region, or on the charity's own GPUs for the sovereign option. Audio and transcripts are held only until the adviser signs the note.
How they connect
A live audio stream from the telephony platform and the case system's published API, over a private link such as AWS Direct Connect or Azure ExpressRoute. Webchat and email arrive through an API gateway.
If the link drops
The helpline carries on exactly as before: advisers listen, use their guidance and write their own notes. Advisers and supervisors see a clear banner saying risk flags are off, so nobody reads silence as safety.
What each agent may do through its tools, what it may not, and where a person signs off. The limits are enforced by the platform, not the prompt.
Adviser assistant
Where a person signs offThe adviser edits and signs every note. Drafts stay marked as drafts until they do. The assistant's access is enforced by the platform's identity and policy controls, not by instructions in a prompt.
Risk indicator flags
Where a person signs offOnly a supervisor can dismiss a flag, with a reason. The designated safeguarding lead decides on referrals, and trustees, or the person they delegate to, decide on serious incident reports.
The telephony platform stays in charge of the call. It sends a live audio stream to transcription only when the caller has agreed, and the adviser can stop it at any point. If the stream fails, the call carries on; only the transcript stops.
The case management system stays the record. Drafts are written to it through its published API as drafts, and only the adviser can sign them. The local services directory is synced from its owner into the retrieval index each night, so out-of-date entries drop out without anyone editing the AI.
Supervisor alerts travel as events with an acknowledgement. An alert that isn't acknowledged within a set time repeats, then goes to the duty manager. If the risk check is down, every adviser and supervisor screen says so.
Map today's contact handling and safeguarding protocol, audit a sample of notes, agree what the telephony and case system allow, and get a regulatory view on intended purpose.
Gate · must be true to passBaseline agreed, DPIA and safeguarding policy changes drafted, designated safeguarding lead and trustees briefed.
Notes and guidance first, with a small group of experienced advisers. Risk flags run in shadow mode, visible only to the reviewing team, and are compared with what advisers and supervisors did.
Gate · must be true to passMissed-flag and alert rates known and accepted by the safeguarding lead, note quality up, trustee sign-off.
Flags go live to advisers and supervisors, with monitoring, the banner when flags are off, and a rollback plan.
Gate · must be true to passMonitoring, support, rollback plan and training in place.
More advisers and volunteers, then webchat and email triage, then other nations' protocols.
Gate · must be true to passEach step passes the same review of misses and alert load.
| Activity | Helpline director | Product owner | Solutions architectI can fill this | Technical PMI can fill this | EngineersI can fill this | Safeguarding lead | DPO | SecurityI can fill this |
|---|---|---|---|---|---|---|---|---|
| Business case and benefits | Accountable | Responsible | Consulted | Consulted | Informed | Consulted | Informed | Informed |
| Target architecture and telephony integration | Consulted | Consulted | Accountable and Responsible | Consulted | Consulted | Consulted | Consulted | Consulted |
| Risk indicators and phrase rules | Consulted | Consulted | Consulted | Informed | Responsible | Accountable | Informed | Informed |
| DPIA and caller information | Consulted | Consulted | Consulted | Informed | Informed | Consulted | Accountable and Responsible | Consulted |
| Build and integration | Informed | Consulted | Accountable | Responsible | Responsible | Consulted | Informed | Consulted |
| Shadow-mode review of flags | Informed | Responsible | Consulted | Responsible | Responsible | Accountable | Informed | Informed |
| Go-live decision | Accountable | Responsible | Consulted | Responsible | Informed | Consulted | Consulted | Consulted |
| Run, monitor and improve | Accountable | Responsible | Consulted | Consulted | Responsible | Consulted | Consulted | Consulted |
R ResponsibleA AccountableC ConsultedI Informed· not involved
Option A
If there's no architect on the programme, I'd own the design end to end: the audio stream from your telephony, transcription, retrieval, the risk flags and how they fail safe, and the gates from shadow mode to live, working closely with your designated safeguarding lead. I'd report to your programme board and your helpline director.
Option B
If your partner, your telephony or case system supplier, or your own team already has an architect, I'd take on the speech, retrieval and alerting pieces under their lead, and give them a second senior opinion on data protection, security and the evidence for going live.
Goes wrong
Advisers start relying on the flag, and silence is read as safety.
How the design avoids it
Training on what flags miss, a banner whenever they are off, and a monthly missed-flag review shared with advisers.
Goes wrong
Indirect disclosures are missed: coded words, young people's language, other languages, a caller who says very little.
How the design avoids it
A test set built from reviewed, anonymised contacts, missed-flag rates measured before go-live, and phrase rules the safeguarding lead can change quickly.
Goes wrong
So many alerts that supervisors stop looking.
How the design avoids it
Alert load measured per shift, rules tuned in shadow mode, and dismissals recorded with reasons.
Goes wrong
Callers aren't told about transcription, or feel pushed to agree.
How the design avoids it
A short script, an easy no, and a check that opt-outs get the same service.
Goes wrong
Flags drift into risk scores, and the tool becomes a medical device without anyone deciding it should.
How the design avoids it
A written intended purpose, no scores about people, and a regulatory view before the pilot.
Changes already announced or under way that affect this design. More in the UK horizon scan.
Make the case note record a disclosure, who was told and the report made. Review which roles are in scope when the guidance appears.
Check the guidance the assistant shows and the helpline's protocol against the new edition.
Write the intended purpose down now and review it as the new guidance lands.
Keep a clear record that a person makes every decision, so the design fits whatever the code asks.
Make sure a caller's complaint about recording or transcription reaches the data protection team with a reference.
Good answers are specific. Vague answers to any of these are worth following up.
Whether you need someone to lead the design or to support the architect you already have, let's talk it through.