Building a sequence
A filtered list of contacts. Sequences run against a list, not against a stage.
Each step is a message and a wait. Three to five steps is where most of the response is.
A reply always stops it. A booked meeting and an unsubscribe stop it too.
Business hours in the recipient's timezone, and a daily cap.
Replies land in the shared inbox, not in a personal mailbox.
Q2 introduction
120 enrolled · running · stops on reply
| Step | Wait | Sent | Replied | Rate |
|---|---|---|---|---|
| 1 · Introduction | — | 120 | 7 | 5.8% |
| 2 · Case study | 3 days | 108 | 4 | 3.7% |
| 3 · Direct ask | 4 days | 96 | 6 | 6.3% |
| 4 · Break-up | 7 days | 61 | 2 | 3.3% |
Deliverability
Sequences send from your domain, authenticated with DNS records that we verify before switching sending on. That verification step is not bureaucracy: a partially authenticated domain does not bounce, it delivers to spam or is accepted and dropped, and the symptom is a campaign that appears to send perfectly and produces nothing.
- Warm a new sending domain gradually. A cold domain sending 500 messages on day one is a domain with a reputation problem by day three.
- Use a subdomain for outreach so a bad campaign cannot damage your primary mail.
- Every sequence message carries an unsubscribe path. That is not optional and cannot be turned off.
- An unsubscribe is honoured across the whole workspace, not just the sequence it came from.
Unsubscribes apply at the mail-provider account level. If a contact who is also a user unsubscribes, later transactional mail to that address — including their sign-in link — is accepted and silently dropped. The symptom is a person who cannot sign in while our logs show the mail sent. Mail [email protected] with the address to clear it.
SMS and voice
The code paths exist, are deployed, and are wired to a carrier. The carrier account they sit on cannot place outbound calls or send SMS, so nothing goes out. This page is marked In progress for that reason. Do not design a campaign around either channel until it is confirmed live — and note that outbound voice in particular carries consent and disclosure obligations that differ by jurisdiction.
Inbound voice is a different thing entirely and does work — that is Phony, which answers calls rather than placing them.
What this does not do
A sequence has one version of each step.
Email only among live channels.
Windows and caps are set by you, not learned.
Built, deployed, carrier-blocked.
Suppression is per workspace.
Questions
Does a reply stop every sequence a contact is in?
It stops the one they replied to. Enrolling one person in several sequences is worth avoiding for that reason.
Can we send from a personal mailbox?
Sequences send from the authenticated workspace domain. Individual email sync is separate.
How many can we send a day?
You set a cap. Set it low on a new domain.
Related
Where replies land in erp.io CRM, how they are assigned and answered, and why a shared inbox beats forwarding to individuals.
PhonyVoice and chat agents in erp.io that answer, qualify and hand off — how they are built, what they know, and the outbound calling this product deliberately will not do.