Resolving Sender ID Display Issues with Amazon Pinpoint SMS in Bangladesh

0

I am experiencing challenges with the sender ID display while using Amazon Pinpoint to send transactional SMS messages in Bangladesh. Our designated Sender ID, "Neurochip," is not being displayed correctly; instead, recipients see "AuthMSG" or "InfoSMS." We've tried both SDKs and the Management Console without success. I'm seeking advice on how to ensure "Neurochip" appears correctly for our SMS messages. This issue persists despite no requirement for Sender ID pre-registration in Bangladesh as per previous support consultations. Guidance on resolving this and correctly implementing our Sender ID in Pinpoint would be greatly appreciated.

1 個回答
0

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

AWS
支援工程師
Palak
已回答 4 個月前
profile picture
專家
已審閱 1 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南