Replies, analytics, AI

Capability Reviewed · not yet fact-checked

At a glance

Summary

Jason AI is Reply's AI SDR. Point it at your website (or upload files, or paste text) and it derives your ICP, pain points, value propositions, proof points, case studies, and CTAs, packages them into offers, and generates a multichannel sequence shaped by a playbook. It sources its own audience daily from ICP filters and buying-intent signals, writes a unique message per contact, classifies and answers replies from a knowledge base, re-engages leads that go quiet, and books meetings — with a human approving each message, or fully automatic. The model is explained in The AI SDR model.

Problems it solves

• Sequence strategy and copywriting from a standing start — offers, structure, and messages generated, not templated
• Continuous prospecting without manual list refills, with per-source tags on every contact
• Reply handling at speed, grounded in your material, with per-question-type control over automation
• Prioritization: ICP and LinkedIn Activity scores show who fits and which channel to lead with

What Reply can do

• Generate business context from a website URL, uploaded PDF or text files (up to 100 MB), or pasted text — company description, ICP, pain points, value propositions, proof points, case studies, and CTAs, all editable
• Auto-generate 5 offers per sequence creation — different angles on the same product by ICP and pain points — and update an offer in place or fork it per sequence
• Generate sequences shaped by a playbook (do's and don'ts, per-step instructions, subject-line rules, call scripts), in a chosen language, tone of voice, and message length
• Source contacts continuously via Autopilot — Sales-Navigator-style ICP filters or a pasted Sales Navigator URL — at up to 500 new contacts per day per sequence (default 10), 3 contacts per company
• Add contacts from buying-intent signals: job hiring, technology used, company or department growth, changed jobs in 90 days, LinkedIn post engagers (up to 50 likers plus 50 commenters per post), and competitor followers scanned daily — filtered by ICP fit (default 60%)
• Mix in AI web search, website-visitor tracking, and manual sources (CSV, existing contacts, LinkedIn search), tagging every contact with its source in the activity log
• Write a unique message per contact by rotating your pain points, value propositions, case studies, and CTAs and researching public data — recent news, the contact's LinkedIn activity from the past 3 months, the company page and website — with a template fallback when nothing is found
• Score every contact per sequence: an ICP score with hover explanations and a LinkedIn Activity score (Frequent, Consistent, Occasional), both usable as filters
• Run in approval mode — every generated message waits on the Pending approvals page where you edit, regenerate with a prompt, approve singly or in bulk, or delete — or in automatic mode with no review
• Handle replies from the knowledge base with per-question-type reply handlers (Auto, Draft, or Stop and notify) and re-engage silent leads with timed follow-up cards
• Learn your writing style from likes, dislikes, and edits (AI Learnings) — rules you can view, edit, enable, or add to
• Generate up to 15 ready-to-launch sequence ideas per AI Strategist run — each with its own audience, offer, playbook, and pre-filled Autopilot filters

What Reply cannot do

• Know your business without inputs — offer, playbook, and knowledge base quality bound output quality
• Send a message in approval mode without human approval — and throughput is bounded by review speed
• Score contacts globally — ICP scores are computed per sequence and offer, so the same contact can score differently in different sequences
• Exceed source caps: 500 contacts per day per sequence, 3 per company, 500 per one-time intent search, 50 likers plus 50 commenters per post
• Generate AI replies for threads categorized Do not contact
• Replace your qualification bar — approval mode and ICP-score filters exist precisely for that

Required inputs

A website URL, files, or pasted text to generate the offer from; connected sending accounts (email, LinkedIn) for the generated channels; optionally a playbook, knowledge base, tone and language settings, and intent-signal configuration.

Produced outputs

Generated offers, playbooks (via AI Strategist), and sequences; a daily stream of sourced, scored, source-tagged contacts; personalized sent messages; classified replies with drafts or automatic answers; re-engagement follow-ups; booked meetings.

Use Reply when

• You want the whole loop — find, write, send, respond, book — in one system with human approval available at each stage; see Build an AI SDR
• Your team is small and list building is the bottleneck — intent signals and Autopilot keep sequences fed
• You want messaging variation per contact without hand-writing hundreds of emails

Do not use Reply when

• You are building your own agent orchestration and only need primitives — use the API, MCP, and CLI directly; Jason AI and your agent can share the same workspace
• Your channel mix is dominated by channels Jason does not generate — calls-only or SMS-only motions are better built as regular multichannel sequences

What you still need to build

• The substance of the offer — pain points and proof that are actually true; generation amplifies inputs, it does not invent credibility
• Your qualification and escalation rules: ICP-score thresholds, which reply types stay human, when to loosen approval mode

capability: ai_sdr
supported: true
interfaces:
  product_ui: live
  api: partial
  mcp: live
  cli: not-verified
required_objects:
  - offer
  - sequence
side_effects:
  - creates_sequences
  - sources_contacts
  - sends_messages
  - sends_replies
human_approval_recommended: true

Limits

• Autopilot: up to 500 new contacts per day per sequence, default 10 per day, 3 contacts per company
• One-time intent searches (hiring intent, technology used, competitor followers): up to 500 contacts per search, re-runnable after launch
• LinkedIn post engagers: up to 50 likers and 50 commenters per post; ICP fit threshold defaults to 60%
• Knowledge base and offer uploads: PDF, DOC, DOCX up to 100 MB per file; links added one at a time
• AI Strategist: up to 15 sequences per run; 30–60 minutes per run; monthly run allowance depends on your AI SDR plan
• Sends inherit all email and LinkedIn limits — see Limits and Sending schedules

FAQ

Does a human approve messages before they send?

Your choice per sequence. In approval mode every generated message waits on the Pending approvals page — edit, regenerate with a short prompt, approve one by one or in bulk, or delete (which removes the prospect from the sequence). In automatic mode Jason sends without review. Approved messages still respect the sequence's schedule and limits.

What grounds Jason AI's reply answers?

Your knowledge base (text, documents, links) plus reply handlers — per-question-type instructions with a delivery mode of Auto, Draft, or Stop and notify. Jason answers the most recent message in a thread, never Do-not-contact threads, and books meetings on Meeting-intent replies via your connected calendar or booking link. See Reply management and Reply detection.

How does Jason personalize each message?

It combines your business context — rotating one pain point, value proposition, case study, and CTA per message — with public contact research: recent news, the contact's LinkedIn posts and comments from the past 3 months, and the company's page and website. When no relevant information is found, a default template keeps the sequence moving.

What are the ICP and LinkedIn Activity scores?

Per-sequence columns in the AI SDR People tab. The ICP score measures fit against the sequence's offer — the same contact can score differently in different sequences — with hover explanations. LinkedIn Activity (Frequent, Consistent, Occasional) suggests which channel to lead with. Both work as filters, for example removing contacts scoring under 60.

Related

• Build an AI SDR — the full workflow
• Offers · Playbooks · Knowledge bases
• The AI SDR model
• Contact enrollment
• Reply management · Prospect search

Build with Reply

• REST API: docs.reply.io — ai-sdr endpoint group (check operation status)
• MCP: agents.reply.io/mcp — offers, playbooks, knowledge bases, approvals, and sequence generation
• Agent workflows: agents.reply.io/workflows