> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.chatbridge.mx/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.chatbridge.mx/_mcp/server.

# Suggestion click

POST 

Notification of a user interaction with a suggestion of the message (open URL, dial, calendar, location, or a generic click).

The root `status` is forced to `DELIVERED`; the real interaction type travels in `data.action`. `data.element_type` and `data.element_value` describe the element the user interacted with; `data.message_index` is only present when the event applies to a specific card.

Reference: https://docs.chatbridge.mx/rcs/webhooks/rcs-suggestion-click-webhook

## Request

### Payload

- `origin` (enum, optional) — Origin of the message: direct API send (`API`) or bulk campaign send (`CAMPAIGN`).
  - Allowed values: `API`, `CAMPAIGN`
- `channel` (enum, optional) — RCS channel of the send, according to the type of the agent/template used.
  - Allowed values: `RCS_BASIC`, `RCS_SINGLE`, `RCS_CONVERSATIONAL`
- `message_id` (string, optional) — The same `message_id` returned by `POST /v1/rcs/messages`, except on inbound message events, where it identifies the inbound message itself.
- `status` (enum, optional) — Forced to `DELIVERED`; the real interaction type travels in `data.action`.
  - Allowed values: `SENT`, `DELIVERED`, `READ`, `FAILED`, `EXPIRED`
- `occurred_at` (datetime, optional) — Moment of the event.
- `timestamp` (string, optional) — Moment of the event as epoch seconds (string). Redundant with `occurred_at`; use whichever you prefer.
- `campaign_id` (string, optional) — Optional. Only present when `origin` is `CAMPAIGN` and the message belongs to a campaign; omitted otherwise.
- `data` (SuggestionClickData, optional) — Event-specific content; its shape depends on the event type.

## Types

### SuggestionClickData

- `sender_phone` (string, optional) — User's number, international format with the 52 country code.
- `action` (enum, optional) — Type of interaction.
  - Allowed values: `OPEN_URL`, `DIAL`, `CREATE_CALENDAR_EVENT`, `VIEW_LOCATION`, `SHARE_LOCATION`, `CLICK`
- `element_type` (string, optional, nullable) — Element the user interacted with: `openUrl`, `dial`, `reply`, `createCalendar`, `viewLocation`, `shareLocation`, or `unknown`.
- `element_value` (string, optional, nullable) — URL, phone number, or text, depending on `element_type`.
- `message_index` (integer, optional) — Optional. Only present when the event applies to a specific card.