RCS via Webex Connect

Connect an agent to RCS using your own Webex Connect account. This is the unmanaged path for the RCS channel. Anychat sends and receives RCS messages through an app in your Webex Connect tenancy, and you remain responsible for that account and the RCS agent registered under it.

If you don't have a Webex Connect account, choose Let Anychat set this up for you when connecting the channel. Anychat provisions and verifies the RCS agent on its own carrier relationships, with no credentials needed. This guide covers only the bring-your-own-Webex path.

What you need

A Webex Connect tenancy with a Service that has a launched RCS app asset. From the Webex Connect dashboard, collect four values:

Field	Where to find it
Service key	Your Service → API tab → Auth Type: Service Key
App ID	The RCS app asset within your Service (looks like a_1768…)
Webex Connect base URL	Your tenant's API base URL, e.g. https://api.us.webexconnect.io
Hub secret	A secret string you choose; you'll enter the same value on the webhooks in step 3

The hub secret is required for inbound messages

The console accepts a binding without a hub secret, but the Anychat gateway rejects unsigned webhooks. Without it your agent can send but never receives messages. Always set one, and use the same value in Webex Connect and in the console.

Step 1: Connect the channel in the console

1. Open the agent in the console and go to Channels.
2. In the Available section, find RCS and click Connect.
3. Choose Use your own account, then select Your own Webex Connect account as the provider.
4. Enter the Service key, App ID, hub secret, and base URL collected above, then Continue to review and Submit.

Unmanaged bindings activate immediately, so the binding reads Active as soon as it is created. Outbound messaging works right away. Inbound needs the webhooks in the next step.

Step 2: Point Webex Connect webhooks at Anychat

Inbound messages and delivery receipts reach Anychat through two separate outbound webhooks in Webex Connect. Both use the same URL, built from your App ID:

https://gateway.anychat.ai/maap/webexRcs/receiver/{appId}

For example, with App ID a_176832859458021950 the URL is https://gateway.anychat.ai/maap/webexRcs/receiver/a_176832859458021950.

Webhook 1, inbound messages (app-level):

1. In Webex Connect, go to Assets → Integrations → Add Integration → Outbound Webhook.
2. Entity: select your RCS app.
3. Notifications: check all of them (Incoming Message, Postback Response, Incoming Attachment, Location Response, Subscribe, Unsubscribe).
4. URL: the receiver URL above.
5. Enable Hub Signature and enter your hub secret.

Webhook 2, delivery receipts (service-level):

Delivery receipts are not available on the app-level webhook, so add a second one:

1. Assets → Integrations → Add Integration → Outbound Webhook again.
2. Entity: select your Service (not the RCS app).
3. Channel: RCS.
4. Notifications: check Submitted, Delivered, Read, Failed.
5. URL: the same receiver URL.
6. Enable Hub Signature with the same hub secret.

Step 3: Test

Send an RCS message from a phone to your RCS agent. Until you launch the channel in Anychat, the phone must be on the binding's early-access list. The agent should answer on the channel; the conversation appears in the agent's Activity feed in the console.

If the agent doesn't respond, the usual suspects are a webhook URL that does not end in your exact App ID, or a hub-secret mismatch between Webex Connect and the binding. Either one makes the gateway reject the webhook.

Rotating credentials

If you rotate the Service key or hub secret in Webex Connect, open the binding's detail page in the console and use Rotate credentials to submit the replacement values. Secrets are write-only: the console never displays them back. Remember that changing the hub secret also means updating both outbound webhooks in Webex Connect to match.