API docsAgent tools

Understand

How Reply works

Overview Reviewed · not yet fact-checked

In short

How does Reply work?

Prospect data from Reply Data search, CSV imports, Findy, or CRM integrations becomes deduplicated contacts and lists; sequences combine email, LinkedIn, call, SMS, WhatsApp, task, Zapier, and condition steps; execution runs through connected mailboxes inside schedules and limits; replies land in the consolidated inbox with AI-assigned categories; Stats and Reports close the loop. Jason AI drives the same machine.

The flow

Prospect data          Reply Data live search · CSV import · Findy extension
      │                CRM integrations · manual entry
      ▼
Contacts and lists     deduplicated by the import identifier · accounts (companies)
      │                stages · custom fields · lists
      ▼
Sequences              email / LinkedIn / call / SMS / WhatsApp / task / Zapier /
      │                condition steps · A/B variants · variables
      │                (built from template, scratch, AI prompt, or Jason AI SDR)
      ▼
Execution              connected email + LinkedIn accounts · schedules · daily limits
      │                MailToaster warm-up · plain-text default · tracking toggles
      ▼
Replies and inbox      reply detection · stopping · AI-assigned categories · AI drafts
      │
      ▼
Analytics              sequence Stats · Reports dashboards (Emails, LinkedIn, Calls,
      │                Tasks, Team Performance, Channel Efficiency, Agency, Trends)
      └──────────────► iterate: fix the ICP, the copy, or the timing

Each stage in one sentence

  1. Prospect data — Live Data search finds contacts from LinkedIn data by your filters, enrichment and email verification fill gaps, and CSV imports (UTF-8, up to 10,000 rows per file) bring your own records.
  2. Contacts and lists — every import row deduplicates on the contact identifier you choose (Email, Last Name, or Phone) into one base, segmented by lists and grouped into accounts.
  3. Sequences — steps define what happens across channels, with A/B variants and per-step delays; enrollment decides who it happens to.
  4. Execution — sequence execution walks contacts through steps inside schedules and limits (400 emails per account per day on paid plans), selecting accounts per the mailbox rule.
  5. Replies — detection stops the contact and routes the conversation to the consolidated inbox, where reply management applies AI-assigned categories and Jason AI can draft answers.
  6. Analytics — the sequence Stats tab counts key metrics per prospect (a contact counts once across steps), and the Reports dashboards break performance down by channel and team on shared definitions.

Where the AI SDR sits

Jason AI is not a separate pipeline — it drives this same machine: it defines the ICP from your website, finds contacts in real time, generates the multichannel sequence, personalizes each message, adds new contacts daily on Autopilot, and handles replies as drafts for review or automatic sends — with approval wherever you keep humans in the loop.

Build with Reply