When going live, make reply-to address and text message sender dependent on estimated sending volumes #2827
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have a number of go live requests where people have said they’re sending text messages, but haven’t changed the text message sender from the default of
GOVUK
(we ask teams who aren’t central government to do this). Or they say they’re sending emails but have no email templates, or any email reply-to addresses.At the moment we don’t prompt them to, because we look at what kinds of templates they have to indicate what kinds of messages they’re going to send.
Now that we explicitly ask for their estimated sending volumes we should use this to determine what we prompt them about because it’s a stronger signal of intent than what templates they’ve set up.
For templates we’re going to ask that they at least have one kind of template of the sort they intend to send. We could be even stricter and say they have to have at least one of each type they
expect to send, but we think that we can get a pretty good idea from just looking at one template whether they’re doing something sensible.