@Saili Gosula There is an SMS issue that can be monitored on our Status Site. I don't believe your TCR status is an issue - I will take a look at your TCR status and make sure all is set there.
Having exactly the same issue since 3/6/2023. RingCentral support and our account rep have been utterly useless, just keep regurgitating the same "TCR registration" nonsense.
We've had our RingCentral service since 2009, didn't have any issues exchanging SMS with these customers up until now.
Why is this issue happening now with Verizon, and what's RingCentral's ETA for getting it fixed?
@Becky-Community_Manager , your tech support does not know this and they are frustrating us and wasting our time insisting that TCR is the issue and we have to wait 20 days to get this resolved. They need to know how to respond to our inquiries. Also I haven't seen a single update on that page about this issue since the original updates yesterday morning (even thought the timestamps say it was later in the day, it was not. All of the notes that are there on this issue were there earlier than their timestamp, all in the morning). I've been checking and there are no updates at all. What is the status since the Status page has nothing new for us for about 24 hours?
@Becky-Community_Manager We need an update on this issue. Ring Central is causing issues for all of our businesses. This seems as though it should be an urgent matter that should have been fixed within the last THREE days. There are no updates on the Status Site.
@Becky-Community_Manager You keep saying check the Status Site but it hasn't been updated since yesterday, even though it says an update will be provided in the morning. If this is truly related to the awful rules that have been put in place that we supposedly have until the 31st of March to deal with, please let us know so we can all make the changes needed immediately (like texting from non-Ring Central phone numbers). Don't forget this is literally our livelihood and how we feed our families, not some hobby. Please treat it as such.
Looks like this issue has now been resolved.