SMS not working even though it says it processed

kristinacree
Mega Expert

I am currently trying to get SMS on notifications working but running into some problems. I created a notification, added some information to the SMS Alternate field. I am in the group that should be receiving the message. I updated my notification settings, added both my cells (personal - AT&T and work - Verizon). I set up that the newly created notification would go to my email, personal, work and push notifications via my system settings - notifications - that specific notification. I created a defect, the table I have the notification on, and I receive the Email and Push notification, but neither SMS came through. I updated my settings to only go through for my cell phones and tested it again. I still never received the SMS. Is there anything else I should be looking at to narrow down why this isn't working?

1 ACCEPTED SOLUTION

EmilyAWN
Tera Expert

If anyone else happens upon this, it's very likely Verizon has blocked your send address. It happens to us occasionally but only with Verizon. Everyone gets the SMS alerts except vtext.com addresses and we have to call them to have them unblock us.

View solution in original post

14 REPLIES 14

kristinacree
Mega Expert

I blacked it out, but I'm not putting in the +1, only the number so 5551234567. 

and if you look in the email log, there is something in the Body field? Recipient should contain you number@vtext.com. Also, try click Resend and see if anything changes.

Interesting post about AT&T issues. Might be part of your problem as Verizon should work fine. Verizon texting was working fine for me all weekend.https://community.servicenow.com/community?id=community_question&sys_id=0eb15577db8367007d3e02d5ca96...

EmilyAWN
Tera Expert

If anyone else happens upon this, it's very likely Verizon has blocked your send address. It happens to us occasionally but only with Verizon. Everyone gets the SMS alerts except vtext.com addresses and we have to call them to have them unblock us.

I was bad about not updating this, and only if I remember correctly, it was a Verizon issue. Our company changed providers to ATT so it isn't that problem anymore for us.