Charities and not-for-profit · Playbook 55

Helpline triage with safeguarding

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.

  • Speech and voice
  • Retrieval (RAG)
  • Human in the loop
  • Charity Commission
  • Safeguarding duties
  • UK GDPR
  • ICO
  • MHRA

At a glance

The problem
Advisers listen, search for guidance and local services, then write up each contact, while supervisors can't hear every call
Typical volume
Around 15,000 contacts a month: 60% phone, 30% webchat, 10% email
Who's involved
Helpline managers, advisers and volunteers, shift supervisors, the designated safeguarding lead, data protection, IT
Pilot
10–12 weeks after a 4-week discovery
Platforms
AWS, Azure, or a sovereign or on-prem stack

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.

The business problem

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.

What AI changes

  • With the caller told and able to say no, the call is transcribed live for the adviser only, and the case note is drafted at the end for the adviser to edit and sign.
  • Approved guidance and local services for the caller's area appear beside the conversation, each with its source, so advisers stop keeping private lists.
  • Phrases that match the helpline's risk indicators, such as self-harm, abuse or a child at risk, are highlighted to the adviser and alerted to the shift supervisor as they are said or typed.
  • Emails and webchats with possible risk move up the queue. The AI can raise a contact's priority but never lower it.
  • Flags are a backstop. They will miss things, so advisers keep listening exactly as trained and the supervisor's role doesn't change.
  • The AI never talks to a caller, never decides a safeguarding referral, and never makes a serious incident decision. People do.

How success is measured

Agree these, and measure the baseline, before anything is built. Example targets are typical, not promises.

Time on after-contact notes

Adviser time spent writing up after the contact ends.

ExampleDown by a third

Case note quality

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

Missed-flag rate

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

Alerts per supervisor per shift

Too many and supervisors stop looking; too few may mean the rules are too narrow.

ExampleWithin an agreed band, reviewed monthly

Time from disclosure to supervisor

From the moment a concern is raised to a supervisor joining or being consulted.

ExampleDown, measured on reviewed contacts

Opt-outs honoured

Callers who said no to transcription, and whether the service they got was the same.

ExampleEvery one

UK regulation and controls

Cross-sector rules are on the UK regulation map.

  • Charity CommissionSafeguarding and protecting people for charities and trustees (updated 8 October 2026)

    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.

  • Charity CommissionHow to report a serious incident (updated 16 January 2026)

    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.

  • DfE and DHSCWorking Together to Safeguard Children 2026 and Care Act 2014 section 42 (England)

    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.

  • Home OfficeCrime and Policing Act 2026: mandatory reporting of child sexual abuse

    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.

  • ICOUK GDPR special category data, recording and transcription

    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.

  • MHRASoftware and AI as a medical device

    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.

The solution

Showing AWSAzuresovereign / on-prem services. Switch with the toggle; every diagram and table on this page follows it.

Helpline triage with safeguarding: reference architecture
  1. 01Channels

    • Phone callers
    • Webchat
    • Email
  2. 02Intake

    • Amazon ConnectAzure Communication ServicesYour existing telephony platformCalls and audio stream
    • Amazon Transcribe streamingAzure Speech in Foundry ToolsOpen-weight speech model (e.g. Whisper)Live transcription (with consent)
    • API GatewayAPI ManagementKong, or your existing API gatewayChat and email intake
  3. 03Intelligence

    • Bedrock Knowledge BasesFoundry IQ (Azure AI Search)OpenSearch, or PostgreSQL with pgvectorGuidance and local services
    • Agent
      Bedrock AgentCoreFoundry Agent ServiceLangGraph on KubernetesAdviser assistant
    • Agent
      Amazon Bedrock plus your phrase rulesMicrosoft Foundry plus your phrase rulesOpen-weight model plus your phrase rulesRisk indicator flags
  4. 04Orchestration

    • Step FunctionsLogic Apps / Durable FunctionsTemporal, or n8nContact workflow
    • EventBridge + SQSEvent Grid + Service BusApache Kafka or RabbitMQSupervisor alerts
  5. 05Systems of record

    • Case management system
    • Local services directory
    • Safeguarding log
  6. 06People

    • Person
      Adviser: listens, decides, signs
    • Person
      Shift supervisor
    • Person
      Designated safeguarding lead
  • Cloud or platform service (AWSAzuresovereign / on-prem)
  • AI agent
  • A person decides
  • Your existing systems
  • Outside your organisation

