OTT (over-the-top) applications are now the primary channels for P2P (person-to-person) communication, while SMS continues to be the mainstay of application to person (A2P) enterprise messaging which is effective because it is ubiquitous, secure and the most trusted format by consumers.
Enterprises will send 2.8 trillion A2P SMS messages by 2022 with revenue of $26.6 billion.
At the same time, smartphone technology is facilitating new patterns of consumer use. In terms of P2P messaging consumers have become habituated to more immersive OTT chat app formats like Line, KakaoTalk, WeChat, Viber and WhatsApp, that enable richer features like file and image transfer and group chat.
Comparing these features to SMS messaging, it’s obvious that there is a growing user experience gap, which is fuelling consumer demand for similar richer experiences from enterprises and the brands that they interact with. As a result, over the last few years most OTTs have opened up support for enterprises to do A2P messaging in addition to allowing people to chat to friends and family.
Being able to ‘chat’ to a bank for example, at a convenient time – whilst on a bus, or waiting in a café, is becoming an expectation. Not only is this kind of responsive customer communication highly prized by consumers, it is one of the prime ways in which enterprises can successfully differentiate themselves in highly competitive sectors like commerce and banking.
However, unlike SMS, which is a native function of every handset, chat apps rely on an install. This means enterprises have to support an ever-growing number of messaging channels, all of which only access a subset of the customer base since not everyone has downloaded every chat app.
Alternatively, an enterprise might offer its own branded app as a container for customer service functions – an expensive option that experience tells us has been met with limited success. Why would a consumer download an enterprise app that was only used once or twice a year? As a result, many customer relationships aren’t adequately supported by the OTT messaging environment or by enterprise applications. So how can enterprises meet this demand?
For some time now, telcos and messaging providers have been touting the arrival of RCS messaging. Billed as the next-generation messaging protocol – SMS 2.0 – RCS is championed by the GSMA, Google, Android phone manufacturers like Samsung, and mobile carriers around the world. It combines an OTT app-like experience, with the potential ubiquity of SMS so that rich features such as images, QR codes, linked buttons and chat can all be used in a branded environment on the native handset.
There’s evidence that RCS adoption is accelerating. New stats from Mobilesquaredshow that the Asian RCS market will grow from 472m users in 2019, to 1.6bn by 2023.
At the OS level, Android and Microsoft support RCS. According to the latest IDC figures, Android had an 85% market share of the 1.5 billion new smartphones shipped in 2018. Crucially, Android OEMs like Samsung, LG, and Huawei support RCS, so via the usual two-year renewal cycle of smartphones, RCS will grow significantly as a native function of nearly all new Android devices – an installed user base of approximately five billion globally.
Getting RCS to market has been a slow process. To date, the GSMA lists 75 mobile operators worldwide (including KDDI, NTT Docomo, KT, SK Telecom and Globe Telecom in the APAC region) that have adopted its Messaging-as-a-Platform (MaaP) and Universal Profile specifications within their networks, so that RCS is enabled. But there is still some way to go as many mobile operators have yet to do so.
Mobile operators of course have multiple priorities, not least rolling out 5G which is absolutely critical to reducing churn and competing for new revenues from the services that 5G enables.
Part of the problem lies with the messaging ecosystem. To enable RCS, mobile operators need to implement a technology that supports both P2P and A2P messaging traffic. The vendor community for providing RCS infrastructure (with appropriate SLAs) either on-premise or on an as-a-service basis, is relatively small.
Moving forward more vendors are entering the space and, by providing turnkey solutions for operators, will help to accelerate RCS adoption.
In order for mobile operators to capitalize on the next generation of enterprise messaging, launching RCS and building a large user base which will entice enterprises to embrace this new channel is critical. If the mobile operators are slow in doing this a large part of the B2C messaging market that is SMS-based today will move to OTTs instead of remaining with the mobile operators. In addition, the mobile operators would miss out of the growth that the richer and more conversational forms of messaging supported by these new technologies will drive.
Consumers are telling us that they are more than ready for RCS, whilst enterprises, which are dependent on RCS being available to their customers, are also keen to start engaging with the new messaging standard. The next twelve months will see the messaging ecosystem shake out its wrinkles so that RCS will become table stakes for any enterprise that is serious about customer service, communication and engagement.
Robert Gerstmann is co-founder and chief evangelist at Sinch.
Article first published in www.telecomasia.com
Table of contents
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 |
terminus.services | terminustb | 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 |