search

cds-snc / notification-planning

Project planning for GC Notify Team
4 stars 0 forks source link

Embedded guidance for users about SMS parts and message length on Review Before Sending #866

Open yaelberger-commits opened 1 year ago

yaelberger-commits commented 1 year ago

Embedded guidance for users about SMS parts and message length

Description

As a (user), I need to know how many message parts my SMS sends will be split into, so that I can understand how much of my SMS quota I am using.

WHY are we building? Help users understand how much of their SMS quota they are using before sending.

WHAT are we building? A message on the preview pages that tells the user how many message parts their SMS send will use.

VALUE created by our solution More transparency around SMS message parts and how the SMS quota is used.

Acceptance Criteria** (Definition of done)

Add to the "Review before sending" screen for SMS sends from a spreadsheet: https://www.figma.com/file/VRqRRfX7Ko5ssg2VryVVET/Dashboard-%7C-Tableau-de-bord?node-id=1470%3A7137

Add to the "Send to 1 person" review screen.

Possibly add to the "Template preview" screen?

Given some context, when (X) action occurs, then (Y) outcome is achieved

QA Steps

yaelberger-commits commented 1 year ago

We don't want to let users request more messages than they're allowed in their limit Quick sync

yaelberger-commits commented 1 year ago

Ready for another review. Does an exact calculation unless CSV is really big (1,000 rows or less, over 1,000 rows it's an approximation. Could be updated easily) Language might need to be undated pending other decisions. FR is there too from Google doc

yaelberger-commits commented 1 year ago

Going to content critique this morning Will need @amazingphilippe on FR content review to follow

adriannelee commented 1 year ago

Is this a duplicate of https://app.zenhub.com/workspaces/notify-planning-614b3ad91bc2030015ed22f5/board ... ?

yaelberger-commits commented 1 year ago

@adriannelee that link brings me back to the main zenhub board. Which issue specifically? I iceboxed this issue for now because we're going back to a "text message" limit as opposed to fragments, so we don't need to show how messages get split into parts for the v2 iteration.