Overview
The authoritative definition of every Reply object: what it is, how it relates to other objects, its lifecycle, configuration, side effects, and edge cases.
A specification page is the canonical explanation of one product object. Capabilities say what Reply can do; specifications say what the objects are. Every page follows the same skeleton (definition, relationships, lifecycle, configuration, behavior, limits, edge cases) so any section can be retrieved on its own.
Data objects
Contacts
one record per person, with statuses, stages, and custom fields
Companies
organizations grouping their contacts; Accounts in the app
Lists
named collections of contacts or accounts for segmentation
Prospect data
Realtime B2B Data search, enrichment, and email validation
Outreach objects
Sequences
the unit of execution (formerly "campaigns")
Sequence steps
email, LinkedIn, call, SMS, WhatsApp, task, condition
Campaigns
the legacy name, and where it survives
Email accounts
sending identities (mailboxes)
Schedules
when sending is allowed
Conversation objects
Jason AI objects
Knowledge bases
sources and reply handlers that ground AI replies
Offers
what you sell, as Jason AI's input
Playbooks
reusable outreach strategies
Planned
| Page | Status |
|---|---|
| Workspaces, users, teams | Not written |
| Tasks | Not written |
| Calls · Meetings | Not written |
| Messages | Not written |
| Integrations | Not written |
| Subscriptions · Credits | Not written |
Related
- Behavior – the deterministic logic that moves these objects
- Entity relationships – the full object graph
- Statuses – every enum value
Build with Reply
- REST API: docs.reply.io – each object maps to an endpoint group
- MCP: agents.reply.io/mcp · CLI: agents.reply.io/cli