From bd39496f649a4fe7467e0a7aa4803f5f77da6534 Mon Sep 17 00:00:00 2001 From: emmagifford <162720670+emmagifford@users.noreply.github.com> Date: Mon, 13 Apr 2026 13:45:37 +0000 Subject: [PATCH 1/4] Update /message-plans --- docs/pages/using-nhs-notify/message-plans.md | 41 +++++++++++--------- 1 file changed, 23 insertions(+), 18 deletions(-) diff --git a/docs/pages/using-nhs-notify/message-plans.md b/docs/pages/using-nhs-notify/message-plans.md index b4439d62..1c6dc016 100644 --- a/docs/pages/using-nhs-notify/message-plans.md +++ b/docs/pages/using-nhs-notify/message-plans.md @@ -3,39 +3,44 @@ # To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults layout: page -title: Routing plans +title: Message plans parent: Using NHS Notify nav_order: 4 -permalink: /using-nhs-notify/routing-plans +permalink: /using-nhs-notify/message-plans section: Sending a message --- -You'll need to create a routing plan to decide how messages will be sent to your recipients. +Use message plans to tell us how to send messages to your recipients. You can choose which message channels to use and in what order. -Setting up a routing plan can make your messages more effective and sometimes lower messaging costs. +You can set up message plans yourself in your NHS Notify account. We no longer need to set these up for you. -You can set up routing plans to: +## Choosing your message order -- [send messages in a cascade](#message-cascades) -- use specific message templates for different groups of recipients -- stop sending messages to a recipient when a channel is successful +You can choose from a list of pre-defined message plans. -## Routing plans and contact details from the Personal Demographics Service (PDS) +For example: NHS App, email, text message, letter. -NHS Notify checks for each recipient's contact details before we send any messages using a routing plan. +How fallbacks work +If we cannot deliver a message through your first choice, we automatically try the next channel in your message plan. -This means that if we do not find a recipient's contact details for a message channel, we'll automatically skip that channel. +A fallback happens if: -We do not re-check for contact details each time there's a fallback in a routing plan. +- the recipient does not have valid contact details for a channel +- the message is not read or delivered within a certain amount of time +- the message fails to send for a technical reason -## Message cascades +We'll stop sending messages once a chosen channel is successful. -A message cascade allows you to message a recipient with different channels in the order you choose. You can set up primary and secondary message cascades in your routing plan. +For example, you might try to send an NHS App message first. If the recipient reads the message within 24 hours, no further messages get sent. If the recipient does not read the first message within 24 hours, we'll then try to send an email. -### Primary cascades +## Linking your templates -Use primary message cascades to send a message with a different channel as a fallback if a primary channel fails. +You can choose specific templates for each channel in your message plan. -### Secondary cascades +## Contact details -Use secondary message cascades to send a message with another channel at the same time as your primary channel. For example, sending a text message at the same time as an email. You cannot fall back to another channel with secondary cascades. +We check the Personal Demographics Service (PDS) for each recipient's contact details before we start sending messages. + +If we do not have a contact detail for a specific channel, we'll skip that channel and move to the next one in your message plan. + +We only check for contact details once at the start. We do not re-check PDS each time there is a fallback. From c606bb4d0193339234209d9c6d6eba16a70c9823 Mon Sep 17 00:00:00 2001 From: emmagifford <162720670+emmagifford@users.noreply.github.com> Date: Mon, 13 Apr 2026 14:03:46 +0000 Subject: [PATCH 2/4] Add page breaks section to /upload-a-letter --- docs/pages/using-nhs-notify/upload-a-letter.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/pages/using-nhs-notify/upload-a-letter.md b/docs/pages/using-nhs-notify/upload-a-letter.md index ce89f2d6..2abfb38a 100644 --- a/docs/pages/using-nhs-notify/upload-a-letter.md +++ b/docs/pages/using-nhs-notify/upload-a-letter.md @@ -75,6 +75,7 @@ Find out how to use: - [personalisation](#personalisation) - [headings](#headings) - [paragraphs and body text](#paragraphs-and-body-text) +- [page breaks](#page-breaks) - [links and URLs](#links-and-urls) - [bullet points](#bullet-points) - [images](#images) @@ -143,6 +144,10 @@ Paragraphs can be split across 2 pages. If you do not want a paragraph to run over different pages, add a page break before the paragraph. +## Page breaks + +Select 'Insert', 'Pages' then 'Page break' in Microsoft Word to add a page break. + ## Links and URLs Use the style 'Hyperlink' in the template for links. From 6ff185a3118f2a02419b78aa50062d1ba027ef6d Mon Sep 17 00:00:00 2001 From: emmagifford <162720670+emmagifford@users.noreply.github.com> Date: Mon, 13 Apr 2026 14:58:06 +0000 Subject: [PATCH 3/4] Change all references to routing plans to message plans --- docs/_data/home/how-it-works.yml | 2 +- docs/_includes/components/styled-list.html | 4 +- .../campaign-feature-list.html | 134 +++++++++++++---- .../direct-message-feature-list.html | 132 +++++++++++++---- .../transactional-feature-list.html | 136 ++++++++++++++---- docs/pages/about/about.md | 8 +- docs/pages/about/new-and-upcoming-features.md | 4 +- .../check-you-are-ready-for-integration.md | 2 +- docs/pages/get-started/onboard-with-notify.md | 2 +- .../using-nhs-notify/(draft)accordion-test.md | 110 -------------- .../using-nhs-notify/accessible-formats.md | 4 +- .../using-nhs-notify/complete-your-testing.md | 20 +-- docs/pages/using-nhs-notify/message-status.md | 8 +- .../using-nhs-notify/using-nhs-notify.md | 2 +- 14 files changed, 355 insertions(+), 213 deletions(-) delete mode 100644 docs/pages/using-nhs-notify/(draft)accordion-test.md diff --git a/docs/_data/home/how-it-works.yml b/docs/_data/home/how-it-works.yml index ed529f55..656f7e8f 100644 --- a/docs/_data/home/how-it-works.yml +++ b/docs/_data/home/how-it-works.yml @@ -16,7 +16,7 @@ - heading: Plan how your messages will be sent description: | - Set up routing plans to decide how your messages will be sent to recipients. + Set up message plans to decide how your messages will be sent to recipients. image: 3-plan-your-messages.svg image_alt: "" number: 3 diff --git a/docs/_includes/components/styled-list.html b/docs/_includes/components/styled-list.html index 6669cceb..1cecd7dc 100644 --- a/docs/_includes/components/styled-list.html +++ b/docs/_includes/components/styled-list.html @@ -15,8 +15,8 @@
You can send campaign messages in the following ways:
All digital message channels will immediately fallback to the next channel if its rejected or an 'unnotified' @@ -250,13 +314,17 @@
Emails and text messages will fallback to the next channel if they are not delivered after 72 hours
-Letters do not have any fallback rules as they’re always sent last in routing plans for +
Letters do not have any fallback rules as they’re always sent last in message plans for transactional messages.
If you send direct messages with the NHS App you must adhere to the following: @@ -252,7 +316,11 @@
You can send event based messages in the following ways:
All digital message channels will immediately fallback to the next channel if its rejected or an 'unnotified' status is received.
-The following fallback rules will apply to message channels used in your routing plans:
+The following fallback rules will apply to message channels used in your message plans:
NHS App messages will fallback to the next channel when:
Emails and text messages will fallback to the next channel if they are not delivered after 72 hours
-Letters do not have any fallback rules as they’re always sent last in routing plans for transactional +
Letters do not have any fallback rules as they’re always sent last in message plans for transactional messages.