As a GC Notify team member or partner, I need to be able to see data on template category usage so that I can optimize and promote GC Notify for those specific use cases.
WHY are we building?
We will have new data coming in about template category and usage from our work to implement our short code
WHAT are we building?
Pumping that new data to the CRM
VALUE created by our solution
We'll be able to analyze that data and see it within the context of other client data and usage we already have.
Documentation and Artifacts
Good docs, figma mockups, ADRs, screenshots etc.
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved
[ ] 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
Description
As a GC Notify team member or partner, I need to be able to see data on template category usage so that I can optimize and promote GC Notify for those specific use cases.
WHY are we building? We will have new data coming in about template category and usage from our work to implement our short code WHAT are we building? Pumping that new data to the CRM VALUE created by our solution We'll be able to analyze that data and see it within the context of other client data and usage we already have.
Documentation and Artifacts
Good docs, figma mockups, ADRs, screenshots etc.
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved
[ ] 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
QA Steps