Overview
The deterministic logic Reply applies: what triggers each behavior, what changes as a result, and which exceptions exist. Each behavior is one page.
Behavior pages answer the questions agents and operators actually ask mid-build: what stops a sequence? which mailbox sends this email? what happens after a bounce? Every behavior page states its trigger, decision logic, result, state changes, and exceptions ( grounded in Reply's product documentation, with exact thresholds, setting names, and status enums) so behavior is predictable before you rely on it.
Enrollment and data
How contacts enter a sequence
enrollment paths, checks, and conflicts
How Reply detects duplicate contacts
the identifier key, and import handling
Execution and sending
How a sequence executes
step order, delays, limits, health
When Reply sends
schedule windows meet delays and budgets
How Reply selects a sending mailbox
distribution across assigned accounts
Replies and state
How Reply detects replies
matching, classification, stopping
What happens when an email bounces
bounce state and protection
When Reply stops a sequence
every stop condition in one place
How statuses change
the transition matrix
How statistics are calculated
counters and denominators
Planned
| Page | Status |
|---|---|
| Step execution detail | Not written |
| Daily sending limits (cross-object precedence) | Not written |
| Automatic-reply detection | Not written |
| Unsubscribe handling | Not written |
| Conversation matching | Not written |
| Task generation | Not written |
| Credit consumption | Not written |
Related
- Specifications – the objects these rules move
- Troubleshooting – when observed behavior doesn't match a rule
Build with Reply
- REST API: docs.reply.io – the operations that trigger these rules