Allow users to request a high priority status, reviewed by Notify Admin

[yaelberger-commits]

Allow users to request a high priority status, reviewed by Notify Admin

Description

As a (user), I need to be able to set my templates to high priority so that I can ensure they are delivered to the recipient in a timely manner for more urgent notifications like password reset or 2FA.

WHY are we building? Currently, users have no way of selecting the priority status of their templates. We can do so as admin of Notify, but we have not made that feature available to our clients yet. Allowing them to request priority status for a template will help ensure we are meeting their expectations and the end recipient's expectations for timeliness of message delivery.

WHAT are we building? A frontend design that would reveal an option for users to be able to select the high priority lane for a template in their service.

VALUE created by our solution Notifications that need to arrive faster will get put in the priority lane and the clients and their end recipients will be more satisfied with the Notify service because they won't be waiting too long for urgent notifications.

Acceptance Criteria** (Definition of done)

To be refined through discussion with the team

• [ ] A client cannot set the priority to high themselves, they make a request and it gets actioned by the team
• [ ] Users understand what high priority means and what kind of templates are a good fit or acceptable use case for high priority

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

[yaelberger-commits]

Notes:

• Could surface first, but not yet allow users to request a change
• Acceptance Criteria for what templates would qualify for a priority change
• A user could edit a template after it's given higher priority so we might need to look at how to prevent that
• Maybe we don't surface priority lanes to them at all, but we ask more direct questions about their templates and then we match that to our own criteria

[yaelberger-commits]

Iceboxed, as it would be less risk to ask more direct questions about their templates and put templates into queues ourselves, rather than surface priority lanes