Unified RCS now reaches iOS · CS Talk registration API
Unified RCS lets you send RCS messages to both Android and iPhone, and you can now register and update CS Talk through the API.
26.10.15 Unified RCS now reaches iOS · CS Talk registration API
In one line
Unified RCS lets you send RCS messages to both Android and iPhone (iOS). iPhone users now receive the RCS message itself instead of a fallback text. A CS Talk registration and update API and a CS Talk integration flow guide have also been added.
What it does
RCS SMS and LMS sent from the web console now go out as unified RCS, so any device that supports Korean carrier RCS — Android or iPhone — can receive them.
- iPhone (iOS) delivery — RCS used to be Android only; it now reaches iPhone as well.
- Applied automatically — Nothing to configure. Send from the same RCS screen as before, at the same price.
- Advertising notice filled in automatically — Tick the promotional-content box and the advertising notice and toll-free opt-out number are inserted for you.
- SMS —
(광고) brand nameat the very start of the body,무료수신거부 080-XXXX-XXXXat the end. - LMS —
(광고)before the title, the brand name on the first line of the body,무료수신거부 080-XXXX-XXXXat the end.
- SMS —
- Preview — The preview on the right shows exactly how the message goes out, advertising notice included.
How to use it
- Go to RCS send.
- Choose the brand and chatroom in the sender settings.
- Write a new message, or load a template you registered.
- For promotional messages, tick "this contains promotional information" and check the preview.
- Enter the recipients and send.
Things to note
- Button labels now take up to 7 characters for both SMS and LMS (previously up to 17).
- A promotional SMS allows up to 100 characters of body text, including the advertising notice and the opt-out line.
- A promotional LMS allows a 30-character title including
(광고), which leaves 25 characters you type yourself. - Existing templates with button labels of 8 characters or more, or promotional LMS titles of 26 characters or more, show a notice at the send step. Edit the template, then send.
- Devices without RCS support still receive the fallback text as before, so keep the fallback setting on.
If you integrate through the API
For the difference between unified RCS and Android RCS, see Unified RCS and Android RCS. The send specification is in the RCS Biz Message API reference, and fallback setup is covered in Failover message.
Also new in the API — register and update CS Talk
You can now register CS Talk and change its settings through the API.
- Register CS Talk
POST /api/comm/v1/account/kakao/sender/cstalk— Registers a sender profile for CS Talk. The result of each step, from granting the permission to linking your account, is returned indata.steps. - Update CS Talk
PUT /api/comm/v1/account/kakao/sender/cstalk/{senderKey}— Updates the webhook URL and whether CS Talk and chat are enabled. The sender profile key cannot be changed.
See the CS Talk API reference for the request and response specification and the sandbox. The order of steps from registration through webhooks to ending a conversation, and how to connect it to your CRM or your own support system, are covered in CS Talk integration flow.