Is there any support or roadmap for RCS? What is the general interest of other customers here?
Hello luketidd,
We have previously assessed RCS, and as of today, there are no current plans for its implementation. Please feel free to contact us for any other concerns. For technical issues, please reach out to our support team at support@voip.ms or through live chat.
I have an interest in RCS. Why not?
x2. how do we vote this up?
Now that apple is adopting RCS, the majority of text messages will be through that protocol. Please support.
I think RCS and short code support would be excellent.
With apple adopting RCS, and Android obviously supporting it already it will be common and widespread. Not having RCS is going to start causing me a lot of friction.
Could you reconsider supporting it.
Hi all, we did survey some of our biggest messaging customers about RCS in the past, but havenāt had much response. We will definitely monitor this trend and adjust accordingly!
Already the lack of MMS support (particularly multi-recipient) has me looking to leave Voip.ms, probably going over to Google Voice, but RCS would be a way to keep me as a customer. I guess Iām not a ābiggest messaging customerā though, just one person, so perhaps Iām just not the kind of customer Voip.ms is oriented towards.
Itās been almost a year. But perhaps waiting was the right thing to do? A new standard for RCS was published yesterday (March 13, 2025) that also includes E2EE. (canāt include links. please search for āGSMA RCS Universal Profile 3.0 specificationsā for all the technical details)
With the large scale support of RCS, can Voip.ms join the love fest? Pretty please?
I am also looking for RCS support.
+1 for RCS support, especially for E2EE (I donāt care about multimedia, but its necessary to include, as encrypted blobs are unparsable). From what I understand, however, this is not trivial to implement, either delivering the data, or managing keys. There are good reasons Apple has not opened up its walled iMessage garden; ts very hard to guarantee such a multilayered system unless you own every layer. Thereās probably a good business opportunity out there for parties willing to undertake the complications. Hereās some research I did, prompting Perplexity.ai.
RCS is the future, unencrypted communications and green bubbles are for ![]()
Other telephony as a service companies already support it or are at least in beta with it.
Now that UP 3.0 and E2EE are official, it feels like the right time to bring it up again. But honestly, when basic support stuff goes unanswered, itās hard to tell if something this big is even possible. Most of my tickets end with āweāre waiting on a third party,ā so it seems like they might not even have control over the parts needed for RCS in the first place.