Concepts

Sequences

A sequence is a series of emails sent from one of your connected Gmail mailboxes to the rows of a table. Step 1 starts the thread; each follow-up replies in that same thread, a few days later.

Docs menu

Nothing is sent until the sequence is started. Your agent shows you a preview and the enrollment counts first, and starts only after you approve.

Lifecycle

Every sequence moves through the same five steps. Each one is a single MCP tool, so you can drive it by asking your agent or call the tools yourself.

Once started, sequence_stats shows emails sent, the reply rate and where every lead is. Pause before changing the steps of a running sequence.

Steps

A sequence has 1 to 10 steps. Bodies are plain text, and any {{column_key}} is filled in from the lead's row (columns as variables).

Field	What it does
subject	Only on step 1, where it's required. Follow-ups reply in the same thread as “Re: ” plus that subject.
body	Plain text with variables, e.g. `{{first_name}}`. An unsubscribe line is added automatically.
delay_days	Days after the previous step, 0 to 60. Defaults to 3.

steps.json

[
  { "subject": "Quick question, {{first_name}}",
    "body": "Hi {{first_name}}, ..." },
  { "delay_days": 3, "body": "One thing I left out: ..." },
  { "delay_days": 4, "body": "I'll stop here so I don't crowd your inbox." }
]

Sending from several mailboxes

A sequence sends from a pool of one or more of your mailboxes. Each lead is assigned one mailbox when you enroll them, and every step goes out from it, in the same thread. More mailboxes means more emails a day, without pushing any single inbox past a safe volume.

Assignment	How leads are spread
capacity	The default. Each lead goes to the mailbox with the most room today, so a mailbox still ramping up gets fewer.
even	Each mailbox gets the same number of leads.

Mailboxes that need reconnecting get no new leads, and their leads wait while the rest keep sending. Change the pool any time, from the sequence's Edit pool button or with update_sequence: leads that haven't been emailed yet move to the new pool, and leads already mid-thread stay on their mailbox.

When emails go out

Send window

9:00–17:00

Monday to Friday, in the recipients' timezone. Set window_start_hour and window_end_hour.

Timezone

Europe/Madrid

The default. Pass any IANA timezone, e.g. America/New_York.

Daily limit

Per mailbox

Each mailbox's own limit, ramp and spacing apply. Mailboxes.

Emails due outside the window wait for the next opening and go out spread over its first half hour. Every email carries an unsubscribe link and Gmail's one-click unsubscribe header.

Who gets skipped

Enrolling never sends anything. enroll_rows skips, and counts, any row that has:

No email
An email marked undeliverable (what about probable ones?)
An address that unsubscribed or bounced before
A variable the steps use but the row doesn't have
Already been enrolled

When it stops for a lead

They reply

Every sequence stops for that address, the reply lands in Replies and the lead moves to the replied stage.

They unsubscribe or bounce

Every sequence in your workspace stops for that address, and it's skipped from then on.

Out-of-office replies are recorded but don't stop the sequence.

Ask your agent

In Claude Code

› Write a 3-step sequence for the Fintech CTOs table from all my healthy mailboxes, show me the preview for the first lead, then enroll everyone with a verified email.

Or use /mcp__meerko__write-sequence, which drafts the steps and shows you previews without enrolling anyone.

PreviousMailboxes Next Replies & drafts