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

Explain how text message ‘fragments’ affect pricing and the free allowance #4902

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

karlchillmaid
Copy link
Contributor

@karlchillmaid karlchillmaid commented Nov 15, 2023

Users need to understand the difference between the number of text messages they send and the number of actual text message ‘fragments’ they use.

In the past we’ve always avoided using the term ‘fragments’ as its meaning may not be clear.

This pull request makes a few small changes to the Text message pricing page to introduce and explain fragments.

Updating our pricing information probably won’t solve the problem though. We also need to think about updating the UI content on the:

  • Usage page
  • Edit template page
  • Template preview page

We might also want to think about whether our offline touchpoints (invoices, emails etc) are consistent with what we say on the Notify website.

Once we’ve discussed and agreed how we want to change content across Notify (and beyond), we can collate all those changes in this PR.

Copy link
Contributor

@CrystalPea CrystalPea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, current changes look good.

Did we get anywhere with additional changes mentioned in pull request's description?

@karlchillmaid
Copy link
Contributor Author

@CrystalPea There’s a story in the backlog to work on this stuff – I’ve been speaking to Product and I hope we can pick it up soon.

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