Assign 10DLC number to VA Profile Pilot (Staging + PROD)

[kbelikova-oddball]

User Story - Business Need

VA Profile is initiating a pilot to notify Veterans via SMS when their registered emails on VA.gov are undeliverable. To support this, we need to allocate a 10DLC number specifically for SMS notifications. We have six existing numbers in AWS, originally provisioned for VEText but currently unused, which can be repurposed for the VA Profile pilot.
This ticket covers assignment of a single number to both VA Profile’s environments - staging and Prod.

• Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As a VA Profile team member
I want to notify Veterans via SMS when their email is undeliverable
So that they can update their email address in their profile and continue receiving important communications from the VA.

As a VA Notify engineer
I want assign +12023358766 to VA Profile's service
So that VA Profile can send sms notifications from this dedicated number

Additional Info and Resources

Ksenia will do the following in AWS Console:

• An opt-out list should be created for this notification type, applicable to both staging and production environments.

Acceptance Criteria

• Opt-out list is added to this number
• Update the SMS sender for +12023358766 number for VA Profile service on staging and PROD
• Use POST {{notification-api-url}}/service/{{service-id}}/sms-sender/{{sms-sender-id}} route to update the default sms sender (do not create a new one)
• staging payload

{
    "sms_sender": "+12023358766",
    "provider_id": "17c4e05b-25ec-4bac-a8f7-27075b27e23a",
    "description": "<check with @kbelikova-oddball  for what the description should be>"
}

• verify with GET {{notification-api-url}}/service/{{service-id}}/sms-sender route that the sender was correctly updated

• prod payload - this will need to be created, using POST {{notification-api-url}}/service/{{service-id}}/sms-sender

{
    "sms_sender": "+12023358766",
    "provider_id": "253d81ee-2004-43ae-9ed9-b2e80858eb66",
    "description": "<check with @kbelikova-oddball  for what the description should be>",
    "is_default": true
}

• verify with GET {{notification-api-url}}/service/{{service-id}}/sms-sender route that the sender was correctly updated

• Since there is no PR for this ticket, validate work with Kyle/Ksenia

• Share a new sms_sender_id with to use on staging and PROD

• This work is added to the sprint review slide deck (key win bullet point and demo slide)

QA Considerations

Potential Dependencies