cds-snc / notification-planning-core

Project planning for GC Notify Core Team

0 stars 0 forks source link

Review and adjust long code routing logic #289

Open jimleroyer opened 4 months ago

jimleroyer commented 4 months ago

Description

As a Notify user, I need to be able to do send my SMS using the appropriate numbers.

WHY are we building?

We want to be able to restrict short code usage.
We want to keep the current logic of "end user gets messages from the same long code"

WHAT are we building?

A system to associate templates to pinpoint pools

VALUE created by our solution

control over when we use our short code
save $$$

Out of scope

ui control for changing what pool is used by the template

Acceptance Criteria

[ ] we can restrict short code usage to specific templates
[ ] long codes stickiness is preserved with previously used long code, i.e. the same long code will be used for the same recipient.

QA Steps

[ ] set one or more GCNotify templates to use the short code
[ ] send an SMS with one of these templates and verify it used the short code
[ ] send an SMS with another template and verify it does not use the template
[ ] use the sms costing data to verify that we used the short code for precisely the GCNotify templates

sastels commented 2 months ago

This card might be done by https://app.zenhub.com/workspaces/notify-planning-core-6411dfb7c95fb80014e0cab0/issues/gh/cds-snc/notification-planning-core/286 We'll see what work is left after finishing that card.