Change the SMS daily limits from fragments back to text messages

[adriannelee]

Description

As a Sender, I need to be able to track my daily limits without learning a new concept so that it's easy for me to stay under my limit.

WHY are we building? Because ‘daily limits’ is something we need to educate and create awareness around, educating Senders on ‘Fragments’ could make the design more challenging to execute well.

WHAT are we building?

• Looking through the design (authenticated pages, unauthenticated pages, API documentation, API error messages) to identify where we said 'fragments' and where a change is needed
• Determine what those changes are - tech and design
• Design those changes
• Hand-off to devs

VALUE created by our solution

• Reduce the amount of learning Senders have to do

Documentation and Artifacts

Good docs, figma mockups, ADRs, screenshots etc.

• Figma file
• The work we did to include 'fragments' - especially the table in this doc
• SMS limits V2 planning notes following research findings

Acceptance Criteria

On authenticated pages, unauthenticated pages, API documentation, and API error messages, Senders won't see the word 'fragments'. Their daily SMS limit will be counted using 'text messages'

• [x] Content referencing "fragments" is updated for Authenticated pages, unauthenticated pages, API documentation, and API error messages in English
• [x] Updates to English content are translated for Authenticated pages, unauthenticated pages, API documentation, and API error messages in French
• [ ] Dev implementation
• [ ] Inform Support of these changes (Ramya and Jimmy P)
• [ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
• [ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)

QA Steps

Ensure messages are updated in the following scenarios:

• [ ] Live service
  • [ ] Email
    • [ ] One off
    • [ ] Bulk
  • [ ] SMS
    • [ ] One off
    • [ ] Bulk
• [ ] Trial service
  • [ ] Email
    • [ ] One off
    • [ ] Bulk
  • [ ] SMS
    • [ ] One off
    • [ ] Bulk

GC Articles Publish checklist

• [ ] Supporting feature is released and unflagged
• [ ] Create or update slug
• [ ] Page content and slug is translated
• [ ] Document links to and from the page
• [ ] Add page slug and title to inventory
• [ ] If new page, add WAF rule
• [ ] Create new page or update existing page content
• [ ] Create or update translation to the page
• [ ] Link translations by choosing an assigned translation
• [ ] If new page, save as draft
• [ ] If existing page, update the page
• [ ] Post page in Slack for last minute reviews
• [ ] On staging: Clear the cache through GC Notify's admin panel
• [ ] On staging: Check links, images and language toggle
• [ ] Give a heads up to the app-team channel once ready to publish
• [ ] On staging and production: Clear the cache through GC Notify's admin panel
• [ ] Clear Cloudfront cache in GCA as needed (Andrew and Phil are GCA admins)

[yaelberger-commits]

Some data: Data question I’m hoping a dev can help me answer through a query: What is the average character length of SMS messages sent through Notify? How many SMS messages are 600 characters or more?

• 947 sms templates
• AVG 175 chars
• MAX 612 chars
• MIN 3 chars

*doesn't factor in that some templates contain variables and might make the final SMS message longer

[adriannelee]

Started working on this today with Yedida and Phil, creating an inventory of the screens that would need to change when "fragments" is removed

[adriannelee]

Hey team! Please add your planning poker estimate with Zenhub @adriannelee @amazingphilippe @YedidaZalik

[adriannelee]

Yedida worked on the content for removing "Fragments" today and I did (a very quick) review. I think it's good for handoff? (other than translation)

[yaelberger-commits]

2 things next 1) Prototype is screenshots and we don't have the FR so will ask if we need to add more screenshots or get translations another way 2) Now using placeholder # for number of text messages (fragments to text messages) devs need to give us the number and number of characters 1,000 text messages is the new daily limit 612 is the new character limit (to confirm)

[YedidaZalik]

Discussed with Marie-Sophie and agreed I'd tag her in Figma where we need French. That's done now so it's ready for her translation.

[smcmurtry]

Translations done, could look at this for dev-design review today.

[YedidaZalik]

Discussed at dev-design review and implemented decisions from the review. Made the relevant changes to TOU EN and FR in GC Articles as Yael said that could go ahead before dev implementation. Worked with Phil to tidy up figma for dev implementation. We need to let Ramya and Jimmy P know that this is changing.

[yaelberger-commits]

@jzbahrai can you please update the checklist above so we can see that all AC is met?

[amazingphilippe]

Merged recent work about Daily limits and Email limits. in Figma

Even this isn't enough. Andrew mapped out all the states and conditions. We missed trial and live

Ok test cases so far:

• Live service
  • Email
  • One off
  • Bulk
  • SMS
  • One off
  • Bulk
• Trial service
  • Email
  • One off
  • Bulk
  • SMS
  • One off
  • Bulk

Made a new pattern template to avoid this when working on the sending flows in the future: Private Zenhub Image

Can be found in Notify's Figma component library