Overview
Capability Reviewed · not yet fact-checked
Can Reply do the task you need? Each capability page states what Reply can and cannot do, required inputs, outputs, limits, and when to choose something else.
A capability page answers the selection question — can Reply perform this task? — before you read any implementation detail. Every page states what Reply can and cannot do, the inputs it needs, the limits that apply, what you still build yourself, and links straight to the workflow, specifications, and API/MCP/CLI surfaces that implement it.
Data and prospecting
Prospect search
find people and companies by ICP criteria in Reply Data
Contact management
contacts, companies, lists, stages, deduplication
Data enrichment
fill emails, phones, and profile fields
Outreach channels
Email outreach
sequences, variants, tracking, limits, scheduling
LinkedIn outreach
visits, connections, messages, InMail
Multichannel outreach
email, LinkedIn, calls, SMS, WhatsApp in one flow
Replies, analytics, AI
Reply management
detection, classification, AI-drafted responses
Campaign analytics
per-sequence, per-channel, per-team reporting
Deliverability
warmup, domain health, safety limits
AI SDR
Jason AI generates, launches, and runs outreach end to end
Planned
Calls, SMS, and WhatsApp are covered inside Multichannel outreach, and the shared inbox inside Reply management, until they get dedicated pages.
| Page | Status |
|---|---|
| Company search | Not written |
| Calls · SMS (dedicated pages) | Not written |
| Shared inbox | Not written |
| Meetings | Not written |
| CRM integration | Not written |
Related
- Workflows — complete outcomes built from these capabilities
- When to use Reply — the honest fit assessment
Build with Reply
- REST API: docs.reply.io
- MCP: agents.reply.io/mcp · CLI: agents.reply.io/cli · Skills: agents.reply.io/skills