Content: Callback warning & suspension emails

[whabanks]

Description

As a service owner, I need to know when the reliability of my callback API is degrading, or my callbacks have been suspended, so that I can take appropriate action to resolve the issue.

As a service owner, I need expectations around callback functionality to be clear, so that I am aware of when warning emails and suspensions are issued.

Acceptance Criteria

• [x] Content for the initial warning email send to a service owner when their callbacks are failing
• [x] Re-review / update content for the critical email that informs the service owner their callbacks were suspended.
• [ ] Create templates in GC Notify service for warning email and suspended email
• [ ] DEV: Update the API documentation with expectations around: callback timeouts, warning emails, suspensions, and how to have a suspension lifted. (response time less than 1 second, we will retry callbacks 5 times if they fail continuously we will warn, then 50 failures in 10 minutes and will suspend your callback service)
• [ ] Document for ICs where these templates are and criteria for when we send them (which alarms trigger us manually sending which template)

[yaelberger-commits]

Please add your planning poker estimate with Zenhub @amazingphilippe

[yaelberger-commits]

Working on draft EN content at the bottom of this document https://docs.google.com/document/d/1yUgerRyr6bcLu0TyoI__XO2L-m28YHcfp8za5ueTlvw/edit

[yaelberger-commits]

Go through this today for story refinement to handoff to Devs

[yaelberger-commits]

Finished drafting both warning and suspension emails at Story Refinement. Handed off to @mariesophiebezert to help with FR versions

[YedidaZalik]

Reviewed and revised emails using the suggest function

[yaelberger-commits]

Accepted all of Yedida's changes

[yaelberger-commits]

Ready for translation when MS is ready

[yaelberger-commits]

Emails are back from translation. Yael will create them in our GC Notify service