# Specifications

> The authoritative definition of every Reply object — what it is, how it relates to other objects, its lifecycle, configuration, side effects, and edge cases.

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

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](/specifications/contacts) — one record per person, with statuses, stages, and custom fields
- [Companies](/specifications/companies) — organizations grouping their contacts; Accounts in the app
- [Lists](/specifications/lists) — named collections of contacts or accounts for segmentation
- [Prospect data](/specifications/prospect-data) — Realtime B2B Data search, enrichment, and email validation

## Outreach objects

- [Sequences](/specifications/sequences) — the unit of execution (formerly "campaigns")
- [Sequence steps](/specifications/sequence-steps) — email, LinkedIn, call, SMS, WhatsApp, task, condition
- [Campaigns](/specifications/campaigns) — the legacy name, and where it survives
- [Email accounts](/specifications/email-accounts) — sending identities (mailboxes)
- [Schedules](/specifications/schedules) — when sending is allowed

## Conversation objects

- [Conversations](/specifications/conversations) — the message history with one contact
- [Inbox](/specifications/inbox) — workspace triage over all conversations

## Jason AI objects

- [Knowledge bases](/specifications/knowledge-bases) — sources and reply handlers that ground AI replies
- [Offers](/specifications/offers) — what you sell, as Jason AI's input
- [Playbooks](/specifications/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](/behavior) — the deterministic logic that moves these objects
- [Entity relationships](/reference/entity-relationships) — the full object graph
- [Statuses](/reference/statuses) — every enum value

## Build with Reply

- REST API: [docs.reply.io](https://docs.reply.io/api-reference/introduction) — each object maps to an endpoint group
- MCP: [agents.reply.io/mcp](https://agents.reply.io/mcp) · CLI: [agents.reply.io/cli](https://agents.reply.io/cli)