- Newest
- Most votes
- Most comments
Hello,
I apologize for the trouble, Sabyasachi. Our Accounts team is best tooled to assist with these matters. I recommend creating a case with them to take a closer look into this. Here's where you can create your case:
In the meantime, I suggest reading through these resources for a possible solution:
https://aws.amazon.com/premiumsupport/knowledge-center/sns-sms-spending-limit-increase/
&
https://docs.aws.amazon.com/sns/latest/dg/channels-sms-originating-identities-sender-ids.html
If these aren't quite what you're looking for, you're welcome to look into these additional help options for further assistance:
Sincerely,
— Thomas E.
Hi Sabyasachi,
Sorry to hear about the trouble you've communicated in your follow up comment. This isn't the experience we aim for. I can understand your urgency for getting this matter resolved, which is why I've taken steps internally to relay the priority and feedback you've shared with us.
After locating your support case, I can confirm it's queued with the best suited team and your request is actively being reviewed. Please note, a recent update on your request was communicated on the case yesterday. For any additional questions or concerns, our internal team handling your case has the visibility to directly assist. To reach secure guidance, please continue to follow up your case correspondence: https://go.aws/support-center.
Thank you for your patience as our internal team continues to investigate.
Kind regards,
- John M.
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
I reached out to accounts for escalation. To summarise I was told to follow up on the same thread.
Here is their response, "I'm suggesting you take the path to direct access to escalate this. If you disagree with me and insist that I attempt to escalate this from a position of limited influence and zero scope, I will do it, because you are my customer right now, but that's not the best move."
At the moment AWS Support closes the ticket every day with the same message as the original post and I re-open it asking for a reason and requesting to update SenderID and Template.
Didn't expect this from AWS!