Before You Begin
Getting Started with RCS
|Seattle, Washington - USAemail@example.com|
|Detroit, Michigan - USAfirstname.lastname@example.org|
The onboarding process involves several steps. The first is collecting information about the following:
- Which RCS capabilities should we check before we send the message? — For a given messaging campaign, you tell us which RCS capabilities we should check before we send the message. You might want us to check only for rich cards, or you might want us to check for rich cards, chip lists, and various other capabilities of a UP 2.0-compliant device.
- Will you use the SMS fallback feature? — Utilizing this feature enables our system to send an RCS message as an SMS message to a handset that doesn' support RCS. If you use SMS fallback, we'll configure your OpenMarket account to use our Global SMS API.
- Will you send RCS messages to subscribers in the US, the UK, or both? — We need to know this so we can assist in registering your bot and testing your campaign with our MaaP partners.
- Do you intend to store your media content in OpenMarket's content management system? — If so, we will provision your account to use our Media Upload API.
Once we collect your information and configure your account in our system, there are two more important steps to complete:
- Register your bot with the mobile operators.
- Test your message with our MaaP partners to pass their certification.
Again, your OpenMarket Implementation Manager will assist with these steps.
Deciding which RCS capabilities to use
As part of the onboarding process you'll need to decide which RCS capabilities your RCS messages will use. Here's an overview of them:
- Chat — Opens the end user's default messaging application for a chat conversation.
- Image — Sends an image.
- Video — Sends a video.
- Chatbot — Opens an AI chat conversation based on keywords sent back by the end user.
- File Transfer — Sends a file to the end user's handset.
- Geolocation — Opens the end user's default map application to share his or her location.
- Calendar Event — Adds an appointment reminder to the end user's default calendar application.
- Dial Number — Displays a phone number that, when tapped by the end user, dials the number.
- Open URL — Displays a website URL that, when tapped by the end user, opens a web page using the phone's default browser.
- Revocation — Allows a message to be revoked.
- Rich Card Stand Alone — Sends a single rich card to the end user's handset.
- Rich Card Carousel — Sends multiple rich cards in a carousel format to the end user's handset.
Testing your RCS messages
Once your account is fully configured, you'll want to test your RCS messages. The following table recommends RCS-capable handsets to use. Make sure you provide your account manager with your test phone numbers so that we can whitelist them in our environment.
|Google / Sprint||Pixel 2|
|Google / Sprint||Pixel XL|
|Vodafone||Samsung Galaxy S8||Supports UP 2.0|
|Vodafone||Vodafone Model VFD710||Supports UP 1.0 and UP 2.0|
|Samsung/AT&T||Samsung Galaxy S7|