Proactively inform users when their usage nears the annual limit

[yaelberger-commits]

Description

As a user, I need to be told in advance that I'm close to my annual limit so that I can plan accordingly for when to send more notifications or how to budget my remaining volume.

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?

• Email notifications and a quarterly report
• Proactive: quarterly report
  • Organized by service
  • One report per user
• Reactive: warning emails
  • Contains daily and annual limit to avoid confusion
  • Not as flexible to increase limit

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

Figma

Acceptance Criteria

• [ ] Send users a warning email when service is near their annual limits (80%, 90%)

• [ ] If next batch of messages pushes them past the annual limit, show warning in the UI to inform them. Only allow users to send if they reduce the number of messages to be below the annual limit.

• [ ] Send a quarterly report by email to each user, notifying them of the current usage of each service

• [ ] 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

Related Research Airtable records

• (find stuff yourself)

QA Steps

• [ ] Tested in a realistic production scenario

[yaelberger-commits]

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

[YedidaZalik]

Starting adapting content in templates about daily limits to create templates about annual limits in google doc

[YedidaZalik]

Yesterday revised annual limit templates to incorporate aspects of Phil's version. Phil reviewed and i implemented his comments. Then I updated templates so can also be used for daily limits. Reviewed again this morning and made a few more changes. Need to check if we need combined text/email templates and if year can update programmatically in the template. Then ask Phil to review again.

[YedidaZalik]

Yedida will share template ID of the Combined text/email templates There might need to be code changes Could also show at dev-design Hopefully can make the year a variable to populate automatically in the code

[YedidaZalik]

Finalized templates with Phil Current template IDs and other annotations entered as comments in the google doc

[YedidaZalik]

Ready for localization https://docs.google.com/document/d/1UYxOoEmLRMVDXdxuisy8dh-_42MEnrSPNPZ7qCO2HkE/edit?tab=t.0#heading=h.yh39z1fo9gom

[YedidaZalik]

YZ to send to MSB as an email - done

[YedidaZalik]

Phil, Marie-Sophie & Yedida met yesterday to discuss visual issues in French interface

French is ready: https://www.figma.com/design/JGp5noL1kCpiwJzHKL5MHe/Sending-capacity---capacit%C3%A9-d'envoi-(Copy)?node-id=3399-2570&node-type=canvas&t=vDMfYBhIRrQfBq5t-0