Help users plan by showing how many messages they have left to send

yaelberger-commits commented 2 months ago

Description

As a user, I need to be able to see how many messages I have left to send in a fiscal year so that I can use my sending volume effectively.

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? Updates to the ready to send page 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

Documentation and Artifacts

Product requirement document Figma Budget component

Acceptance Criteria

[ ] Ready to send page: help users plan how many messages they can send by showing them a positive balance
[ ] 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