ProductSequences

Paced like a person. Threaded like a conversation.

Build email and call steps once. PEMAX sends each email from the rep's own Google Workspace mailbox, minutes apart, inside the prospect's business hours, in one thread, with a one-click way out. When someone answers, the sequence stops for them.

Every email is checked twice: when the person is enrolled, and again at the moment it leaves.

Logistics NL · call-first
  1. Day 1Call firstPower-dial list

    Script: Intro NL · privacy line on top

  2. Day 1Intro after the callAI draft · in review

    Consent captured on the call · art. 14 notice in Dutch

  3. Day 3Wait 2 business days

    Mon to Fri, 08:00 to 18:00, Europe/Amsterdam

  4. Day 3Replied?

    Yes: stop and hand off · No: continue

  5. Day 4Re: Intro after the callVariant A/B

    Same thread · In-Reply-To set

  6. Day 7Follow-up callTask

    Callback task if no answer

How it works

From a list to a conversation in four moves.

A sequence is a set of steps every enrolled person walks through on their own clock. You write it once; PEMAX decides when each step is allowed to happen.

  1. 01

    Build the steps

    Email, a call task, a place on the power-dial list, a wait, a branch, a follow-up task. Waits skip weekends unless you turn that off, and a branch can follow a field or a reply.
  2. 02

    Enrol with a check

    Enrolling runs the compliance check per person first. Anyone without a recorded lawful basis, in a country you have not allowed, or without a notice text in their language shows up blocked, with the reason.
  3. 03

    Send from the owner's mailbox

    Each step goes out from a mailbox the prospect's owner may use, their own first, rotated, paced and inside the market's hours. A rep never sends through a colleague's mailbox.
  4. 04

    Stop when they answer

    Interested, not interested, unsubscribe and wrong person end the sequence for that person. Out of office pauses it until they are back. Queued sends pause, they are never silently cancelled.

The mechanics

The parts that decide whether a sequence lands.

Most cold email fails on timing, threading and trust long before the copy is read. These are the rules PEMAX applies to every send, whoever set up the sequence.

Pacing and rotation

Two to six minutes apart, never a burst.

Each mailbox waits a random two to six minutes between sends, and two people at the same company are never mailed within ten minutes of each other. Slots land inside the market's business hours, in the market's time zone, so a list in Stockholm and a list in Rotterdam each get their own working day.

  • 200 prospects over three mailboxes split 67, 67 and 66
  • One capacity rule for every mailbox: 40 a day by default, lower while it warms up
  • A full mailbox hands the send to another mailbox the rep may use, or waits for the next local day
  • A paused mailbox makes the step wait and retry. It never drops it
Send plan · Tuesday · Europe/Amsterdam

Rotation · 200 enrolled

67 / 67 / 66

10:0010:1010:2010:3010:40
  • sanne@brightwater.example

    Today 23 of 40

  • joost@brightwater.example

    Today 19 of 40

  • inge@brightwater.example

    Today 9 of 15 · warming

Held to 10:12. Sanne mailed kuipers-transport.nl at 10:02, so the second person at that company waits ten minutes.
Per mailbox
2 to 6 min, random
Same domain
10 min apart
Daily cap
40, or the warmup cap

Threading and the way out

Every follow-up lands in the same thread.

Each email gets its own Message-ID. A follow-up carries In-Reply-To and References and a “Re:” subject, so the prospect's mail client shows one conversation. Replies are matched on those ids first, and a colleague's mail from the same company is never attached to your prospect by accident.

  • An RFC 8058 one-click unsubscribe header and a footer link on every email
  • No unsubscribe key, no send: the email waits and an alert opens
  • Your company name and postal address in every footer
  • A new sequence after an old one starts a fresh thread
Step 3 of 6 · follow-up
From
Sanne de Wit <sanne@brightwater.example>
To
daan@kuipers-transport.nl
Subject
Re: Peak weeks at Kuipers Transport

Hi Daan, a short follow-up on my note from Tuesday. Would a 20-minute call next week help to compare how you plan the December peak today?

On Tue, Sanne de Wit wrote: Hi Daan, I saw Kuipers added a route to…

Brightwater Outbound B.V. · Stationsweg 12, 3011 AB Rotterdam · Unsubscribe

Raw headers

Message-ID: <7c1e0b52-4a9f@brightwater.example>

In-Reply-To: <3f488f6b-91c2@brightwater.example>

References: <a91d27e0-0d3b@brightwater.example> <3f488f6b-91c2@brightwater.example>

List-Unsubscribe: <https://app.pemax.io/unsubscribe/eyJ0…>

List-Unsubscribe-Post: List-Unsubscribe=One-Click

X-AI-Generated: true

  • Threaded

    Reply chain kept, capped at 20 ids

  • One click out

    Header and footer link

  • AI marked

    Kept after your edits

AI drafts

AI writes the draft. A person sends it.

An AI step drafts the email for each person. By default every AI-drafted step waits in Review for its rep, in every market, until someone approves it. Only the workspace owner can turn that off, and managed markets review either way.

  • A rep who sees only their own prospects reviews only their own drafts
  • The AI marking stays on the email after a person edits it
  • A monthly AI spend cap, visible in Settings
  • If a draft fails, the step keeps the text you wrote as its fallback
Review · Sanne
Daan KuipersLogistics NL · step 2 AI draft

Peak weeks at Kuipers Transport

Hi Daan, thanks for picking up yesterday. As promised, here is how Vos & Partners plans its December peak in two pages. Worth a look before your planning round?

Edited by Sanne · the AI marking stays on this email

Discard Edit Approve and queue
AI spend this month€18 of €50

In detail

