Data protection

Texting patients: consent, content and confidentiality

What a GP surgery, dental practice or clinic can put in a text to a patient under UK GDPR, when consent is needed, and how to handle shared phone numbers.

Ava research teamPublished 7 min read

On this page
  1. Why texting needs its own rules
  2. Do you need consent to text a patient?
  3. What each type of text can say
  4. Writing the text: a template checklist
  5. Shared phones, changed numbers and children
  6. Example: one wrong number, two decisions
  7. Replies, links and fake texts
  8. Keeping a record of what was sent
  9. Frequently asked questions
  10. References

Key takeaways

  • Care texts such as reminders and recalls do not need UK GDPR consent, but patients must be told about them and be able to choose another channel.
  • Marketing texts are different: under PECR they need prior consent unless the soft opt-in genuinely applies.
  • Write every text for the person who might read it on someone else's lock screen: name of the practice, the action needed, no diagnosis.
  • Shared, changed and children's numbers cause most texting incidents, so check the number on the record at every contact.

Why texting needs its own rules

Texting is now part of ordinary practice life. NHS England reports that every GP practice in England offered digital messaging by 2025/26[1], and patients are moving the same way: the share who last contacted their practice online rose from 16.8% in 2024 to 30.8% in 2026[2]. Dental practices and private clinics send reminders, recalls and payment links by text as a matter of routine.

Patients whose last contact with their GP practice was onlineGP Patient Survey, England
Patients whose last contact with their GP practice was onlineColumn chart. 2024: 16.8%; 2025: 22.4%; 2026: 30.8%.0%10%20%30%40%2024: 16.8%16.8%20242025: 22.4%22.4%20252026: 30.8%30.8%2026Patients whose last contact with their GP practice was onlineColumn chart. 2024: 16.8%; 2025: 22.4%; 2026: 30.8%.0%10%20%30%40%2024: 16.8%16.8%20242025: 22.4%22.4%20252026: 30.8%30.8%2026

Source: Ipsos (GP Patient Survey provider for NHS England), 2026[2]

Show the data
ItemValue
202416.8%
202522.4%
202630.8%

The problem is that a text lands on a device you do not control. Phones are shared by couples, borrowed by teenagers, handed to carers and left face up on desks with message previews switched on. Anything about a patient's health is special category data under Article 9 of UK GDPR[3], and the Caldicott Principles ask you to use only the minimum confidential information necessary for the purpose[4]. A text that says too much can be a data breach the moment it is delivered to the wrong person, or read by the right person's partner.

For texts that support a patient's care, consent is usually the wrong lawful basis under UK GDPR. An NHS practice normally relies on its public task, with the health and social care condition for special category data. A private clinic usually relies on the contract with the patient or on legitimate interests, again with the health care condition. Asking for UK GDPR consent to send appointment reminders creates a problem you do not need: if consent is your basis, a patient can withdraw it and you must then stop.

What patients do need is transparency and a real choice of channel. Your privacy notice should say that you send reminders, recalls and requests to contact the practice by text, and reception should be able to switch a patient to letters or calls on request. Record that preference where every member of staff will see it.

Marketing is the exception. Under regulation 22 of the Privacy and Electronic Communications Regulations, a text promoting a service needs the person's prior consent unless the soft opt-in applies, which only covers similar products and services offered to someone whose details you collected during a sale and who was given a simple way to refuse[5]. Where a recall stops and a promotion starts is covered in service messages versus marketing, and the consent rules for clinics are in PECR for private clinics.

What each type of text can say

A working guide to text content by message type. Check it against your own privacy notice and clinical policies.
Message typeUsual basisSafe contentAvoid
Appointment reminderCare: no consent needed, opt-out offeredPractice name, date, time, how to cancelClinic name that reveals a condition, such as a sexual health or memory clinic
Recall (check-up, review, screening)Care: no consent neededThat a review is due and how to bookThe condition being reviewed
Request to contact the practiceCarePlease call or reply via the online formResults, abnormal values, urgency wording that alarms
Normal result notificationCare, if the practice policy allowsYour recent result needs no further actionTest names that reveal a condition
Payment link or invoice (private)ContractAmount due and a link from a domain patients recogniseTreatment details in the message body
Offer, new service or seasonal promotionMarketing: PECR consent or soft opt-inClear sender, opt-out in every messageSending to anyone without a recorded basis

A useful test before sending any template: would this message embarrass or harm the patient if their employer, parent or partner read it on the lock screen? If yes, cut it back to the practice name and the action needed.

Writing the text: a template checklist

Most practices send texts from templates in the clinical system or a messaging tool, so the template review is where you control risk. Review every template once a year and whenever a new one is added.

  • Start with the practice name so the patient knows who is writing before they open anything.
  • Use the patient's first name only, or no name at all for recall batches sent to whole households.
  • Say what you want the patient to do: book, call, reply, or nothing.
  • Leave out diagnoses, test names, medicines and the name of a specialist clinic.
  • If you include a link, make it a domain patients already know, such as your website or the NHS App, never a shortened link that hides the destination.
  • State whether replies are read. If they are not, say how to contact the practice instead.
  • Add a line that the practice will never ask for bank details or passwords by text.

