# How Reply Works

> Canonical product documentation explaining what Reply can do, how Reply behaves, and what you can build with it — for humans and AI agents. how.reply.io explains what Reply can do, how the product behaves, and what can be built with it. docs.reply.io is the single source of truth for API reference detail; agents.reply.io covers MCP, CLI, and agent skills — this site links out to both rather than restating them.

Pages marked "Placeholder" are structural scaffolding with no verified content yet — do not treat them as documentation. Pages marked "Reviewed" are human-edited but not yet fact-checked against the product. Unmarked pages are verified.

## Machine entry points

- [Full site as one file](https://how.reply.io/llms-full.txt): every page concatenated
- [Page index](https://how.reply.io/search-index.json): title, description, and headings for every page
- [Capability matrix](https://how.reply.io/capabilities.json): flat can-do / cannot-do answers for tool selection
- [Canonical technical documentation](https://docs.reply.io): the single source of truth
- [Agent-facing surfaces](https://agents.reply.io/llms.txt): API, MCP, CLI, and Skills index

## Start

- [Introduction](https://how.reply.io/index.md): Understand Reply's capabilities, workflows, product specifications, and rules — and build prospecting, outbound, inbox, and AI SDR systems on top of it. (Reviewed)
- [Start here](https://how.reply.io/start.md): The orientation section — what Reply is, what you can build with it, when to use it, how it works, and the compact index built for AI agents. (Reviewed)
- [What is Reply?](https://how.reply.io/start/what-is-reply.md): Reply is a sales engagement platform — prospect data, contact management, multichannel outreach execution, reply handling, deliverability, analytics, and an AI SDR. (Reviewed)
- [What can you build?](https://how.reply.io/start/what-can-you-build.md): Systems Reply can power — an AI SDR, a prospecting agent, an outbound campaign generator, a sales inbox assistant, CRM outreach extensions, and internal outbound tools. (Reviewed)
- [When to use Reply](https://how.reply.io/start/when-to-use-reply.md): The honest fit test — use Reply when you need prospect data plus outreach execution with state management; look elsewhere for transactional email or CRM-grade pipeline. (Reviewed)
- [How Reply works](https://how.reply.io/start/how-reply-works.md): The system-level flow — prospect data becomes contacts and lists, sequences execute through accounts on schedules, replies land in the inbox, analytics closes the loop. (Reviewed)
- [Product map](https://how.reply.io/start/product-map.md): Every Reply module in one view — data, outreach, execution, conversation, AI, intelligence, and platform layers, each linked to where it is documented on this site. (Reviewed)
- [Core concepts](https://how.reply.io/learn.md): How outbound actually works — deliverability, sender reputation, sequencing, and AI SDRs explained as mechanisms, independent of any product. (Reviewed)
- [Email deliverability](https://how.reply.io/learn/email-deliverability.md): The mechanism that decides whether an email lands in the inbox, the spam folder, or nowhere — filtering signals, placement, and what senders control. (Reviewed)
- [Sender reputation](https://how.reply.io/learn/sender-reputation.md): The running score mailbox providers keep on every sending domain, mailbox, and IP — what feeds it, how fast it moves, and how it is repaired. (Reviewed)
- [Email warm-up](https://how.reply.io/learn/email-warm-up.md): The gradual ramp that teaches mailbox providers to trust a new sender — ramp curves, engagement simulation, and the maintenance floor that follows. (Reviewed)
- [SPF, DKIM, DMARC](https://how.reply.io/learn/spf-dkim-dmarc.md): What each email authentication record verifies, how DMARC alignment ties them to the From domain, and the failure modes that break them. (Reviewed)
- [Sequence design](https://how.reply.io/learn/sequence-design.md): Cadence mechanics for outbound — touch counts, spacing, diminishing returns, and why a sequence that reacts to replies beats a fixed drip campaign. (Reviewed)
- [Multichannel strategy](https://how.reply.io/learn/multichannel-strategy.md): Why layered channels outperform any single one — attention recapture, identity signals, and the orchestration rules that keep touches from colliding. (Reviewed)
- [The AI SDR model](https://how.reply.io/learn/ai-sdr-model.md): What an AI SDR automates and what it cannot — autonomy levels from drafts-for-approval to supervised autonomy, and the limits that keep humans in the loop. (Reviewed)
- [Reply classification](https://how.reply.io/learn/reply-classification.md): How incoming replies get sorted into intents, why natural language resists clean sorting, and what one misclassification costs an outreach system. (Reviewed)
- [Agent index](https://how.reply.io/start/agent-index.md): The compact map of Reply for AI agents — what the platform is, core capabilities and workflows, key rules, interface entry points, and every machine-readable file. (Reviewed)

## Capabilities

- [Capabilities](https://how.reply.io/capabilities.md): 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. (Reviewed)
- [Prospect search](https://how.reply.io/capabilities/prospect-search.md): Reply's Live Data search finds LinkedIn-sourced contacts by ICP filters or a pasted Sales Navigator URL, reveals emails and phone numbers for credits, and saves results to lists or sequences. (Reviewed)
- [Contact management](https://how.reply.io/capabilities/contact-management.md): Reply stores contacts and company accounts with custom fields, stages, lists, smart filters, blacklists, and CSV import and export — one shared base that every sequence works from. (Reviewed)
- [Data enrichment](https://how.reply.io/capabilities/data-enrichment.md): Reply finds missing LinkedIn URLs, emails, and phone numbers for existing contacts, refreshes profile fields, fills AI custom fields from prompts, and validates addresses before sending. (Reviewed)
- [Email outreach](https://how.reply.io/capabilities/email-outreach.md): Reply sends multi-step email sequences with A/B variants, variables and spintax, optional tracking, threaded follow-ups, three unsubscribe mechanisms, and throttled daily contact starts. (Reviewed)
- [LinkedIn outreach](https://how.reply.io/capabilities/linkedin-outreach.md): Reply automates nine LinkedIn action types — connections, messages, InMail, voice and AI voice messages, views, likes, endorsements, follows — under per-account safety limits. (Reviewed)
- [Multichannel outreach](https://how.reply.io/capabilities/multichannel-outreach.md): Reply mixes email, LinkedIn, call, SMS, WhatsApp, task, and Zapier steps in one sequence, branches on conditions, and compares channel performance in one dashboard. (Reviewed)
- [Calls and SMS](https://how.reply.io/capabilities/calls-and-sms.md): Reply places Cloud Calls through rented local numbers with recording, resolutions, and inbound transfer, and sends sequence SMS with pre-send phone validation and a dedicated SMS Inbox. (Reviewed)
- [Reply management](https://how.reply.io/capabilities/reply-management.md): Reply collects replies into one team Inbox, classifies each thread by AI into intent categories, pauses out-of-office contacts, and drafts or sends responses with Jason AI. (Reviewed)
- [Campaign analytics](https://how.reply.io/capabilities/campaign-analytics.md): Reply reports per-sequence, per-step, and per-variant metrics plus dashboards for emails, LinkedIn, calls, channel efficiency, team performance, and agencies, with CSV export and period comparison. (Reviewed)
- [Deliverability](https://how.reply.io/capabilities/deliverability.md): Reply layers MailToaster warm-up, default-on ramp-up, a weekly domain Health Checker, Postmaster spam monitoring, custom tracking domains, and AI template scoring around every send. (Reviewed)
- [AI SDR](https://how.reply.io/capabilities/ai-sdr.md): Jason AI generates offers and sequences from your website, sources contacts daily from ICP filters and intent signals, personalizes per prospect, handles replies, and books meetings. (Reviewed)
- [AI writing assistant](https://how.reply.io/capabilities/ai-writing-assistant.md): Jason AI as an in-editor writing assistant — generating a sequence from one prompt, writing and rewriting email steps from summaries or bullets, adjusting tone, length, and language on selected text, and drafting replies to prospects. (Reviewed)
- [AI chat assistant](https://how.reply.io/capabilities/ai-assistant.md): A natural-language agent inside Reply's new interface and Slack that executes account actions on request, confirms destructive and bulk changes, answers product questions from the help center, searches the web, and hands off to a human. (Reviewed)
- [Meetings](https://how.reply.io/capabilities/meetings.md): Reply books meetings through a personalized Google Calendar booking link with Google Meet or Zoom, or through a connected Calendly account, setting contacts to Meeting Booked and reporting bookings per channel. (Reviewed)
- [CRM and integrations](https://how.reply.io/capabilities/integrations.md): Reply syncs two-way with Salesforce, HubSpot, Pipedrive, and Copper, reaches thousands of apps through Zapier, Make, and n8n, serves AI agents over MCP, and emits real-time webhooks. (Reviewed)
- [Chrome extension](https://how.reply.io/capabilities/chrome-extension.md): The Reply Chrome extension finds emails on LinkedIn, LinkedIn Recruiter, Gmail, and CRM pages, pushes contacts into Reply lists and sequences, and executes call, SMS, WhatsApp, LinkedIn, and manual email tasks from the browser. (Reviewed)

## Workflows

- [Workflows](https://how.reply.io/workflows.md): Complete outcomes built on Reply — from finding prospects to booking meetings. Each workflow states what Reply provides, what you build, and every rule on the path. (Reviewed)
- [Build an AI SDR](https://how.reply.io/workflows/build-an-ai-sdr.md): The five-step Jason AI SDR wizard — business information, contact sources, personalization, generated steps, and launch settings — plus approval mode, reply handling, and meeting scheduling. (Reviewed)
- [Find prospects from an ICP](https://how.reply.io/workflows/find-prospects-from-an-icp.md): Turn ICP criteria into Realtime B2B Data filters, preview matches, launch a Live Search to a list or sequence, and track credits — plus Sales Navigator import and email validation. (Reviewed)
- [Build a prospect list](https://how.reply.io/workflows/build-a-prospect-list.md): Assemble a clean outreach list from CSV imports, search results, and manual adds — identifier-based dedup, import statuses, email validation, blacklisting, and list segmentation. (Reviewed)
- [Launch an outbound campaign](https://how.reply.io/workflows/launch-an-outbound-campaign.md): From connected mailbox to live sending — create the sequence, assign accounts and a schedule, set daily limits and delays, test with a real email, preview per recipient, and launch. (Reviewed)
- [Run multichannel outreach](https://how.reply.io/workflows/run-multichannel-outreach.md): Coordinate email, LinkedIn, call, SMS, and WhatsApp steps in one sequence — manual vs automatic per action, LinkedIn safety limits, Cloud Calls, and condition-based branching. (Reviewed)
- [Warm up new mailboxes and domains](https://how.reply.io/workflows/warm-up-new-mailboxes.md): The path from a fresh domain to full sending volume — DNS authentication first, MailToaster warm-up profiles and seats, then default-on ramp-up from 10 emails per day toward 100. (Reviewed)
- [Process positive replies](https://how.reply.io/workflows/process-positive-replies.md): From detected reply to booked meeting — inbox categories and triggers, AI reply handlers with Auto, Draft, and Stop and notify modes, canned responses, and per-channel meeting stats. (Reviewed)
- [Sync Reply with a CRM](https://how.reply.io/workflows/sync-reply-with-a-crm.md): Connect Salesforce, HubSpot, or Pipedrive — Default vs Custom profiles, sync steps with field, filter, and ownership mappings, pushing contacts to sequences, and the 2-hour sync cadence. (Reviewed)
- [Analyze campaign performance](https://how.reply.io/workflows/analyze-campaign-performance.md): Read the sequence Stats tab and the Reports dashboards — key prospect metrics, per-step detail, channel efficiency, Trends period comparison, smart filters, and CSV exports. (Reviewed)
- [Playbooks](https://how.reply.io/playbooks.md): Situation-anchored outreach recipes — each page maps one specific sales situation to targeting, sequence structure, message templates, expected results, and the steps that build it in Reply. (Reviewed)
- [Reactivate closed-lost pipeline](https://how.reply.io/playbooks/reactivate-closed-lost-pipeline.md): A play for deals lost 6–18 months ago to timing, budget, or a competitor — validate the aged list, segment by loss reason, reopen with what-changed messaging on Reply's default step delays, and close with a permission-style breakup. (Reviewed)
- [Outbound for seed-stage founders](https://how.reply.io/playbooks/outbound-for-seed-stage-founders.md): A play for founder-led outbound — a separate business sending domain warmed for 2–3 weeks, ramp-up from roughly 10–15 emails a day, a tight 50–100 account list, and founder-voice messages of about five sentences. (Reviewed)
- [Re-engage a cold contact database](https://how.reply.io/playbooks/re-engage-cold-database.md): A play for a CRM full of contacts untouched for a year or more — validate every address into Valid, Risky, or Invalid, keep Risky under 20% of the send, reopen with a permission-style message, and prune whoever stays silent. (Reviewed)
- [AI SDR for lean teams](https://how.reply.io/playbooks/ai-sdr-for-lean-teams.md): A play for one-to-three person GTM teams that want outbound running without an SDR hire — Jason AI in Approval mode, one Offer, one Playbook object, a knowledge base with Re-engagement follow-ups, and Autopilot held to its defaults. (Reviewed)
- [Book meetings from inbound signals](https://how.reply.io/playbooks/book-meetings-from-inbound-signals.md): A play for inbound signals going cold — Website Visitors tracking and the RB2B integration feed identified visitors straight into a sequence, the first line names what the person did, and a connected calendar puts the booking link in the email. (Reviewed)

## How to

- [How-to guides](https://how.reply.io/how-to.md): Product-interface instructions — connect accounts, import contacts, build and launch sequences, process replies. Steps describe actions, not button positions. (Reviewed)
- [Connect a mailbox](https://how.reply.io/how-to/connect-a-mailbox.md): Add a sending email account in Settings — single-click Gmail, Outlook, and Exchange connections, Autodiscover for on-premises Exchange, manual IMAP and SMTP setup, aliases, and the corporate-domain rule. (Reviewed)
- [Configure sending limits](https://how.reply.io/how-to/configure-sending-limits.md): Set the limit stack — the account's daily total and send delay, the sequence's Max number of emails per day and Max new daily contacts with its addition modes, and the same-domain cap. (Reviewed)
- [Import contacts](https://how.reply.io/how-to/import-contacts.md): Bring a CSV into Reply — file requirements, field mapping, the contact identifier, matched-records and no-email options, and the Imported, Updated, Skipped, and Import Errors results. (Reviewed)
- [Connect a LinkedIn account](https://how.reply.io/how-to/connect-linkedin.md): Connect LinkedIn to Reply by session cookie via the Findy extension, by credentials with an optional 2FA shared secret, or by an invite link for profiles you cannot log into. (Reviewed)
- [Set up DNS for sending](https://how.reply.io/how-to/set-up-dns.md): Configure MX, SPF, DKIM, and DMARC at your DNS host for any mail provider and registrar combination, then confirm the records with Reply's domain Health Checker. (Reviewed)
- [Configure account settings](https://how.reply.io/how-to/configure-account-settings.md): Where each account preference lives in Settings — the Account tab's personal details and Dark mode toggle, the three email notification reports, per-mailbox signatures, the Beta program, and where compliance and uptime information sits. (Reviewed)
- [Create a sequence](https://how.reply.io/how-to/create-a-sequence.md): Build a sequence in the Reply app — creation options, step types, delays, variables, A/B variants, and the Settings tab with accounts, schedule, and replies handling. (Reviewed)
- [Launch a sequence](https://how.reply.io/how-to/launch-a-sequence.md): Go live — check messages in Preview, send a test email, start the sequence with its toggle, read the toggle colors, and watch progress and logs in the first window. (Reviewed)
- [Edit a running sequence](https://how.reply.io/how-to/edit-a-running-sequence.md): What you can safely change on a live sequence and what you cannot — appending and deleting steps, switching to conditional, per-contact email edits, CC and BCC, custom opt-out links, clearing a Bounced status, and bulk actions across sequences. (Reviewed)
- [Filter contacts](https://how.reply.io/how-to/filter-contacts.md): Build smart filters on the People page — the property, condition, and value pattern, AND and OR logic, every filter dimension from time zone to LinkedIn connection status, and what you can do with the result. (Reviewed)
- [Manage duplicate contacts](https://how.reply.io/how-to/manage-duplicates.md): Prevent and clean up duplicates — the contact identifier key at import, matched-records choices, account import modes including Duplicate, and the contact handling settings. (Reviewed)
- [Process replies](https://how.reply.io/how-to/process-replies.md): The inbox routine — filter and correct AI-assigned categories, handle AI drafts, answer with canned responses, forward threads, and reply on behalf of teammates from one consolidated inbox. (Reviewed)
- [Read sequence reports](https://how.reply.io/how-to/analyze-campaign-performance.md): Where each number lives — the sequence Stats tab and its Brief and Detailed views, the Reports Emails dashboard, smart filters, and the CSV export options. (Reviewed)
- [Troubleshooting](https://how.reply.io/troubleshooting.md): Symptom-first diagnosis — why an email did not send, a contact was not enrolled, a campaign is not running, a reply was not detected, and more. (Reviewed)
- [Why was an email not sent?](https://how.reply.io/troubleshooting/email-was-not-sent.md): A due email did not go out — the four cause groups (account, limits, schedule, contact state), the Log tab as the error surface, and how to confirm the fix. (Reviewed)
- [Why is a campaign not running?](https://how.reply.io/troubleshooting/campaign-is-not-running.md): The sequence toggle is the diagnosis — what gray, red, orange, yellow, and blue mean, the 24-hour auto-stop for blocked accounts, and the 8% bounce suspension. (Reviewed)
- [Why was a mailbox disconnected?](https://how.reply.io/troubleshooting/mailbox-was-disconnected.md): An email account dropped its connection — expired connection tokens, revoked access, missing Gmail sending permission, and provider suspensions, with the reconnect path for each. (Reviewed)
- [Why LinkedIn steps fail](https://how.reply.io/troubleshooting/linkedin-steps-fail.md): Diagnosing stalled LinkedIn sequence steps — an expired session cookie, a lapsed Sales Navigator subscription, missing profile URLs, daily and weekly limits, unassigned contacts, and missing voice profiles. (Reviewed)
- [Why was a contact not enrolled?](https://how.reply.io/troubleshooting/contact-was-not-enrolled.md): A contact never made it into the sequence — import skips and errors, the Opted Out block, keep-in-sequence options, and the states that leave an enrolled contact idle. (Reviewed)
- [Why was a reply not detected?](https://how.reply.io/troubleshooting/reply-was-not-detected.md): A prospect answered but the contact still shows Active — the 3-4 hour window, the main-folder rule, same-address matching, and the direct-email divergence. (Reviewed)
- [Why do statistics not match?](https://how.reply.io/troubleshooting/statistics-do-not-match.md): Two reports disagree — denominator splits, the 7-day default filter, prospect-level counting, tracking gaps, and deletions that move the numbers. (Reviewed)

## Behavior

- [Behavior](https://how.reply.io/behavior.md): The deterministic logic Reply applies — what triggers each behavior, what changes as a result, and which exceptions exist. Each behavior is one page. (Reviewed)
- [How contacts enter a sequence](https://how.reply.io/behavior/contact-enrollment.md): The enrollment rule — the three add paths and their keep-in-sequence options, start-date scheduling, import requirements, and the pause-on-reply team settings. (Reviewed)
- [How Reply detects duplicate contacts](https://how.reply.io/behavior/contact-deduplication.md): The deduplication rule — the contact identifier chosen at import, update-vs-skip handling for matched records, and LinkedIn URL normalization across every source. (Reviewed)
- [How email validation works](https://how.reply.io/behavior/email-validation.md): How Reply classifies addresses as Valid, Risky, or Invalid — the disposable, catch-all, and honeypot signals, the syntax, DNS, and mailbox error taxonomy, and when validation runs. (Reviewed)
- [How a sequence executes](https://how.reply.io/behavior/sequence-execution.md): The execution rule — daily contact throttling, the 10,000-email cap, step delays that count weekends, task handling modes, and the same-domain limit. (Reviewed)
- [When Reply sends](https://how.reply.io/behavior/sending-schedules.md): The timing rule — schedule windows in UTC without DST, contact-timezone override, holiday calendars, daily contact capacity, and per-email delays. (Reviewed)
- [How Reply selects a sending mailbox](https://how.reply.io/behavior/mailbox-selection.md): The mailbox assignment rule — round-robin distribution across up to 100 accounts, follow-up thread continuity, provider matching, and reassignment on removal. (Reviewed)
- [How LinkedIn action limits work](https://how.reply.io/behavior/linkedin-limits.md): The daily caps Reply applies to automatic LinkedIn steps — dynamic ranges vs a static maximum, the nine action types, the 100-per-action ceiling, and what happens when a cap is hit. (Reviewed)
- [How Reply detects replies](https://how.reply.io/behavior/reply-detection.md): The reply-detection rule — the IMAP-monitored mailbox, the 3-4 hour detection window, same-address matching, forwarded emails, and which statuses a reply sets. (Reviewed)
- [What happens when an email bounces](https://how.reply.io/behavior/bounce-handling.md): The bounce rule — hard vs soft bounces, the 4% and 8% bounce-rate thresholds, the 200-email floor, and how a stopped step resumes the next day. (Reviewed)
- [When Reply stops a sequence](https://how.reply.io/behavior/sequence-stopping.md): Every condition that stops automated outreach — the six sequence toggle states, replies handling, blocked-account auto-stop, and the 8% bounce suspension. (Reviewed)
- [How statuses change](https://how.reply.io/behavior/status-transitions.md): The 14 contact statuses — when Reply assigns each one, which are user-settable, and the reconstructed transition rules including one-way and retained statuses. (Reviewed)
- [How statistics are calculated](https://how.reply.io/behavior/statistics-calculation.md): Every email-metric formula — Total people, Contacted, and the denominator split that puts delivery and bounce rates over Total but open and reply rates over Contacted. (Reviewed)

## Specifications

- [Specifications](https://how.reply.io/specifications.md): The authoritative definition of every Reply object — what it is, how it relates to other objects, its lifecycle, configuration, side effects, and edge cases. (Reviewed)
- [Contacts](https://how.reply.io/specifications/contacts.md): The specification of the Reply contact — one record per person with profile fields, custom fields, an email validation status, 14 sequence statuses, and a separate pipeline stage. Called People in the app. (Reviewed)
- [Companies](https://how.reply.io/specifications/companies.md): The specification of the Reply company record — Accounts in the app. How accounts group contacts, the eight account stages, account lists, CSV import modes, and filters. (Reviewed)
- [Lists](https://how.reply.io/specifications/lists.md): The specification of Reply lists — named collections of contacts or accounts for segmentation and team sharing, and how lists differ from filters and the blacklist. (Reviewed)
- [Prospect data](https://how.reply.io/specifications/prospect-data.md): The specification of Reply's data services — Realtime B2B Data search, contact enrichment, AI custom field enrichment, and email validation, with the Reply credit cost of each. (Reviewed)
- [Sequences](https://how.reply.io/specifications/sequences.md): The authoritative specification of the Reply sequence — ordered outreach steps, enrolled contacts, up to 100 sending accounts, the General and Replies settings, and the six toggle states. Formerly called a campaign. (Reviewed)
- [Sequence steps](https://how.reply.io/specifications/sequence-steps.md): The specification of sequence steps — email, LinkedIn, call, SMS, WhatsApp, task, condition, and Zapier actions, with A/B variants, step delays, and manual or automatic task handling. (Reviewed)
- [Campaigns](https://how.reply.io/specifications/campaigns.md): Campaign is the former name of what Reply now calls a sequence. This page explains where the old name survives and routes to the sequence specification. (Reviewed)
- [Email accounts](https://how.reply.io/specifications/email-accounts.md): The specification of Reply email accounts (mailboxes) — plan-based allowances, connection methods from single-click to CSV bulk import, per-account delays, DNS health checks, opt-out settings, and MailToaster warm-up. (Reviewed)
- [Schedules](https://how.reply.io/specifications/schedules.md): The specification of Reply schedules — weekly sending windows in UTC with no DST adjustment, contact-timezone sending, national holiday calendars, defaults, and changing the schedule of an active sequence. (Reviewed)
- [Tasks](https://how.reply.io/specifications/tasks.md): The specification of Reply tasks — task types and subtypes, sequence-generated vs manually created tasks, manual and automatic handling modes, Tasks page filters and bulk actions, Chrome Extension execution, and what the task object leaves undocumented. (Reviewed)
- [Templates and variables](https://how.reply.io/specifications/templates-and-variables.md): The specification of Reply message templates and personalization variables — the contact, team, custom, advanced, and AI variable types with their syntax, Spintax randomization, template folders and sharing, and the HTML-editor rules for images, fonts, and hyperlinked custom fields. (Reviewed)
- [Conversations](https://how.reply.io/specifications/conversations.md): The specification of Reply conversations — message threads with one contact across email and LinkedIn, their participants, CC handling, threading rules, and outside-email sync. (Reviewed)
- [Inbox](https://how.reply.io/specifications/inbox.md): The specification of the Reply Inbox — the consolidated view over all threads, with main and inbox categories, filters, search, unread state, and auto-reply handling. (Reviewed)
- [Knowledge bases](https://how.reply.io/specifications/knowledge-bases.md): The specification of the Jason AI knowledge base — product information added as text, documents (100 MB per file), and links, plus Reply Handling with Auto, Draft, and Stop & notify modes and Re-engagement follow-ups. (Reviewed)
- [Offers](https://how.reply.io/specifications/offers.md): The specification of Jason AI offers — audience-specific positioning built from an ICP, pain points, value propositions, proof points, and case studies; five are generated per new sequence, with an Update original vs Keep separate edit flow. (Reviewed)
- [Playbook (Jason AI object)](https://how.reply.io/specifications/playbooks.md): The specification of the Jason AI playbook — the message-generation prompt with Do and Don't instructions, step-specific sections, step attachments, and the AI-generated playbook Jason builds from your offer. (Reviewed)
- [Workspaces and roles](https://how.reply.io/specifications/workspaces-and-roles.md): The specification of Reply's organization structure — how an organization contains workspaces and users, the permanent organization-owner rules, the three role levels, Team Edition Public and Private modes, and the seat types that gate access to mailboxes, LinkedIn, and calls. (Reviewed)
- [Triggers](https://how.reply.io/specifications/triggers.md): The specification of Reply triggers — the built-in When/If/Then automations in Settings, the full catalog of trigger events with their available actions, the conditions that narrow them, and how they behave in Team Edition. (Reviewed)

## Reference

- [Reference](https://how.reply.io/reference.md): Exact values and lookup tables — terminology, entity relationships, statuses, permissions, limits, and calculations. Compact pages built for retrieval, not reading order. (Reviewed)
- [Terminology](https://how.reply.io/reference/terminology.md): The canonical name for every Reply object, the synonyms you will meet in the app and the API, and the one-line definition of each. (Reviewed)
- [A–Z index](https://how.reply.io/reference/a-z.md): Every page and every registered entity on this site, alphabetically — pages, objects, and the synonyms that point at them. (Reviewed)
- [Entity relationships](https://how.reply.io/reference/entity-relationships.md): Which Reply object contains, uses, or references which — the organization containment chain, the outreach object graph, and the ownership rules that move data between them. (Reviewed)
- [Lifecycle diagrams](https://how.reply.io/reference/lifecycle-diagrams.md): The contact status, sequence toggle, and email validation lifecycles as machine-readable text diagrams, each with a table of the events that trigger every transition. (Reviewed)
- [Statuses](https://how.reply.io/reference/statuses.md): Every status family in Reply with exact values — the 14 contact statuses, contact and account stages, sequence toggle colors, email validation results, and inbox categories. (Reviewed)
- [Permissions and roles](https://how.reply.io/reference/permissions.md): Reply's three-tier role model — organization, team-wide, and workspace roles — with the organization-level permission list, workspace permission categories, and the seat types behind resource access. (Reviewed)
- [Limits](https://how.reply.io/reference/limits.md): Every documented Reply limit in one place — sending caps, contact storage, API rate limits, LinkedIn action limits, and the fair-usage mailbox scale. (Reviewed)
- [Calculations](https://how.reply.io/reference/calculations.md): The exact formula behind every Reply email metric — Total people, Contacted, delivery, open, reply, bounce, and opt-out rates — plus tracking mechanics and both CSV export field dictionaries. (Reviewed)
- [API limits and webhooks](https://how.reply.io/reference/api-limits.md): Reference for Reply's API rate limits — the 15,000-call monthly quota, per-team-member allocation, and 10-second call interval — plus the V2 vs V3 webhook generations, event types, subscription scopes, and payload options. (Reviewed)