Text Suggestions

Text Suggestions allow you to guide the user through a conversation by providing predefined response options. When a user taps a suggestion, that text is sent as their response — creating a more interactive, structured experience.

When a user taps a suggested reply, your agent receives an event that contains the reply's text and postback data.

Suggested replies are useful for:

Menu navigation

Collecting quick responses

Confirmations (e.g., Yes/No)

Driving specific conversation flows

✅ Supported Features

Feature	Description
Tap-to-send	When tapped, the suggestion is sent as a standard text message from the user.
Character limit	Typically 20 characters per suggestion.
Multiple options	You can include up to 4 suggestions per message.
Quick interactions	Speeds up user responses and reduces input errors.
No persistence	Suggestions disappear after being used or once the message is dismissed.

Suggested actions

Agents can suggest that users to dial a number, open a location on a map, open a URL or create a calendar event.

When a user taps a suggested action, your agent receives an event that contains the action's postback data.

RCS supports the following types of suggested reply & actions, which can be included to enhance user interaction:

📩 Suggested Replies
Suggested replies guide users through conversations by providing responses that your agent knows how to react to.

When a user taps a suggested reply, your agent receives an event that contains the reply's text and postback data. The payload has a maximum of 2000 characters.
Example: "Yes", "No", "Tell me more"

📞 Suggested Actions – Dial a number
The Dial action guides the user to dial a phone number specified by your agent. Phone numbers can only include digits (0-9), plus sign (+), asterisk (*), and number sign (#). The E.164 international format (for example, +14155555555) is supported but not required. That is, both +14155555555 and 1011 are valid entries.
Example: "Call Support" → Dials +919801234567

📍 Suggested Action – View Location
The View location action displays a location in the user's default map app. You can specify the location either by latitude and longitude or with a query based on the user's current location. You can also set a custom label for the pin that displays in the map app.
Example: "View location"

📍 Suggested Action – Share a Location
The Share Location action allows the user to share a location with your agent. The user can share either their current location or a manually selected location from the Maps app.
Example: "Share a location"

🔗 Suggested Actions – Open a URL
The Open URL action lets you guide users to a web page specified by your agent. By default, the web page opens in the user's browser. If a user has a default app configured for the web page, that app will open instead. In that case, the icon on the suggested action button will be the app's icon.
Example: "Visit Website" → Opens https://example.com

🔗 Suggested Actions – Open a URL with webview
The Open URL with webview action loads the specified web page inside the messaging app with the rendering engine of your default browser. This allows the user to interact with the web page without leaving the RBM conversation. If the user's device doesn't support webviews, the web page opens in the user's browser instead.icon.
Example: "Visit Website" → Opens https://example.com

📅 Suggested Action – Create a calendar event
The Create calendar event action opens the user's calendar app and begins to create a new event with the specified information.

A calendar event title is required. It has a maximum of 100 characters. The calendar event description is optional and has a maximum of 500 characters.
Use case: Appointment scheduling.

Example

The following code sends text with two suggested replies. For formatting and value options, see SuggestedReply.

application/json

Body

message

string

required

data

array [object {3}]

required

messageId

string

optional

mobile

string

optional

charges

number

optional

Example

{
    "message": "1 numbers accepted",
    "data": [
        {
            "messageId": "a8XXXXXX-1bXX-4XXd-b5XX-5dXXXXXX:1",
            "mobile": "+9198XXXXXXXXX",
            "charges": 0.05
        }
    ]
}

✅ Supported Features

Suggested actions

Example

Request

Responses

Text Suggestions

✅ Supported Features#

Suggested actions#

Example#

Request

Responses

✅ Supported Features

Suggested actions

Example