Components, side by side

Helpline triage with safeguarding: components on AWS, Azure and a sovereign or on-prem stack
LayerAWSAzureSovereign / 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 telephonyAzure Communication Services (UK data location), or your existing telephonyYour 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 BedrockMicrosoft FoundryOpen-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 BasesFoundry IQ, built on Azure AI SearchOpenSearch, 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 AgentCoreFoundry Agent ServiceAn 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 ConnectMicrosoft Foundry, plus your phrase rulesAn open-weight model plus your phrase rules
Personal data redactionRedacts transcripts kept for quality review.Amazon Comprehend PII detectionAzure Language in Foundry Tools (PII detection)Open-source PII detection (e.g. Presidio)
WorkflowAWS Step FunctionsLogic Apps or Durable FunctionsTemporal, or n8n
Alerts and eventsSupervisor alerts are delivered and acknowledged; an unacknowledged alert repeats.Amazon EventBridge, SQSEvent Grid, Service BusApache Kafka or RabbitMQ
GuardrailsKeeps drafts to approved guidance; no clinical or legal advice.Bedrock GuardrailsAzure AI Content SafetyOpen-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, MacieEntra ID, Key Vault, PurviewKeycloak 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, CloudTrailAzure Monitor, Log AnalyticsPrometheus, 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 WestYour 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 →

Hybrid and on-prem

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.

The agents

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

May do

  • Show the adviser a live transcript, when the caller has agreed
  • Find approved guidance and local services for the caller's area
  • Show the helpline's protocol steps that match what has been said
  • Draft the case note in the helpline's template for the adviser

May not do

  • Speak or type to a caller, or send anything to them
  • Make a referral or contact emergency services
  • Record a safeguarding decision, or close a case
  • Give advice beyond the approved guidance
  • Keep audio or transcripts after the note is signed

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

May do

  • Highlight phrases that match the helpline's risk indicators
  • Alert the adviser and the shift supervisor at the same moment
  • Move an email or webchat up the queue
  • Log each flag for the monthly review

May not do

  • Lower a contact's priority or clear a flag
  • Give a risk score or a judgement about the person
  • Decide a contact is safe
  • Start a referral or a serious incident report

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.

Middleware and integration

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.

Process and people

  • A supervisor on every shift, as now. The AI changes what they can see, not their role.
  • The designated safeguarding lead owns the risk indicators and phrase rules, and signs off every change after testing.
  • A monthly review of a sample of contacts with no flag, to find what was missed, and of dismissed flags, to check the reasons.
  • A short script for telling callers about transcription, and a rule that saying no changes nothing about the help they get.
  • Training for advisers and volunteers on what the flags miss, before they use them.
  • Support for advisers' wellbeing, since transcripts make hard contacts easier to revisit.

Delivery plan

  1. 4 weeks

    Discovery

    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.

  2. Gate · must be true to passBaseline agreed, DPIA and safeguarding policy changes drafted, designated safeguarding lead and trustees briefed.

  3. 10–12 weeks

    Pilot

    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.

  4. Gate · must be true to passMissed-flag and alert rates known and accepted by the safeguarding lead, note quality up, trustee sign-off.

  5. 4–6 weeks

    Production

    Flags go live to advisers and supervisors, with monitoring, the banner when flags are off, and a rollback plan.

  6. Gate · must be true to passMonitoring, support, rollback plan and training in place.

  7. Ongoing

    Scale

    More advisers and volunteers, then webchat and email triage, then other nations' protocols.

  8. Gate · must be true to passEach step passes the same review of misses and alert load.

Roles and RACI

Who is responsible, accountable, consulted and informed, by activity
ActivityHelpline directorProduct ownerSolutions architectI can fill thisTechnical PMI can fill thisEngineersI can fill thisSafeguarding leadDPOSecurityI can fill this
Business case and benefitsAccountableResponsibleConsultedConsultedInformedConsultedInformedInformed
Target architecture and telephony integrationConsultedConsultedAccountable and ResponsibleConsultedConsultedConsultedConsultedConsulted
Risk indicators and phrase rulesConsultedConsultedConsultedInformedResponsibleAccountableInformedInformed
DPIA and caller informationConsultedConsultedConsultedInformedInformedConsultedAccountable and ResponsibleConsulted
Build and integrationInformedConsultedAccountableResponsibleResponsibleConsultedInformedConsulted
Shadow-mode review of flagsInformedResponsibleConsultedResponsibleResponsibleAccountableInformedInformed
Go-live decisionAccountableResponsibleConsultedResponsibleInformedConsultedConsultedConsulted
Run, monitor and improveAccountableResponsibleConsultedConsultedResponsibleConsultedConsultedConsulted

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

