Email delivery visibility for Examiners
- Dominant language
- Python
- Stars
- 2
- Forks
- 22
- Avg merge
- 2d 35m
- Merged PRs (30d)
- 11
Description
## Problem statement
Examiners need to trust and verify outbound customer email: whether it left our systems, who it went to, and what the notification provider reports - not only a local SENT flag.
## Objectives
- Reduce support interactions and escalations where Hosts claim they did not receive the notification emails (especially renewal reminders)
- Increase email delivery success rate by proactively addressing failed emails
## User stories
### Display email delivery status
As an Examiner, I want to know if an individual STRR notification was successfully delivered so that I can more efficiently address Host support queries and escalations
**Success criteria**:
- For each notification that is logged as an event (NOC, Approval, Renewal, Cancellation, Suspended) the delivery status is also included in the event log
- The team can query the database for metrics on overall email deliverability and pull reports on failed emails
### Flag invalid email addresses
As an examiner, I want invalid email addresses to be flagged in the Examiner Dashboard so I know that some action has to be taken to prevent missed notifications.
**Success criteria**:
- When an email address has a failed delivery status as a result of invalid address, email address is visually flagged so that users know that there is an issue with the displayed email
- Once the email address is updated or has a successful email notification, the visual indicator is cleared
-
### Failed notifications report
As an examiner, I want a report of all the failed emails that were sent in a given period so that I can reach out to those contacts and have the contact details corrected.
**Success criteria**:
- The system generates a report (eg. csv file) of all the failed notifications over a given period. The record includes the date sent, type of notification, delivery status (and other relevant information that is already logged on the event / interaction) as well as the registration number.
- The report is periodically updated (every week)
-
Technical Analysis: See [Jimmy's overview of the solution and constraints](https://bcgov.sharepoint.com/:fl:/r/contentstorage/CSP_8c61494f-c53c-47da-8d05-108d38897072/Document%20Library/LoopAppData/Email%20delivery%20visibility%20for%20examiners.loop?d=wfeaeeca0559745bbbde9b44da17a1df0&csf=1&web=1&e=m5gcn0&nav=cz0lMkZjb250ZW50c3RvcmFnZSUyRkNTUF84YzYxNDk0Zi1jNTNjLTQ3ZGEtOGQwNS0xMDhkMzg4OTcwNzImZD1iJTIxVDBsaGpEekYya2VOQlJDTk9JbHdjZ2IxQWhhMlZKSk9xbWk3Y0w5alc5enJDQlFNSWxMb1JvR3hDU0UwelM5YiZmPTAxV1lEMlpBRkE1U1hQNUYyVlhOQzMzMk5VSldRWFVIUFEmYz0lMkYmYT1Mb29wQXBwJnA9JTQwZmx1aWR4JTJGbG9vcC1wYWdlLWNvbnRhaW5lcg%3D%3D)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.