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

​
Best interface

The manage-replies skill for approved, gated sending. Webhooks for real-time — subscribe to email_replied and reply_categorized events instead of polling. MCP for conversational triage in a client.

​
Steps

1

Receive the signal (real-time) or poll (simple)

Real-time: subscribe to webhook events — email_replied, reply_categorized — pushed to your endpoint (see payloads). Polling: reply api /v3/inbox/threads/filter --body '{"source":"unread"}' or MCP reply_get_inbox_emails.
2

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

Read the full thread context

4

Draft, show, confirm, send

Sending reaches a real prospect — a high-stakes action. 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.
MCP: reply_send_inbox_reply (channel must match the thread; body only in v1 — no Cc/Bcc, attachments, or scheduling). See the MCP recipe.
5

Categorize and route

Route meeting-intent threads to scheduling; mark contacts as replied to stop further automated outreach (MCP: reply_mark_contacts_as_replied).

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