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

When going live, make reply-to address and text message sender dependent on estimated sending volumes #2827

Merged
merged 3 commits into from
Mar 8, 2019

Conversation

quis
Copy link
Member

@quis quis commented Mar 4, 2019

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.

quis added 3 commits March 5, 2019 10:05
We have a number of go live requests where people have said they’re
sending email, but haven’t set up a reply-to address. At the moment we
don’t prompt them to, because we look at whether they have email
templates as indicative of whether they’re going to send email.

Now that we explicitly ask for the volumes of email they’re sending we
should use this to determine whether or not we prompt them to set up an
email reply to address because it’s a stronger signal of intent than
what templates they’ve set up.
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). At the moment we don’t prompt them to, because we look at whether
they have text message templates as indicative of whether they’re going
to send text messages.

Now that we explicitly ask for the volumes of text messages they’re
sending we should use this to determine whether or not we prompt them to
change their text message sender because it’s a stronger signal of
intent than what templates they’ve set up.
If you have email templates but haven’t told us what volumes you’re
sending we should assume you are going to send emails. We should only
stop asking you to add a reply-to address once you’ve told us for sure
you’re not going to send any emails.

This also applies to changing the text message sender – this should only
be hidden if you don’t have text message templates or you’ve said you’re
not going to be sending any text messages.
@quis quis force-pushed the depend-on-service-volumes branch from 87e62a0 to 87c62e6 Compare March 5, 2019 11:03
@quis
Copy link
Member Author

quis commented Mar 5, 2019

Updates:

  • Roll back eff86d2 (Make required templates dependent on volumes). We’ve decided that it’s confusing that you can’t make the templates checklist item complete until you’ve told us the volumes, and that it would also be confusing to hide it until you’ve completed the volumes.
  • Show the email reply to address and text message sender tasks if you have relevant templates but haven’t yet told us your volumes (on the assumption that you probably intend to send emails if you have some email templates). See 87c62e6 for more detail.

@quis quis changed the title When going live, make reply-to address, text message sender and required templates tasks dependent on estimated sending volumes When going live, make reply-to address and text message sender dependent on estimated sending volumes Mar 5, 2019
@quis quis merged commit cd59919 into master Mar 8, 2019
@quis quis deleted the depend-on-service-volumes branch March 8, 2019 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants