> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revreply.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Orchestrator First Message Webhook

> Sent when the first inbound message of a conversation is received.

<Badge color="blue">WEBHOOK</Badge> `POST`

<Note>
  This webhook is sent when the first inbound message of a conversation is received.
</Note>

## Overview

The `orchestrator.first.message` webhook is triggered when the first inbound message of a conversation is received.

RevReply sends an HTTP `POST` request to your configured webhook URL containing an event object and information about the first received message.

## Event

The webhook event is identified by the following name:

```text theme={null}
orchestrator.first.message
```

**Description:** A first message has been received.

## Payload

All webhook requests follow the same top-level structure, containing an `event` object and a `data` object.

### Event object

| Field         | Type      | Description                                                              | Example                              |
| ------------- | --------- | ------------------------------------------------------------------------ | ------------------------------------ |
| `name`        | `string`  | Unique identifier of the webhook event.                                  | `orchestrator.first.message`         |
| `description` | `string`  | Human-readable description of the event.                                 | `A first message has been received.` |
| `sent_at`     | `string`  | ISO 8601 UTC timestamp indicating when the webhook was generated.        | `2026-07-17T20:45:12.000000Z`        |
| `timestamp`   | `integer` | Unix timestamp, in seconds, representing when the webhook was generated. | `1784321112`                         |

### Data object

The `data` object contains information about the first inbound message, lead, and conversation.

| Field                | Type             | Description                                                 | Example                                                 |
| -------------------- | ---------------- | ----------------------------------------------------------- | ------------------------------------------------------- |
| `user_id`            | `integer`        | Identifier of the user.                                     | `123`                                                   |
| `lead_id`            | `integer`        | Unique identifier of the lead.                              | `98765`                                                 |
| `inbox_manager_id`   | `integer`        | Identifier of the Inbox Manager handling the conversation.  | `12`                                                    |
| `thread_id`          | `string`         | Unique identifier of the conversation thread.               | `4e9bc3a2`                                              |
| `lead_name`          | `string`         | Name of the lead.                                           | `Jane Doe`                                              |
| `inbox_manager_name` | `string`         | Name of the Inbox Manager assigned to the conversation.     | `Sales Assistant`                                       |
| `message_id`         | `string`         | Unique identifier of the received message.                  | `01JZ8WQW5A9K7T`                                        |
| `from_email`         | `string`         | Sender's email address.                                     | `jane@example.com`                                      |
| `to_email`           | `string`         | Recipient email address.                                    | `sales@example.com`                                     |
| `cc_emails`          | `array<string>`  | List of CC recipients.                                      | `[]`                                                    |
| `bcc_emails`         | `array<string>`  | List of BCC recipients.                                     | `[]`                                                    |
| `subject`            | `string`         | Subject of the message.                                     | `Question about pricing`                                |
| `body`               | `string`         | Content of the received message.                            | `Hi, I'd like to know more about your enterprise plan.` |
| `phone_number`       | `string \| null` | Lead's phone number, when available.                        | `+15551234567`                                          |
| `lead_email`         | `string`         | Primary email address associated with the lead.             | `jane@example.com`                                      |
| `lead_email_list`    | `array<string>`  | List of all known email addresses associated with the lead. | `["jane@example.com"]`                                  |

## Example payload

```json theme={null}
{
  "event": {
    "name": "orchestrator.first.message",
    "description": "A first message has been received.",
    "sent_at": "2026-07-17T20:45:12.000000Z",
    "timestamp": 1784321112
  },
  "data": {
    "user_id": 123,
    "lead_id": 98765,
    "thread_id": "4e9bc3a2",
    "lead_name": "Jane Doe",
    "inbox_manager_id": 12,
    "inbox_manager_name": "Sales Assistant",
    "message_id": "01JZ8WQW5A9K7T",
    "from_email": "jane@example.com",
    "to_email": "sales@example.com",
    "cc_emails": [],
    "bcc_emails": [],
    "subject": "Question about pricing",
    "body": "Hi, I'd like to know more about your enterprise plan.",
    "phone_number": "+15551234567",
    "lead_email": "jane@example.com",
    "lead_email_list": [
      "jane@example.com",
      "j.doe@company.com"
    ]
  }
}
```

## Handling the webhook

Your webhook endpoint should accept an HTTP `POST` request with a JSON body.

A successful webhook handler should process the event and return an appropriate HTTP success response.

Because webhook delivery is event-driven, your application should identify the event using `event.name` before processing the contents of `data`.

## Event details

| Property     | Value                                                   |
| ------------ | ------------------------------------------------------- |
| Event        | `orchestrator.first.message`                            |
| Method       | `POST`                                                  |
| Trigger      | The first inbound message of a conversation is received |
| Content type | `application/json`                                      |