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

# Convert replies into meetings

> Triage the inbox, surface interested prospects, and send approved replies — event-driven or conversational.

**Outcome:** every reply triaged, interested prospects surfaced, responses sent with explicit
approval — from both email and LinkedIn, in one inbox.

## Best interface

<Note>
  **The [`manage-replies` skill](/skills/catalog#manage-replies)** for approved, gated sending.
  **Webhooks for real-time** — subscribe to [`email_replied` and `reply_categorized`
  events](/webhook-events) instead of polling. **MCP** for conversational triage in a client.
</Note>

## Steps

<Steps>
  <Step title="Receive the signal (real-time) or poll (simple)">
    Real-time: subscribe to [webhook events](/webhook-events) — `email_replied`,
    `reply_categorized` — pushed to your endpoint (see
    [payloads](/webhook-event-payloads)). Polling:
    `reply api /v3/inbox/threads/filter --body '{"source":"unread"}'` or MCP
    `reply_get_inbox_emails`.
  </Step>

  <Step title="Triage by category and intent">
    Group threads by category and meeting intent. LinkedIn and email replies land in the same
    unified inbox with the same categories.

    ```bash theme={null}
    reply api /v3/inbox/threads/categories --json          # resolve category ids first
    reply api /v3/inbox/threads/filter \
      --body '{"categoryIds":[7],"onlyWithMeetingIntent":true}' --json
    ```
  </Step>

  <Step title="Read the full thread context">
    ```bash theme={null}
    reply api /v3/inbox/threads/58217 --json
    reply api /v3/inbox/threads/58217/messages --json
    ```
  </Step>

  <Step title="Draft, show, confirm, send">
    Sending reaches a real prospect — a [high-stakes action](/agents/safety). Nothing here prompts
    for confirmation, so show the exact text, get approval, then send. The body's `channel` must
    match the thread's, or the call is rejected with `inboxThread.channelMismatch`.

    ```bash theme={null}
    reply api /v3/inbox/threads/58217/messages \
      --body '{"channel":"email","message":"Thanks — does Tuesday at 10am work?","applySignature":true}' --json
    ```

    MCP: `reply_send_inbox_reply` (channel must match the thread; body only in v1 — no Cc/Bcc,
    attachments, or scheduling). See the [MCP recipe](/mcp/recipes#reply-to-an-inbox-thread).
  </Step>

  <Step title="Categorize and route">
    ```bash theme={null}
    reply api /v3/inbox/threads/58217/category --method PUT --body '{"categoryId":42}' --json
    ```

    Route meeting-intent threads to scheduling; mark contacts as replied to stop further automated
    outreach (MCP: `reply_mark_contacts_as_replied`).
  </Step>
</Steps>

## Availability notes

* Inbox triage, replying, categorization, and webhooks: **available today**.
* **Fully automated reply policies (auto-answer) are not in Skill v1** — every send is
  human-approved. For AI-drafted replies with an approval queue, see
  [Build an AI SDR](/guides/build-an-ai-sdr).

## Related

* [Build a supervised AI SDR](/guides/build-an-ai-sdr) — Jason drafts the replies, you approve
* [Automate outbound end-to-end](/guides/automate-outbound) — the event-driven pattern in full
* [Webhook events catalog](/webhook-events)