Resolving Sender ID Display Issues with Amazon Pinpoint SMS in Bangladesh

Hello,

When issues such as this (SenderId different to the one specified) happen after Pinpoint hands over the message to the downstream provider, we would need to reach out to the downstream providers with the delivery status logs[1] to get more details on it. The delivery status logs contain valuable and necessary information required, such as the timestamp, record_status and most importantly the message_id, which can be used by the downstream providers to track the messages. The caveat here is that they would require the latest message IDs to track the messages, which should be at most 48-72 hours old.

Therefore, to troubleshoot the delivery issues in this case, kindly open a case with AWS Support as this information is non public and provide 3-4 delivery status logs [1] of messages (in .txt format), where the SenderId displayed on the recipient device was different (“AuthMSG” or “InfoSMS”) to the specified SenderId ("Neurochip"). With these logs/MessageIds, we can reach out to our aggregators and open an investigation with them.

[1] Event stream settings - https://docs.aws.amazon.com/pinpoint/latest/userguide/settings-event-streams.html