Everything a sequence does for you.

  • Each rep's own mailbox

    Reps connect their own Google Workspace mailbox with Google sign-in. A step sends from the prospect owner's mailbox; a rep who only sees their own prospects never borrows the pool.
  • Loud when access is revoked

    When Google withdraws a mailbox's access, the mailbox stops, its queued sends pause and the rep sees “Reconnect your mailbox” with the count waiting. Reconnecting resumes exactly those sends.
  • Calls in the same sequence

    A call task with a deadline, or a place on the power-dial list. A sequence with only call steps sends no electronic message, so the email rules do not hold it back.
  • Follow-up tasks

    New task from the task list or the prospect drawer, due in the market's own time. Admins assign tasks to a teammate; the list shows Done and Skip.
  • The privacy notice, in their language

    The first email to a person carries the GDPR article 14 notice in their language, filled with your data source and privacy page. A missing value blocks the send and says which one.
  • Checked again at the send

    The compliance check runs at enrolment and again when the email leaves. Remove a person's lawful basis after enrolling and their queued email fails with the reason, never silently.
  • No double sequences

    An address that another sequence mailed in the last 30 days is not mailed by a second one. Manual one-off emails from the inbox are your call and never cancelled.
  • Market time, not server time

    Business hours, waits and due dates follow each market's time zone, so a DACH list and a Nordic list each send in their own working day.
  • Hard bounce, hard stop

    A hard bounce suppresses the address that failed and stops its sends. A soft bounce makes that person's queued emails wait 24 hours. Nothing is suppressed on a guess.

One honest limit

Sequences send from Google Workspace mailboxes. A Microsoft 365 mailbox can be connected and used to reply from the inbox, but it does not run cold sequences: PEMAX does not read replies, bounces or unsubscribes from an Outlook mailbox, and a sequence that cannot hear “stop” should not send.

The details that matter

Pacing, capacity and replies, in numbers.

These are the defaults every new workspace starts with. Each one is a workspace or market setting, so a team with its own rhythm can tune it.

Pacing and capacity
RuleDefault and effect
Gap between sends, per mailbox120 to 360 seconds, randomA batch spreads over the morning instead of leaving in one burst.
Same recipient domain600 seconds apartTwo people at one company never get your mail in the same ten minutes.
Sending windowThe market's business hours; Mon to Fri, 08:00 to 18:00 when none are setJudged in the market's own time zone. A slot outside the window moves to the next opening.
Daily cap per mailbox40, or the warmup cap when that is lowerCounted per market-local day. A mailbox that is not warming yet starts at 5.
A mailbox is fullAnother mailbox the rep may use, else the next local dayCapacity ranks mailboxes. It never drops a send.
Soft bounces above 15% in 48 hoursToday's cap halves, re-checked hourlyOld bounces age out of the window, so the cap comes back on its own.
A mailbox is paused or reconnectingThe step waits and retries every hourA run is never parked for a temporary problem, and no step is lost.
What a reply does to the sequence
Reply labelWhat happens
InterestedSequence ends with its goal reached. The lead goes to your CRM when you connected one.
Not interestedSequence ends for this person.
UnsubscribeSequence ends and the address goes on the suppression list.
Wrong personSequence ends for this person.
Out of officeSequence pauses until the return date in the reply, or 30 days when there is none.
Automatic replyNothing changes. Machine noise never stops a sequence.
Anything elseSequence pauses until a person has looked at it.

A label the classifier is not sure about pauses the sequence instead of ending it. Correct a label in the inbox and every count follows.

FAQ

Questions about sequences

Which mailboxes can send a sequence?

Google Workspace mailboxes, each connected by its own rep with Google sign-in. Microsoft 365 mailboxes can be connected for replies from the inbox, but not for cold sequences, because PEMAX does not read replies or bounces from them. Free addresses such as gmail.com cannot be a sending domain: you need a domain you control, so its SPF, DKIM and DMARC records can be checked.

How many emails does one mailbox send a day?

Forty by default, or less while the mailbox warms up; a mailbox that is not warming yet starts at five. Within that cap the pacing keeps sends minutes apart, so a full day of mail from one rep looks like one person working through a list. Admins can change the daily limit per mailbox.

Can AI write the emails?

Yes. An AI step drafts each email for the person it goes to, and by default the draft waits in Review until its rep approves it. Every AI-drafted email carries an X-AI-Generated header, also after a person edited it. Drafts run on an Anthropic key: your own, sealed in the vault and used only for your workspace, or, where agreed, the platform key under a monthly cap. Drafting inside the browser with your own key is coming soon; sequence steps already use it.

What happens when a rep leaves or loses access?

When Google revokes a mailbox, it stops sending, its queued emails pause and the rep is asked to reconnect. Those emails are not moved to a colleague's mailbox. When someone leaves the team, an admin removes them and hands their prospects and work to a named teammate in one step.

Can a sequence include LinkedIn?

LinkedIn connection requests and messages exist as step types, sent through a LinkedIn account connected with Unipile's hosted sign-in, so PEMAX never sees the password. A LinkedIn message always needs a lawful basis. A connection request without a note is treated as pitch-free, and every such request is logged on the audit trail. Email and phone are where PEMAX does most of its work.

What does PEMAX not do?

It does not send from a domain that fails its DNS check, it does not mail anyone without a recorded lawful basis, and it does not burst a list out in one go. It is also not a CRM: a qualified lead goes to yours through a signed webhook.

See PEMAX on your own pipeline.

Thirty minutes with the people who build it. We show the product on a real workspace, answer the hard questions about deliverability and compliance, and tell you honestly whether it fits.

Invite-only workspaces · Hosted in the EU · Bring your own keys