When OTT providers first started offering calls and messaging for a fraction of the cost of mobile network operators, many telcos feared that one-day they might simply become dumb data pipes.
For many MNOs today that scenario has become a reality.
In countries like Brazil and China, OTT applications are now the primary channels for P2P (person-to-person) communication. WhatsApp penetration continues to grow at a significant rate, for example in Saudi Arabia (73%), Malaysia (68%) and Indonesia (40%).
For some telcos this is good news. The surge in the use of WhatsApp, Facebook Messenger and WeChat means there’s more money to be made from servicing our insatiable appetites for data. However, selling bits and bytes is ultimately a low margin, low growth business, and being a data pipe doesn’t really put a telco in a strong position.
Telcos could really be at the center of the mobile ecosystem, the masters of all they survey. This means generating revenue off data from increased OTT use, from consumer messaging, and from A2P (application-to-person) messaging and its myriad of potential use cases. However, in reality telcos are losing the grip they once had in the marketplace. Many are simply sleep-walking into a dumb-pipe future and need to wake-up if they want to take a meaningful part of the market.
Voice revenues are near extinction. P2P SMS traffic is heading off a cliff’s edge, and the long-term future of the basic text message format looks uncertain at best. Right now, A2P SMS revenues are buoyant and even set to increase significantly, but enterprises will one day start to question the efficacy of SMS compared to feature-rich OTT messaging services.
Therefore, I believe the only thing standing in the way of telcos becoming dumb pipes is RCS (Rich Communication Services), otherwise known as the next generation of SMS. Telcos must choose to either support RCS and make it work, or accept their fate.
Spearheaded by Google, RCS has the potential to completely replace SMS and help MNOs to possibly regain lost ground in P2P messaging, but even more importantly for their bottom lines, continue to be part of the A2P messaging eco-system. The question is – are they ready to take this opportunity?
To control the mobile ecosystem you must have traffic. But with Facebook Messenger for Business gaining traction with brands and enterprises, and WhatsApp recently entering the A2P market, the battle for control of the mobile inbox has never been more fiercely contested.
With A2P SMS only growing in popularity among businesses, the mobile inbox is still an important destination for everything from appointment reminders, to delivery notifications and fraud alerts, but that status is under threat. If OTT messaging services were to gain significant share of the A2P messaging market, the world consumers know today where most A2P messages end up in the same mobile inbox would be a thing of the past.
In many ways RCS represents a chance for telcos to control the mobile inbox and ensure A2P messaging continues to mainly be sent via an open eco-system as opposed to the OTTs proprietary approach, and there are encouraging signs that suggest RCS will deliver. According to Juniper Research, 90% of all RCS traffic is expected to be driven by brands and businesses by 2022, netting operators an estimated $9 billion. However, the key to telcos unlocking that revenue lies in the appeal of RCS to both businesses and consumers – which is why the pricing model will be critical.
Right now nobody in the mobile industry has a clear idea of how the pricing for RCS is going to look. As a basis, it looks likely that there will be a per transaction model supplemented with a per session model to support more interactive use cases. These costs will be charged by the telcos and carried by the business wanting to communicate with consumers.
With OTT services like WhatsApp, MNOs typically make money on the data from when the message is sent, and when that message is received.
However, it doesn’t seem fair that consumers should have to pay if a brand decides to send you a rich media message like a video advert. Ideally, the businesses should also pay for the recipient’s data so that the recipient only pays when they respond.
If operators follow the WhatsApp pricing model for rich-media for RCS, it could lead to problems. Because RCS has the capacity to deliver a whole payload of information in one message (think SMS plus images, audio, videos and more), consumers could resent having to cover the data costs just to hear from their bank or retailer.
For now, RCS only works on Android, whereas services like WhatsApp already work seamlessly across iOS and Android devices. Until Apple gets onboard with RCS, which is not guaranteed, installations of Android Messages hit a level where RCS offers brands and businesses enough consumer reach, and telco interoperability is in place so that businesses can run the same RCS service across multiple telcos, telcos will have to get creative with pricing.
We know that brands and businesses are more than ready for an SMS upgrade, while consumers already prefer richer, more interactive forms of personalized messaging.
The long-term future of MNOs in the A2P messaging market depends on ensuring that RCS takes the baton from SMS, winning the battle of the mobile inbox and continuing to deliver rich messaging for many years to come. Robert Gerstmann is co-founder and chief evangelist at Sinch
Article originally published by telecomasia.net.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Cookie Statement
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work.
These cookies do not store any personally identifiable information.
Cookie details
Cookie Subgroup | Cookies | Cookies used |
---|---|---|
eu5.mm.sdi.sinch.com | ASP.NET_SessionId | First Party |
community.sinch.com | AWSALB , LiSESSIONID | First Party |
appengage.sinch.com | dd_cookie_test_ | First Party |
tickets.sinch.com | atlassian.xsrf.token , JSESSIONID | First Party |
cockpit2.sinch.com | SESSION | First Party |
engage.sinch.com | instapage-variant-xxxxxxxx | First Party |
dashboard.sinch.com | cookietest | First Party |
brand.sinch.com | PHPSESSID , AWSALBCORS | First Party |
sinch.com | __cf_bm , OptanonConsent , TEST_AMCV_COOKIE_WRITE , OptanonAlertBoxClosed , onesaasCookieSettings, QueryString, functional-cookies, performance-cookies, targeting-cookies, social-cookies lastExternalReferrer, lastExternalReferrertime, cookies, receive-cookie-deprecation _gdvisitor, _gd_session, _gcl_au, _fbp, _an_uid, _utm_zzses, lpv | First Party |
mediabrief.com | __cf_bm | Third Party |
recaptcha.net | _GRECAPTCHA | Third Party |
cision.com | __cf_bm | Third Party |
techtarget.com | __cf_bm | Third Party |
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous.
If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Cookie details
Cookie Subgroup | Cookies | Cookies used |
---|---|---|
community.sinch.com | ValueSurveyVisitorCount | First Party |
buzz.sinch.com | instap-spid.8069 , instap-spses.8069 | First Party |
appengage.sinch.com | _dd_s | First Party |
sinch.com | AMP_TLDTEST , rl_page_init_referrer , rl_trait , _vis_opt_s , __q_state_dp56h9oqwhna9CoL , cb_user_id , __hstc , rl_anonymous_id , rl_user_id , initialTrafficSource , _vwo_uuid , _vwo_uuid_v2 , rl_page_init_referring_domain , _hjIncludedInSessionSample_xxx , apt.uid , __hssrc , test_rudder_cookie , cb%3Atest , __hssc , rl_group_trait , _hjAbsoluteSessionInProgress , _vwo_referrer , _vwo_sn , _vis_opt_test_cookie , _hjFirstSeen , _hjTLDTest , _hjSession_xxxxxx , s_sq , _vwo_ds , rl_group_id , _vis_opt_exp_n_combi , s_cc , _gclxxxx , cb_anonymous_id , cb_group_id , apt.sid , rl_session , _uetvid , AMP_899c7e29a9 , _hjSessionUser_xxxxxx | First Party |
brand.sinch.com | AMP_TEST | First Party |
engage.sinch.com | no-cache , instap-spses.85bb , instap-spid.85bb | First Party |
www.sinch.com | d-a8e6 , s-9da4 | First Party |
nr-data.net | JSESSIONID | Third Party |
sinch-en.newsroom.cision.com | _ga, _gid | Third Party |
sinch.in | _ga_xxxxxxxxxx, _gat_UA-XXXXXX-X, _gid, _ga | Third Party |
g.fastcdn.co | instap-spses.85bb | Third Party |
hello.learn.mailjet.com | pardot, visitor_id, visitor_id##### | Third Party |
www.googletagmanager.com | userId | Third Party |
hello.learn.mailgun.com | visitor_id#####, visitor_id | Third Party |
dev.visualwebsiteoptimizer.com | _vwo_ssm | Third Party |
box.com | box_visitor_id | Third Party |
app.box.com | z, cn | Third Party |
sinch-tfn.paperform.co | laravel_session | Third Party |
go.sinch.in | visitor_id#####, visitor_id | Third Party |
Qualified | __q_local_form_debug | Third party |
Rudderstack | rudder.inProgress, rudder.3156dd1f-7029-4600-ae54-baf147d9af20.queue, rudder.3156dd1f-7029-4600-ae54-baf147d9af20.ack, rudder.3156dd1f-7029-4600-ae54-baf147d9af20.reclaimStart, rudder.3156dd1f-7029-4600-ae54-baf147d9af20.reclaimEnd, | Third party |
6sense | _6senseCompanyDetauls, _6signalTTL | Third party |
Appcues | apc_local_id, apc_user | Third party |
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device.
If you do not allow these cookies, you will experience less targeted advertising.
Cookie details
Cookie Subgroup | Cookies | Cookies used |
---|---|---|
investors.sinch.com | visitor_id | First Party |
community.sinch.com | VISITOR_BEACON , LithiumVisitor | First Party |
sinch.com | _uetsid , ajs_user_id , _gcl_aw , ajs_group_id , AMCV_ , __utmzzses , _fbp , _gcl_au , AMCVS_ | First Party |
go.latam.sinch.com | visitor_id##### , pardot | First Party |
linkedin.com | li_gc, bcookie, lidc, AnalyticsSyncHistory, UserMatchHistory, li_sugr | Third Party |
pi.pardot.com | lpv151751, pardot | Third Party |
hsforms.com | _cfuvid | Third Party |
google.com | CONSENT | Third Party |
sinch.in | _gclxxxx, _gcl_au | Third Party |
www.linkedin.com | bscookie | Third Party |
bing.com | MUID, MSPTC | Third Party |
www.facebook.com | Third Party | |
hello.learn.mailgun.com | pardot | Third Party |
www.youtube.com | TESTCOOKIESENABLED | Third Party |
dev.visualwebsiteoptimizer.com | uuid | Third Party |
g2crowd.com | __cf_bm | Third Party |
pardot.com | visitor_id#####, visitor_id | Third Party |
tracking.g2crowd.com | _session_id | Third Party |
hubspot.com | __cf_bm, _cfuvid | Third Party |
doubleclick.net | test_cookie, IDE | Third Party |
youtube.com | CONSENT, VISITOR_PRIVACY_METADATA, VISITOR_INFO1_LIVE | Third Party |
go.sinch.in | pardot | Third Party |
liadm.com | lidid | Third Party |
www.google.com | _GRECAPTCHA | Third Party |
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies, then some or all of these services may not function properly.
Cookie details
Cookie Subgroup | Cookies | Cookies used |
---|---|---|
portal.sinch.com | pnctest | First Party |
partner.appengage.sinch.com | _dd_s | First Party |
investors.sinch.com | First Party | |
community.sinch.com | LithiumUserInfo , LithiumUserSecure | First Party |
tickets.sinch.com | selectedidp | First Party |
engage.sinch.com | ln_or | First Party |
cockpit2.sinch.com | CSRF-TOKEN , NG_TRANSLATE_LANG_KEY | First Party |
sinch.com | apt.temp-xxxxxxxxxxxxxxxxxx , hubspotutk , ajs%3Acookies , cf_clearance , ajs%3Atest , __tld__ , __q_domainTest , pfjs%3Acookies , ajs_anonymous_id | First Party |
auth.appengage.sinch.com | AUTH_SESSION_ID , KEYCLOAK_3P_COOKIE , KEYCLOAK_3P_COOKIE_SAMESITE , KC_RESTART , AUTH_SESSION_ID_LEGACY | First Party |
www.recaptcha.net | _GRECAPTCHA | Third Party |
boxcdn.net | __cf_bm | Third Party |
d2oeshgsx64tgz.cloudfront.net | cookietest | Third Party |
sinch-np.paperform.co | XSRF-TOKEN, laravel_session | Third Party |
vimeo.com | __cf_bm, vuid | Third Party |
sinch-ca-sc.paperform.co | XSRF-TOKEN, laravel_session | Third Party |
box.com | site_preference | Third Party |
app.box.com | bv | Third Party |
sinch-tfn.paperform.co | XSRF-TOKEN | Third Party |
cision.com | cf_clearance | Third Party |
These cookies are set by a range of social media services that we have added to the site to enable you to share our content with your friends and networks. They are capable of tracking your browser across other sites and building up a profile of your interests. This may impact the content and messages you see on other websites you visit. If you do not allow these cookies you may not be able to use or see these sharing tools.
Cookie details
Cookie Subgroup | Cookies | Cookies used |
---|---|---|
community.sinch.com | ln_or | First Party |
sinch.in | _fbp | Third Party |
youtube-nocookie.com | CONSENT | Third Party |
youtube.com | YSC | Third Party |