Update status descriptions to help users understand the 72 hour period (.net) - Githubissues

alphagov / notifications-net-client

.NET client for the GOV.UK Notify API

https://www.nuget.org/packages/GovukNotify/

MIT License

25 stars 20 forks source link

Update status descriptions to help users understand the 72 hour period (.net) #113

Closed karlchillmaid closed 4 years ago

karlchillmaid commented 4 years ago

What problem does the pull request solve?

This PR changes the wording of 2 message status descriptions:

mentioning the 72 hour period in the Sending status makes it explicit that this a message that remains in this state for longer than a users expects is not 'stuck'
not mentioning the 72 hour period in the Phone not accepting messages right now status should reduce any confusion for users who see this status after <72 hours

This change was prompted by feedback from a user on x-gov Slack:

We sent out a message last night and there were a few numbers that did not get it, on checking one, it gives the message: "The provider could not deliver the message after trying for 72 hours. This can happen when the recipient’s phone is off..." Given it is not even 24 hours after the text was sent, any ideas why this report is worded like this?

New content

Sending Notify has sent the message to the provider. The provider will try to deliver the message to the recipient for up to 72 hours. Notify is waiting for delivery information.

Failed: temporary-failure The provider could not deliver the message. This can happen when the recipient’s inbox is full or their phone is off...

Checklist

[x] I’ve used the pull request template
[ ] I’ve written unit tests for these changes
[x] I’ve update the documentation (in DOCUMENATION.md and CHANGELOG.md)
[ ] I’ve bumped the version number (in src/Notify/Notify.csproj)