Daily Limits (Overarching versions & releases)

[yaelberger-commits]

High level problem statement and goals:

Problem Statement: As a Notify Sender, I need to know how many messages I can send in a day, how many I have already sent, and how many I have left to send so that I can track, monitor and report my daily volume to stay within my limits and know if I need to request an increase to my daily limit in advance.

Hypothesis: If we show Senders their daily habits in their service dashboard and provide light education/guidance, then they will have an easier time planning their sends and be less frustrated with the process for sending messages, resulting in fewer support tickets about limits.

If we change the SMS daily limits from fragments back to text messages, then SMS senders will have more confidence sending SMS and understanding their daily limits.

Outcomes:

• Senders are able to track daily messages sent and remaining in their service dashboard.
• Senders are able to track how many messages they have remaining from their warning email when they reach 80%.
• Senders are able to plan for sending in advance and request a higher limit if needed by reading some light guidance and content on the website.

Possible iterations https://miro.com/app/board/uXjVPpnntV0=/

OLD

Acceptance Criteria

• [x] Accurately counting the number of messages each service is sending (fragmented SMS included)
• [x] Accurately reporting the number of messages each service is sending to GC Notify
• [x] Users know their limits for sending messages per service
• [x] We are enforcing the daily limits

Prerequisite for billing For V2

• [x] Users can see how many messages they have sent and understand where their account stands against the limits
• [ ] Users know how and when to request a limit increase, and when we might refuse
• [ ] Users are notified of the new limits in some way (email to all clients or release log, what's new etc.)
• [ ] Notify admin are monitoring when services reach their warnings and limits
• [ ] users know how sending SMS to international numbers will impact their daily and annual limits

Notes following research shareback https://docs.google.com/document/d/1lrDvKwHRwtm4gVgF0E-xKoY3J1UWQ-FeUybYEX3AbfU/edit#

Airtable records to update when completed:

• Finding

[yaelberger-commits]

Think about services that would warrant exceptions to the daily, and annual limits and what the criteria is for making an exception

[YedidaZalik]

Sprint planning document to be used at Stand-up and EOD summaries in hackathon channel

To determine at Sprint Planning:

- What pieces are completed

Dev work

Design work Still in progress, see below

- What pieces are left to do

Design work examples (check at Sprint planning if anything to add): (1) Dashboard - distinguish btwn day and week more clearly #865 (2) Review page - contact hierarchy-eg. where should "contact us" go #866 (3) Character limit 160 v 153 what to do!!! #867

Dev work

- What is in scope :

Acceptance criteria on Epic

- What is out of scope

Release, testing, further iterations Design annotation (?) Guidance content Journey mapping

Delivery managers

@Steve McMurtry for dev work @Phil C. for design work

Definition of Done

Ready to test with real SMS users and get feedback before full release

[adriannelee]

@yaelberger-commits will refine this card for V2 and put it back into the Epics column.

[YedidaZalik]

Can we address "tomorrow" in sms daily limits but putting it in the UI?