I have purchased a dedicated AWS pinpoint long code for India (ie. An Indian phone number) for $120/mo. I'm not using any keywords. I've enabled two way sms on it. I'm able to receive messages on it and send messages, however when I send a message, the sender id shows up as NOTICE to the user.
Thus a conversation is not possible because while to user has to send a message to the dedicated long code, they receive a reply from a different number.
eg. When I send this message:
{
"ApplicationId":"6b07b70b18714cf6ba60fb5446123456",
"MessageRequest":{
"Addresses":{
"+914321321321":{
"ChannelType":"SMS"
}
},
"MessageConfiguration":{
"SMSMessage":{
"Body":"Your message was received, we will contact you shortly. ",
"MessageType":"TRANSACTIONAL",
"OriginationNumber":"+911234123123"
}
}
}
}
The person receiving it sees it from sender "NOTICE". Even if I explicitly specify the senderId to be the same as the origination number. ie. I add ,"SenderId":"+911234123123" to the above, the behavior is the same.
Am I missing something, or is the AWS Pinpoint dedicated long code two way sms functionality broken in India?
This use case should be supported according to the AWS docs here: https://docs.aws.amazon.com/pinpoint/latest/userguide/channels-sms-originating-identities.html