Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clients get notified when their service gets suspended #869

Open
4 tasks
amazingphilippe opened this issue Sep 15, 2022 · 7 comments
Open
4 tasks

Clients get notified when their service gets suspended #869

amazingphilippe opened this issue Sep 15, 2022 · 7 comments
Assignees
Labels
Content l Contenu Tasks to write, edit or delete content from any Notify pages UX Design and prototyping

Comments

@amazingphilippe
Copy link
Collaborator

amazingphilippe commented Sep 15, 2022

Give your user story a simple, clear title

Description

This links to these AC statements from the Bounce rate epic:

  • Given my bounce rate is too high, when my service is suspended, then I get notified by email
  • When I get notified by email, I can contact Notify support to get help

As a Notify client, I need to know when my service is/will be suspended so that I can take steps to recover it/prevent it.

WHY are we building?

  • The communication for suspending services is manual, because the suspension process is manual. With the emergency break, suspension will be automatic, therefore we need automatic suspension communications, including leading warnings before suspension happens.
    WHAT are we building?
  • Communication around account suspensions linked to when the automatic break (Write ADR on bounce rate emergency brake #845) is triggered.
  • Communication around warning and critical thresholds. (Before being suspended)
  • Possible next steps to recover or prevent in those emails
    VALUE created by our solution
  • Our clients are never suspended and locked out of their services without knowing why.

Acceptance Criteria** (Definition of done)

To be refined through discussion with the team

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

If this user story emerged from User Research insights:

  • Link research insight back to hypothesis from Epic or Objective in Airtable
  • Once change/fix/feature is implemented, mark insight as "resolved" in Airtable
  • Once change/fix/feature is implements, link insight to design artifacts (Figma) in Airtable
  • A11y
  • Bilingualism
  • Privacy considerations
  • Security controls in place
  • Measuring success and metrics

QA Steps

  • Tested in a realistic production scenario

Relevant Research

Research question: How do Senders react to the concept of being suspended due to their bounce rate?

@amazingphilippe amazingphilippe added UX Design and prototyping Content l Contenu Tasks to write, edit or delete content from any Notify pages labels Sep 15, 2022
@yaelberger-commits
Copy link
Collaborator

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

@jimleroyer
Copy link
Member

@whabanks Potential task during the holidays, just to implement the email sending plumbing when a service gets suspended.

@whabanks whabanks self-assigned this Dec 28, 2022
@whabanks
Copy link

Should we notify our users when a service is resumed as well?

@YedidaZalik
Copy link

+1 to notifying users when service resumes!

@YedidaZalik
Copy link

When we suspend or have suspended their service due to email bounce rate, can the service still send SMS? Should we specify that we've just suspended email for the service? Can we suspend for one but not the other?

@YedidaZalik
Copy link

Started drafting possible email content

@whabanks
Copy link

Plumbing is in place to support the remaining work to be done once the ADR is complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content l Contenu Tasks to write, edit or delete content from any Notify pages UX Design and prototyping
Projects
None yet
Development

No branches or pull requests

5 participants