Target architecture and telephony integration

Helpline director
C · Consulted
Product owner
C · Consulted
Solutions architect
A/R · Accountable and Responsible
Technical PM
C · Consulted
Engineers
C · Consulted
Safeguarding lead
C · Consulted
DPO
C · Consulted
Security
C · Consulted

Risk indicators and phrase rules

Helpline director
C · Consulted
Product owner
C · Consulted
Solutions architect
C · Consulted
Technical PM
I · Informed
Engineers
R · Responsible
Safeguarding lead
A · Accountable
DPO
I · Informed
Security
I · Informed

DPIA and caller information

Helpline director
C · Consulted
Product owner
C · Consulted
Solutions architect
C · Consulted
Technical PM
I · Informed
Engineers
I · Informed
Safeguarding lead
C · Consulted
DPO
A/R · Accountable and Responsible
Security
C · Consulted

Build and integration

Helpline director
I · Informed
Product owner
C · Consulted
Solutions architect
A · Accountable
Technical PM
R · Responsible
Engineers
R · Responsible
Safeguarding lead
C · Consulted
DPO
I · Informed
Security
C · Consulted

Shadow-mode review of flags

Helpline director
I · Informed
Product owner
R · Responsible
Solutions architect
C · Consulted
Technical PM
R · Responsible
Engineers
R · Responsible
Safeguarding lead
A · Accountable
DPO
I · Informed
Security
I · Informed

Go-live decision

Helpline director
A · Accountable
Product owner
R · Responsible
Solutions architect
C · Consulted
Technical PM
R · Responsible
Engineers
I · Informed
Safeguarding lead
C · Consulted
DPO
C · Consulted
Security
C · Consulted

Run, monitor and improve

Helpline director
A · Accountable
Product owner
R · Responsible
Solutions architect
C · Consulted
Technical PM
C · Consulted
Engineers
R · Responsible
Safeguarding lead
C · Consulted
DPO
C · Consulted
Security
C · Consulted

R ResponsibleA AccountableC ConsultedI Informed· not involved

Where I'd fit

Option A

Lead the architecture

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

Support your architect

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.

Where this goes wrong

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

On the horizon

Changes already announced or under way that affect this design. More in the UK horizon scan.

  1. Not yet in force
    The mandatory duty to report child sexual abuse in the Crime and Policing Act 2026, for people in regulated activity with children in England. The government will publish guidance before it starts.

    Make the case note record a disclosure, who was told and the report made. Review which roles are in scope when the guidance appears.

  2. Published March 2026
    Working Together to Safeguard Children 2026 replaced the 2023 edition, with stronger expectations on child sexual abuse.

    Check the guidance the assistant shows and the helpline's protocol against the new edition.

  3. 2027
    After the national commission on regulating AI in healthcare, the MHRA plans a 2027 consultation on how AI devices are qualified and classified, and a full roadmap in spring 2027.

    Write the intended purpose down now and review it as the new guidance lands.

  4. Being written
    The ICO's code of practice on AI and automated decision-making, required by SI 2026/425.

    Keep a clear record that a person makes every decision, so the design fits whatever the code asks.

  5. In force since 19 June 2026
    The Data (Use and Access) Act's data protection complaints duty: easy to make, acknowledged within 30 days.

    Make sure a caller's complaint about recording or transcription reaches the data protection team with a reference.

Questions to ask your partner or vendor

Good answers are specific. Vague answers to any of these are worth following up.

Copy them into your next supplier meeting

  1. How often does the flag miss a real disclosure, and how will we keep measuring it?
  2. What do advisers and supervisors see when the risk check is down?
  3. Where is audio processed and stored, and when is it deleted?
  4. Who owns the risk indicators, and how is a change tested before it goes live?
  5. What happens when a caller says no to transcription?
  6. What exactly is the intended purpose, and who decided it isn't a medical device?

Planning something like this?

Whether you need someone to lead the design or to support the architect you already have, let's talk it through.

Sam Naseem
Sam NaseemBirmingham, UK · UK & Europe
Available now