When user reaches the annual limit, prevent message deployment

yaelberger-commits commented 2 months ago

Description

As the GC Notify product team, we need to be able to prevent message deployment when a service reaches its annual limits so that we can scale our services more widely across the GC for greater impact.

WHY are we building? Clients cannot see their annual limits or their current usage status. To calculate their usage, clients have to manually sum up month over month statistics. We also don’t enforce the annual limits, so clients have no incentive to honour them. WHAT are we building? Error message, freeze ready to send page and an email notification VALUE created by our solution

Users feel confident about budgeting their message usage. Metrics: Sentiment score, number of users who max out their usage before fiscal, how early users max out their usage
Users feel that they are given appropriate degree of warning before reaching their annual limit. Metrics: Sentiment score, number of users who max out their usage before fiscal, how early users max out their usage
Users are not able to send messages after reaching their annual limit. Metrics: Backend data
Existing users are aware of the increase in annual limit Metrics: Number of notification emails opened

Documentation and Artifacts

Product requirements document Figma

Acceptance Criteria

[ ] Show an error message for when people reach the review page, but are over their limits
[ ] Freeze “ready to send” page function
[ ] Send email informing user they are at 100% usage
[ ] Cypress UI tests if needed.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] 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)
[ ] Does the feature change our Information Architecture? If so, update the Sitemap in En/Fr
A11y
Bilingualism
Privacy considerations
Security controls in place
Measuring success and metrics