How to Use the Vonage Verify RCS Default Agent

If you are already sending OTPs with the Vonage Verify API, you can start delivering RCS messages instantly, with no agent registration and no carrier approval process to complete first. The Vonage Verify RCS Default Agent is a centrally managed, pre-registered RCS agent operated by Vonage under the name Vonage Verify. Any Verify API customer in a supported country can use it by simply omitting the from field in their existing Verify V2 request.

Prerequisites

• A Vonage account with a Vonage Application configured (Application ID and private key, for JWT authentication).
• An existing integration with the Verify V2 API.

Check that Your Target Country is Supported

First, confirm that your end users are located in one of the countries where the Default Agent is Live:

Add RCS to Your Verify Workflow

In your existing Verify V2 request, add "channel": "rcs" to the workflow array. Omit the from field as Vonage automatically routes the message through the Default Agent. No agent ID is needed.

curl -X POST "https://api.nexmo.com/v2/verify" \
    -H "Authorization: Bearer $JWT" \
    -H 'Content-Type: application/json' \
    -d $'{
        "brand": "YOUR_BRAND",
        "workflow": [
        {
            "channel": "rcs",
            "to": "'$PHONE_NUMBER'"
        },
        {
            "channel": "sms",
            "to": "'$PHONE_NUMBER'"
        }
    ]
}'

Handle the Response

A successful request returns a request_id:

{
  "request_id": "REQUEST_ID"
}

Once the end user submits the OTP, check the code using the request_id exactly as you would for any other Verify channel — see Check the Supplied Verification Code.

End-User RCS Experience

When a verification message is delivered via the Default Agent, end users on supported Android devices receive a rich RCS message with the following features:

• Verified sender badge — the message arrives from the carrier-verified Vonage Verify agent (VonageVFY in Singapore), increasing user trust.
• Rich card layout — the OTP is displayed prominently in a styled card, making it easy to read at a glance.
• One-tap Copy Code button — a suggestion chip lets users copy the code directly to their clipboard, reducing input errors.
• Automatic OTP suggestion — on supported Android versions, Google Messages may surface the code above the keyboard as a one-tap autofill suggestion.
• Branded message body — your brand value appears inside the message body, so users see your company name in context even though the agent name is Vonage Verify.
• No app installation required — RCS is built into Android's default Messages app. No downloads or extra steps for the user.

Behavior and Limitations

• The RCS agent sender name is always Vonage Verify (VonageVFY in Singapore) and cannot be customized when using the Default Agent. However, your brand name does appear in the message body via the brand parameter: Your {brand} code is: {code}.
• Opt-outs are scoped to the individual end user and your API key — they do not affect other customers using the same Default Agent.
• No additional setup, allowlisting, or enablement steps are required. All Verify API customers in supported countries can use the Default Agent immediately.
• Standard Vonage Verify API usage limits and fair-use policies apply.
• Billing is identical to standard Vonage Verify RCS pricing. Usage is attributed to your individual API key.

Register Your Own RCS Agent

The Default Agent is a recommended starting point and bridge while your custom agent is being provisioned. You can run your own agent registration in parallel while using the Default Agent, with no disruption to your existing traffic. To get started, use the RCS Agent Builder in the Vonage API Dashboard.

See Also

• Verify V2 API Reference
• Verify Workflow
• RCS channel concepts
• Integrate RCS into your authentication workflows
• RCS Agent Builder guide