Bright, bouncy takes on the world

,

How GOV.UK Notify Became the Invisible Tech Backbone Sending Millions of Texts and Emails to Britons Every Day

Sophie Davis Avatar

There is a piece of software quietly running underneath a huge slice of British daily life, and almost nobody outside of a developer Slack channel has heard of it. Every time you get a text reminding you about your NHS appointment, an email from HMRC about your tax code, or a council notification about your recycling collection being moved, there is a decent chance GOV.UK Notify sent it. Not a private SaaS company. Not a big tech giant with a flashy logo. A government-built API, maintained by the Government Digital Service (GDS), sitting at the centre of how the UK state talks to its citizens. Quietly brilliant, and almost entirely invisible.

Developers working on the GOV.UK Notify API in a modern government digital services office
Photo by Quang Vuong on Pexels

I find the whole thing genuinely fascinating, partly because it is one of those rare cases where a government technology project actually worked. Notify launched in 2016 and has spent the better part of a decade expanding its reach. By 2025, it was processing over 10 billion notifications a year across email, SMS, and letter formats. That is not a rounding error. That is a number that puts it comfortably alongside some of the largest commercial messaging platforms operating in the UK.

What the GOV.UK Notify API actually does

At its core, Notify is a transactional messaging service. Organisations with access send it a message template and a recipient, and Notify handles delivery. It manages the relationships with telecoms providers, handles bounce rates, tracks delivery receipts, and provides a simple dashboard so service teams can see what is happening. The API itself is RESTful and well-documented, which matters a lot. Poorly documented government APIs are basically a tradition in this country, so the fact that developers routinely describe Notify’s docs as clear and reliable is almost a news story on its own.

NHS England uses it extensively. Local councils across England, Scotland, and Wales use it. HMRC uses it for everything from self-assessment reminders to notifications about PAYE coding changes. The Ministry of Justice sends prisoner licence notifications through it. Courts send hearing reminders. Dozens of services that most people interact with without a second thought are quietly routing their communications through this one shared platform. If you have ever read about the NHS experimenting with AI triage tools, it is worth knowing that the notification layer underneath a lot of those services runs on exactly this kind of infrastructure.

Why developers are building on top of it

Here is where it gets interesting for the tech crowd. Notify is not just for big government departments. Any UK public sector body can apply for access, and the eligibility definition has gradually widened. Arm’s-length bodies, NHS trusts, registered charities delivering public services, and even some regulated private contractors delivering government contracts have found their way onto the platform. That opens up a surprisingly large space for startups building products in the civic tech or public sector SaaS world.

NHS appointment reminder notification on a smartphone, powered by the GOV.UK Notify API
Photo by Nothing Ahead on Pexels

The economics are genuinely compelling. Notify is free to use up to a generous monthly limit (currently 250,000 emails, 25,000 texts, and 5,000 letters per year, with higher volumes available on request). For a startup building a tool for local councils or NHS trusts, removing the cost and complexity of managing your own transactional messaging infrastructure is a meaningful advantage. You do not have to negotiate contracts with SMS gateways, worry about deliverability, or maintain your own opt-out lists. The platform handles all of that. I have spoken to a handful of developers working in this space and the consensus is pretty consistent: Notify is one of the genuinely good things GDS has produced, and more startups should know it exists.

The tech commentary site The Ice Age has written thoughtfully about how this kind of shared government infrastructure creates both opportunity and dependency for the startups building on top of it, which is a tension worth sitting with. When a single API handles this volume of citizen communications, the resilience question becomes serious. What happens when it goes down? The GDS publishes a status page and the platform has a strong uptime record, but the concentration of risk is real.

The letters feature nobody talks about

Everyone focuses on the SMS and email functionality, which is fair, but Notify also sends physical letters. Actual paper, printed and posted by Royal Mail. Government teams can trigger a letter through the same API call they would use for an email, and Notify handles the print-and-post relationship. For services that need to reach people without reliable internet access or those who simply prefer written correspondence, this is quietly remarkable. It also means a single developer can build a service that communicates with citizens across every channel from one codebase, with one set of templates. The accessibility implications alone make this worth highlighting, especially for services reaching elderly residents or people in low-connectivity areas. Speaking of which, if you are curious about how communities are solving connectivity gaps themselves, the story of rural villages building their own broadband networks is a brilliant read alongside this one.

The broader pattern here is one of infrastructure thinking rather than product thinking. Instead of every government department building its own messaging system (which was absolutely what was happening before Notify existed, with predictably terrible results), GDS built one shared platform and made it easy to adopt. It is the same logic behind GOV.UK Pay and GOV.UK One Login. You reduce duplication, raise the floor on quality, and free up teams to focus on the actual service rather than the plumbing.

What the subscription economy tells us about notification fatigue

There is an irony lurking here. Notify is genuinely useful precisely because it sends things people actually need to receive. But as Britons grow increasingly fed up with the volume of digital communications landing in their inboxes each month, even well-intentioned government notifications face a trust problem. If your phone buzzes forty times a day with app alerts, there is a real risk that an HMRC reminder starts getting dismissed alongside the promotional nonsense. The platform is only as useful as the content it carries, and the teams using it still have to do the hard work of writing messages that people will actually read and act on.

GDS has tried to address this with guidance on writing notifications, tone of voice standards, and template review processes. Whether that is enough in a world where AI is increasingly generating communications across every sector is an open question. For what it is worth, researchers working in civic tech fields have started thinking about how algorithmic personalisation might eventually touch government messaging too. The parallel with commercial AI tools is interesting: just as some are exploring how AI shapes personalised recommendations for consumers, there are questions about whether government notifications could eventually be tailored more intelligently to individual circumstances and preferences.

For now, though, Notify keeps doing its job. Billions of messages. NHS appointment reminders landing on time. HMRC alerts that actually get through. Council tax notifications that do not require a login, a PDF, and three browser tabs to parse. It is unglamorous, infrastructure-level work, and it matters enormously. For more on how GDS built it and what the Government Digital Service has published about its approach to shared platforms, their official pages are worth a read if you are the kind of person who finds this stuff as absorbing as I do.

Not every piece of government technology is a cautionary tale. Sometimes they just build something that works.

Frequently Asked Questions

What is GOV.UK Notify and who can use it?

GOV.UK Notify is a free government messaging platform that lets public sector organisations send emails, text messages, and letters to citizens. It is available to UK government departments, NHS trusts, local councils, arm’s-length bodies, and some registered charities delivering public services.

How much does GOV.UK Notify cost?

Notify is free to use up to a defined annual limit: currently 250,000 emails, 25,000 text messages, and 5,000 letters per year. Higher volumes can be requested, and there is no charge for the core API access. Letters do incur a small per-unit cost to cover print and postage.

Is GOV.UK Notify reliable enough for critical services like NHS appointment reminders?

GDS publishes a live status page for Notify and the platform has maintained a strong uptime record since its 2016 launch. It is trusted by NHS England, HMRC, and dozens of local councils for time-sensitive communications, though like any centrally managed service it represents a single point of dependency for organisations that rely on it.

Sophie Davis Avatar

Written by

Keep it rolling

One response to “How GOV.UK Notify Became the Invisible Tech Backbone Sending Millions of Texts and Emails to Britons Every Day”

  1. […] is the same quiet shift happening across public services, as we covered in our look at how GOV.UK Notify sends millions of texts and emails. Done well, it means fewer phone calls at a time when you least want to make […]

Leave a Reply

Your email address will not be published. Required fields are marked *