Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added 'message cascade' concept into /routing-plans #60

Closed
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 15 additions & 4 deletions docs/pages/using-nhs-notify/routing-plans.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,18 @@ Setting up a routing plan can make your messages more effective and sometimes lo

You can set up routing plans to:

- use certain templates for specific groups of recipients
- message a recipient with each channel in the order you choose
- set up fallbacks for messages that fail
- stop sending messages after a chosen channel is successful
- [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

## Message cascades

A message cascade allows you to message a recipient with different channels in the order you choose. You can set up primary or secondary message cascades in your routing plan.

### Primary cascades

Use primary message cascades to send a message with a different channel as a fallback if a primary channel fails.

### Secondary cascades

Use a 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 fallback to another channel with secondary cascades.
Loading