Example: two versions of the same fictional message show the difference. Too much: ‘Hi Sam, your HbA1c was 64 and Dr Patel wants to change your metformin, please call.’ Better: ‘Hillside Surgery: please call us on our usual number or use our online form about your recent test. Replies to this number are not read.’ The second version still gets the patient to act, and gives nothing away if someone else reads it.

Shared phones, changed numbers and children

The most common texting incidents are not hacks. They are messages sent to an old number that now belongs to someone else, to a parent's phone after a teenager has asked for confidentiality, or to a carer who is not authorised to see the information. A short routine at reception prevents most of them.

  1. Confirm the number at every contact

    When a patient phones or attends, read the mobile number on the record back to them and ask whether it is still theirs alone. Update it straight away if it has changed.

  2. Flag shared and proxy numbers

    If the number belongs to a family member or carer, add an alert so templates with any health content are not sent there, and record what the patient has agreed can be shared.

  3. Handle young people's numbers carefully

    When a young person who is competent to make their own decisions asks for confidentiality, check whether the mobile on the record is theirs or a parent's before any text is sent.

  4. Stop on a bounce or a wrong-person reply

    If someone replies to say they are not the patient, remove the number, tell the information governance lead and decide whether the content sent amounts to a breach that needs logging.

  5. Check batches before sending

    Recall and flu campaigns go to hundreds of patients at once. Ask a second person to check the search criteria and the template before the batch goes.

Example: one wrong number, two decisions

Example: Northgate Dental, a fictional mixed practice, sends a reminder for a hygienist appointment to a number a patient gave up a year ago. The new owner replies asking who the patient is. The reminder only said ‘Northgate Dental: reminder of your appointment on Tuesday at 10:20. Reply C to cancel.’ The manager logs the incident, removes the number and contacts the patient by email to update the record. Because the message contained no health information beyond the fact of a dental appointment, the manager records the reasoning and decides the risk to the patient is low.

Example: the same month, a template for orthodontic reviews still includes the words ‘brace adjustment’ and the patient's full name. The manager rewrites it to match the other templates. The lesson is that the template review, not the reply, is where the real control sits.

Two-way texting is useful for cancellations and short answers, but decide in advance what a reply can and cannot do. A reply of C to cancel is fine. A patient replying with symptoms to an unmonitored number is a safety risk, so the template must say clearly whether replies are read and how to get urgent help instead.

Patients also receive scam texts that pretend to come from the NHS or a dentist and ask for payment or login details. Keep your own messages predictable, use the same sender name every time, and publish on your website the kinds of text you send. That makes a fake easier to spot and gives reception a simple answer when a worried patient calls.

Keeping a record of what was sent

Texts with clinical meaning, such as a request to book after an abnormal result, should be traceable from the patient's record, with the date, the template used and the number it went to. Messaging systems keep delivery logs, but those logs belong to the supplier's platform, so check how long they are kept and whether you can export them if a patient complains or makes a subject access request.

  1. Keep a list of approved templates with an owner and a review date.
  2. Record channel preferences and shared-number alerts in the clinical system, not on sticky notes.
  3. Log wrong-number and wrong-person incidents, even when no report to the regulator is needed.
  4. Confirm that your messaging supplier has a written processing contract with you.

For messages that need more detail than a text can safely carry, a secure email or the NHS App is usually the better route. See emailing patients securely and the patterns behind common data breaches in practices.

Frequently asked questions

Do we need written consent to send appointment reminders by text?

No. Reminders and recalls support care, so NHS practices usually rely on their public task and private clinics on their contract or legitimate interests. Tell patients in your privacy notice and let them choose another channel.

Can we text test results?

Only within a written practice policy, and usually only to say a result is normal or that the patient should contact you. Leave test names and values out of the message[4].

Is a text about a new treatment marketing?

Yes, if it promotes a service rather than supporting care the patient is already receiving. Under PECR it needs prior consent or a genuine soft opt-in, plus an easy opt-out[5].

What if a text goes to the wrong person?

Remove the number, log the incident, assess the risk to the patient from what the message said and decide whether it must be reported. Contact the patient to correct their details.

References

  1. NHS England (via GOV.UK) (2026). NHS England annual report and accounts 2025 to 2026 (opens in a new tab) ↑

  2. Ipsos (GP Patient Survey provider for NHS England) (2026). 2026 GP Patient Survey results released (opens in a new tab) ↑

  3. legislation.gov.uk (The National Archives) (2026). UK GDPR Article 9: Processing of special categories of personal data (opens in a new tab) ↑

  4. GOV.UK (National Data Guardian) (2020). The Caldicott Principles (opens in a new tab) ↑

  5. legislation.gov.uk (The National Archives) (2026). Privacy and Electronic Communications Regulations 2003, regulation 22 (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo