# What is Reply?

> Reply is a sales engagement platform — prospect data, contact management, multichannel outreach execution, reply handling, deliverability, analytics, and an AI SDR.

**Reply is a sales engagement platform: Reply Data prospect search, contact and account management in the People section, multichannel sequences with email, LinkedIn, call, SMS, WhatsApp, task, Zapier, and condition steps, MailToaster warm-up, a consolidated inbox with AI-assigned categories, eight Reports dashboards, meeting booking, CRM integrations, the Findy Chrome extension, and Jason AI SDR.**

_Status: Reviewed — human-edited, facts not yet confirmed against the product._

Reply is infrastructure for outbound sales. In concrete modules:

| Module | What Reply provides |
| --- | --- |
| Prospect data | Reply Data (Realtime B2B Data): live contact information from LinkedIn based on your filters — including Sales Navigator URL import, keywords, and exclusion filters — saved to lists and sequences on Reply credits. See [Prospect search](/capabilities/prospect-search) and [enrichment](/capabilities/data-enrichment) |
| Contacts and accounts | The People section: [contacts](/specifications/contacts) with [lists](/specifications/lists), custom fields, import/export, and advanced filters; accounts group contacts by [company](/specifications/companies) with stages such as New, Qualified, Meeting Booked, and Closed-Won. [Deduplication](/behavior/contact-deduplication) runs on the contact identifier chosen at import |
| Sequences | [Sequences](/specifications/sequences) combine Email (automatic and manual), Call, SMS (automatic and manual), WhatsApp, LinkedIn (automatic and manual), Zapier, Task, and Condition [steps](/specifications/sequence-steps) with A/B variants, variable-based personalization, and [schedules](/specifications/schedules) — built from a template, from scratch, from an AI prompt, or by Jason AI SDR |
| Email accounts and warm-up | Connect Gmail, Outlook/Office 365, Exchange, or any IMAP/SMTP provider — the sending domain must be corporate, not generic. MailToaster warms up mailboxes with one warm-up seat per connected mailbox. See [Email accounts](/specifications/email-accounts) and [Deliverability](/capabilities/deliverability) |
| Inbox | The consolidated [inbox](/specifications/inbox) gathers threads from all sequences and team members; an AI algorithm assigns categories such as Interested, Not interested, Not now, and Do not contact, custom categories can be added, and Jason AI can prepare draft replies. See [Reply management](/capabilities/reply-management) |
| Calls and SMS | Cloud Calls places, records, and logs calls (with resolutions) directly in the platform from rented numbers; SMS steps run automatically or manually with a dedicated SMS Inbox for responses |
| Tasks | The Tasks page manages To Do, Call, LinkedIn, Manual Email, Manual SMS, WhatsApp, and Meeting tasks for you and your team, executed with the Chrome extension |
| Meetings | Booking links with availability windows, buffer times, and scheduling horizons; calendars connect through Google Calendar, Calendly, and Zoom |
| Analytics | Per-sequence Stats plus the Reports dashboards: Emails, LinkedIn, Calls, Tasks, Team Performance, Channel Efficiency, Agency, and Trends. See [Campaign analytics](/capabilities/campaign-analytics) |
| Integrations | Native Salesforce, HubSpot, Pipedrive, and Copper CRM integrations; Zapier for hundreds of other apps; a REST API; and an MCP server that connects AI models and automation platforms such as Claude, ChatGPT, n8n, and Make.com |
| AI SDR | [Jason AI](/capabilities/ai-sdr): defines your ideal customer profile from your website, finds contacts in real time from LinkedIn data, builds multichannel sequences, personalizes messages, adds contacts daily on Autopilot, verifies email addresses before sending, and handles replies as drafts for review or automatic sends |
| Chrome extension | Findy finds contacts on LinkedIn, reveals their details, moves them into Reply lists and sequences, manages tasks, and places Cloud Calls |
| Organization | Workspaces for teams or clients, invited users, and roles at organization, team-wide, and workspace level. See [Permissions](/reference/permissions) |

## What Reply is not

- Not a CRM — Reply organizes contacts, accounts, and stages for outreach; keep pipeline and deals in your CRM and [sync it with Reply](/workflows/sync-reply-with-a-crm)
- Not a transactional email service — Reply sends outreach conversations, not receipts
- Not a data-only vendor — the database exists to feed execution, though you can save Reply Data contacts to lists without sequencing them

## Getting an account

Sign-up starts from **Try for free** on reply.io. On the account creation page you either
enter a work email and create a password, or sign up with Google or Microsoft; the manual
route also asks for a reCAPTCHA and acceptance of the Terms of Use and Privacy Policy.

A short registration form follows and has to be finished before the platform opens:
**Company → About You → Team → Outreach**, four steps on a trial account and three on a
paid one, which ends on the Team step. Every field is required, **Continue** stays disabled
until the current step is complete, there is no auto-save, and the form cannot be exited
part-way — leaving it means starting again. The Company step is skipped when Reply already
knows the company behind your domain. Finishing takes you to the Sequences page. Trial
scope and limits are listed in [When to use Reply](/start/when-to-use-reply).

Signing in afterwards happens at [Reply's login page](https://run.reply.io/login) with the
same three methods: email and password, Google, or Microsoft. **Forgot password** emails a
reset link. Organizations on Microsoft Entra SSO with a tenant lock are the exception — on
those domains Microsoft sign-in is the only available method, and password and Google
sign-in are unavailable. The Reply mobile app has its own login screen supporting the same
three methods.

## The four Reply properties

| Property | Question it answers |
| --- | --- |
| [reply.io](https://reply.io) | Why should a company use Reply? |
| **how.reply.io** (this site) | What can Reply do, and exactly how does it behave? |
| [docs.reply.io](https://docs.reply.io) | How does a developer call the API? |
| [agents.reply.io](https://agents.reply.io) | How does an AI agent connect and operate Reply? |

## Related

- [What can you build?](/start/what-can-you-build)
- [How Reply works](/start/how-reply-works)
- [When to use Reply](/start/when-to-use-reply)

## Build with Reply

- REST API: [docs.reply.io](https://docs.reply.io) · MCP, CLI, skills: [agents.reply.io](https://agents.reply.io)