jimleroyer commented 2 weeks ago

Description

As a recipient of an international SMS sent via GCNotify, I want to have an identification of the sender, So that I know who sent the SMS.

As a British telecom provider, I want SMS senders to use IDs, So that I can identify these and get these to pass our internal filters.

As a product owner of GCNotify, I want our SMS to use a custom sender ID, When sent internationally, So that these are not blocked by destination countries that require these.

WHY are we building?

To improve the international sending of SMS.

WHAT are we building?

Define a custom sender ID for Pinpoint that we can use at the international level. Probably not to be used nationally as this is not used anyway.

VALUE created by our solution

More reliance for international sending of SMS.

Acceptance Criteria

[ ] The custom sender ID works for specific destination country using Pinpoint. A working sender ID entails that SMS sent to that destination country are successfully sent.
Measuring success and metrics

Sending metrics at the international level is improved for key destinations that we know require the usage of sender ID.

QA Steps

Pinpoint:

[x] Send a domestic sms using a template in the shortcode list. It should be sent from the Pinpoint shortcode pool (and the shortcode!).
[x] Send a domestic sms using a template not in the list. It should be sent from the Pinpoint default pool.
[x] Send an sms to an international number outside Zone 1. It should be sent by Pinpoint from our default sender "CANADA-CA"

SNS:

[x] Send a domestic sms using a service with a dedicated number. If should be sent through SNS / us-west-2 (and from the dedicated number)
- [x] Send an sms to a US number. It should be sent through SNS / us-west-2 (and fail on staging until we get our toll free number sorted)
- [x] Send an SMS to a fake Guam number (1 671 555 0123). Should be sent with SNS / ca-central-1 (but fail since it's a fake number)