Cold-email sequences
Build follow-up that runs on schedule and stops when someone replies.
Create multi-step email sequences with delays, personalization, reply-aware control, safe publishing, and a sending pool of authenticated business inboxes.
Email and delay steps·Stop on reply·Staged migration support
Sequence builder
Design the conversation before you enroll the audience.
Email steps
Write subject and body content, use approved contact variables, and keep a deterministic text version alongside supported visual email content.
Time-based delays
Place hour- or day-based delays between messages. Due enrollments advance on the scheduled engine cadence.
Reply-aware control
Stop an enrollment when an associated reply arrives, and use supported reply/no-reply conditions where the sequence needs a branch.
Manual or AI-assisted copy
Start from your own draft or use the AI credits included in your plan for generation, personalization, and rewrites, with human review before publication.
Safe publication
Validate the current sequence graph and content before atomically publishing it as the campaign's active version.
Sending-pool assignment
Select the connected inboxes eligible to carry the campaign and choose fair round-robin or random allocation.
Execution
Scheduled, idempotent, and recoverable.
MailSequence processes due enrollments in bounded batches. Send steps carry an idempotency key so a repeated execution does not silently send the same step twice.
- Active enrollments advance when their next step becomes due
- Duplicate-send protection for each inbox, contact, and step
- Transient failures defer work for a later retry
- Authentication failures remove the affected inbox from safe sending
Build or migrate
Start fresh or assess a campaign you already trust.
Create a new sequence
Build the steps, delays, content, audience, sending pool, and limits inside MailSequence, then publish after validation.
Transfer an existing sequence
Use your authorized Smartlead or Instantly API key for a compatibility check before transferring supported campaign structure, leads, or block-list records. Reconnect inboxes separately before launch.
Planning the sequence? Start with sequence structure, then choose how many follow-ups and their timing.
FAQ
Frequently asked questions
Which sequence steps are supported?
The shipped engine supports send-email, delay, and condition steps. Use reply and no-reply logic for branching; MailSequence does not market open- or click-based branching as shipped.
Will follow-ups stop after a reply?
Yes. When an inbound reply is associated with the enrollment and thread, MailSequence stops that enrollment and clears its next scheduled step.
Can a retry send the same step twice?
Send steps use an idempotency key tied to the inbox, contact, and step. If the corresponding message is already queued or sent, the engine does not create another send for that execution.
Can I transfer sequences from another platform?
For Smartlead and Instantly, first verify the records exposed by the current source API. Transfer only the supported structure and reconnect business inboxes separately before publishing.
Does MailSequence track opens and clicks?
MailSequence does not present campaign open or click tracking as a shipped capability. Evaluate campaigns with sends, replies, bounces, unsubscribes, and operational health.
Build sequences that earn useful replies.
Create or carefully transfer the first campaign, assign eligible inboxes, and publish after the audience and limits are ready.