> 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.

# Linked reply

POST 

Notification sent when the user replies to a *reply*-type suggestion (or to a message) you previously sent. The root `message_id` is the original outbound message being replied to, and the root `status` is forced to `DELIVERED` (`data.action` is always `REPLY`).

Reference: https://docs.chatbridge.mx/rcs/webhooks/rcs-reply-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) — Original outbound message being replied to.
- `status` (enum, optional) — Forced to `DELIVERED`; `data.action` is always `REPLY`.
  - 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` (ReplyData, optional) — Event-specific content; its shape depends on the event type.

## Types

### ReplyData

- `sender_phone` (string, optional) — User's number, international format with the 52 country code.
- `action` ("REPLY", optional)
- `reply_text` (string, optional) — Text of the user's reply.