Objective
Connecting Google RCS to Conversational Connect (Jumper.ai) - Guided Method
Applies To
- Jumper.ai
- Conversational Connect
- RCS
- Channel
- Connection
Prerequisites
- Have an account within the Vonage API dashboard.
- Have an account within Jumper.ai.
- For the Google RCS onboarding process, refer to Setting up a RBM Agent for RCS Messaging, or please reach out to your Account Manager, Customer Solution Architect (CSA), or Partner Manager.
- Have Google RCS connected under the Vonage API dashboard.
Note:
- Jumper leverages Vonage Messages APIs for RCS. Refer here to understand RCS, coverage, rate limits, and other technical specifications.
- Find FAQs about Rich Communication Services(RCS) here.
Procedure
The following topics will be covered:
- Connecting the Google RCS channel within Jumper.ai
- Disconnecting the Channel or Updating the Private Key
Connecting the Google RCS channel within Jumper.ai
To connect your RCS Agent to Jumper, follow the steps below
-
Navigate to Channels → Google RCS in the menu, select the Guided Setup option, and click Next
-
On the Sign In screen, enter your API Key and API Secret, then click Next to continue.
S.No Information Required Where to find them 1 API Key Vonage API dashboard → API Settings 2 API Secret Vonage API dashboard → API Settings
Instructions to find the required informationAPI Key & API Secret: You can locate your API Key and API Secret under the API settings page of your Vonage API dashboard.
Please note: For security reasons, the API Secret can no longer be copied or viewed. If you have forgotten the API Secret provided when creating your Vonage API Dashboard account, you can generate a new API Secret and use the new one.
-
In the Link account section, you will see the external accounts (i.e., RCS Agents) already connected to your Vonage API account, with their status shown as linked or not linked to a specific Vonage API Application; select the desired account using the radio button and click Next to proceed.
External Accounts: You can locate your External Accounts under the Messaging Section of your Vonage API dashboard.
If no existing link is found, the system will create an application in the Vonage API Dashboard and proceed directly to the Complete step. If your external account is already linked to a different Vonage API application, a confirmation pop-up will appear asking whether you want to connect it to the new application and disconnect it from the old one.
To Proceed with New Linking
- Review the current and target applications carefully.
- Click Confirm to proceed with the new connection.
The account will be unlinked from the previous application and linked to the new one.
To Cancel the Linking Operation-Click Previous to return to the previous step.
The existing connection will remain unchanged.
-
Once you confirm, the application will be created in the Vonage API dashboard, and you will be taken to the Complete step. Here, you will see the connection details: the RCS Agent Name displayed under ID, App ID (the ID of the application created in the Vonage API dashboard), and API Key. Review these details carefully, make a note of the App ID, and click Done to finish the process and activate your Google RCS integration.
Application: You can locate the application using the App ID (example: 129e74c8-8ef8-4d62-b99f-244f5304ce28) in the Applications section of your Vonage API Dashboard.
-
Once your Google RCS channel is connected successfully, it will show under Channels → Google RCS.
When the connection is established, send one outbound and one inbound test message via Jumper.ai to ensure the connection is working properly and that messages are being sent and received successfully, before proceeding with bulk messaging.
Disconnecting the Channel or Updating the Private Key
-
To disconnect or to connect a new RCS application, simply click on the Disconnect option & reconnect to the new application.
Note: If you disconnect, all existing associations with customers, broadcasts, and bot builders will be lost. Therefore, exercise caution before disconnecting. If there are no other changes, it is recommended to update the private key instead of simply disconnecting. -
Updating the Private Key: If you’ve made any configuration changes to the application and are unable to send or receive messages, try updating the private key to restore connectivity instead of disconnecting completely and reconnecting again.
SMS FAILOVER
Failover refers to the capability to switch to an alternate communication channel when the primary channel cannot deliver a message.
Jumper.ai supports an SMS Failover mechanism. If you wish to use this feature, please enable and connect the SMS channel. Click here to learn more about connecting the SMS sales channel.
Note: If the SMS channel is unavailable under the Jumper.ai account, connect with your Account Manager to enable the SMS channel as per your plan.
Articles in this section
- Connecting Vonage’s WhatsApp Business Account to Conversational Connect (Jumper.ai) Dashboard - Guided Method
- Connecting Google RCS to Conversational Connect (Jumper.ai) - Guided Method
- Setting up a WhatsApp widget on your website with Conversational Connect (Jumper.ai)
- Customer Opt-In Options for WhatsApp Business with Conversational Connect (Jumper.ai)
- How to add and manage multiple Sender ID for SMS in Conversational Connect (Jumper.ai)?
- Connecting SMS to Conversational Connect (Jumper.ai) - Manual Method
- Connecting WhatsApp to Conversational Connect (Jumper.ai) Dashboard via Vonage API Dashboard - Manual Method
- Connecting Google RCS to Conversational Connect (Jumper.ai) - Manual Method