GC Notify sends a notification when a send is complete

[adriannelee]

Description

As a Sender, I need to be notified when a send is complete so that I can check the failure report and take next steps without waiting around for the send to finish.

WHY are we building?

During the bounce rate research, we made an observation that clients will wait around after they do a send or log into the site at a set time after doing a send to go over the failure report. While this is not a 'problem', we could help remove friction while providing information that is oriented to them reducing their bounce rate (actions they can take for each email address).

Participants during this research also noted that they don't realize something is an issue until Notify lets them know.

Furthermore, this could potentially help keep a record of problem email addresses that are older than the data retention period for Notify.

It may also make it easier for clients to forward these notifications to their colleagues who manage the distribution list.

WHAT are we building?

• An email notification that gets sent after a send is 'complete'

The notification outlines:

• the percentage of failures overall
• email addresses that should be reviewed for removal or correction

We'd need to think more on / research:

• What counts as 'complete'?
• What about single-sends? E.g. using the API? Is this only for bulk sends?

VALUE created by our solution

• Friction removed for clients who wait around or have to remember to log in to check
• Lowered bounce rate by serving bounce rate information in a way clients need

Documentation and Artifacts

Good docs, figma mockups, ADRs, screenshots etc.

Acceptance Criteria

Given some context, when (X) action occurs, then (Y) outcome is achieved

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

• A11y

• Bilingualism

• Privacy considerations

• Security controls in place

• Measuring success and metrics

Related Research Airtable records

• The feature is not discoverable because of clients' reliance on alerts for issues and because "problems" are synonymous to "failures"
• There is motivation we can direct toward reducing the bounce rate
• Distribution lists are managed externally
• Wanting more out of the API: ... Download usage report using API

QA Steps

• [ ] Tested in a realistic production scenario

[yaelberger-commits]

Interesting idea! I think this could make a good small bet to try out. Maybe to be released as a beta feature to a few services to start