Sequences
Every email leaves from your rep's own mailbox, not from a platform address.
Connect Gmail or Microsoft 365 in one click over OAuth, or point at any SMTP and IMAP server. Sequence emails then send from that mailbox, with that reputation, and replies thread back onto the deal. Credentials are encrypted at rest and inbound mail is polled every minute.
Sequences are on by default, from the Starter plan up — there is no switch to ask for. Connect a mailbox and build a cadence; a custom sending domain is the one piece that stays opt-in.
Sign-up opens when the app launches. We will email you once — no marketing list.
Deliverability
Failing closed beats sending.
Every rep sends from their own mailbox by default — nothing to configure. Verify a custom sending domain and Oneop adds self-managed DKIM on top: an RSA-2048 key pair generated for you, the private key encrypted at rest and never returned by the API.
The rule either way: an unverified domain or a failed DKIM signature blocks the send, it does not go out unsigned. The lease releases and retries on the next tick, so sending resumes by itself once verification completes.
Alongside it: a per-sequence hourly throttle, a daily send cap, optional ramp-up from a low starting number, and send windows evaluated in your own timezone — a step due outside the window is rescheduled to the next opening, never fired late.
The limits
What sequences do.
- Real branches
- Reads replied, opened, clicked, meeting booked — and their negatives.
- Deterministic A/B
- 2–8 weighted variants, locked per recipient by seed.
- Own-mailbox sending
- Gmail, Microsoft 365 or any SMTP/IMAP — never a shared pool.
- Fail-closed signing
- Custom-domain sends are DKIM-verified or blocked — never unsigned.
- Auto exit on reply
- Also on bounce, unsubscribe, click, meeting booked, or deal stage change.
Getting started
Three steps. None of them is "wait for us to flip a switch."
Connect a mailbox
Gmail or Microsoft 365 over OAuth, or any SMTP/IMAP server. This is the only real precondition — a sequence has nowhere to send from until a rep does this.Build a cadence
Already on for your plan. Add steps, a branch, and A/B variants, then enroll contacts or deals — nothing to request first.Verify a domain — optional
Want cold outreach to leave from your own domain with self-managed DKIM instead of your mailbox's default signing? That layer stays a separate, opt-in switch.
What it costs
Sequences run on every plan from Starter up. What scales with the plan is how many can run at once, not whether the feature exists.
| Capability | Free $0 | Starter $19 | Pro $59 | Business $129 |
|---|---|---|---|---|
| Sequences | — | ✓ | ✓ | ✓ |
| Connect your own mailbox | ✓ | ✓ | ✓ | ✓ |
Annual billing is two months free; extra seats are $5 per seat per month. These are plan limits published as plan limits — see pricing for the current ladder, generated from the product's own plan catalogue.
See full pricingFrequently asked
Whose mailbox do sequence emails actually come from?
Each rep’s own. Gmail and Microsoft 365 connect over OAuth using XOAUTH2, and any other provider connects over SMTP and IMAP with credentials encrypted at rest. The mail leaves from that mailbox, with that sending history, and replies poll back in every minute and thread onto the deal.
Do I have to ask for sequences to be turned on?
No. Sequences are on by default in every workspace, from the Starter plan up — there is nothing to enable. The only thing that has to happen first is a rep connecting their own mailbox, because a sequence with nowhere to send from has nothing to do.
What happens if my sending domain isn’t verified?
The send is blocked. Not sent from a fallback address, not sent unsigned — blocked, with the reason written onto the enrollment and an automatic retry on the next tick, so sends resume by themselves once verification completes. The same applies if the domain is verified but the mailbox has no SMTP credentials to DKIM-sign with. There is no code path that sends unauthenticated cold email. Note this only applies if you have turned on a custom sending domain in the first place — that layer is a separate, opt-in switch, and most workspaces never need it.
Can a sequence send at 3am or on a Sunday?
Only if you let it. A sequence carries allowed weekdays, a start and end time, and the timezone those are read in. A step that comes due outside the window is rescheduled to the next window opening rather than fired. You can also cap daily sends per sequence and ramp up from a low starting number over the first days.
Does it stop when someone replies?
Yes — a reply exits the prospect automatically, and bounces and unsubscribes exit through suppression. You can also exit on click, on a booked meeting, or on a deal stage change. One limit we will state rather than let you discover: automatic reply detection runs from the Postmark inbound webhook, not from the per-user IMAP sync.
Is the A/B testing real, or just two subject lines?
Real. Two to eight weighted variants per email step, with the variant chosen deterministically from a per-enrollment seed — so the same recipient always receives the same variant and a retry re-sends the identical one. Attribution is recorded on the send.
Connect a mailbox. Sequences are already on.
No request, no waiting on us. Build a cadence with real branches and A/B tests, sending from the mailbox your reps already use.
Sign-up opens when the app launches. We will email you once — no marketing list.