by mkdirFrom an empty workspace to a reply you approved.
Setup is a checklist, not a call. The engine does the reading and the writing; the steps marked in black are yours, and none of them can be switched off.
Day one.
Get a workspace
Invite-only for now. Tell us about your outbound and we’ll set you up. The workspace is created with its own database, and a verification link is sent to the email you gave.
Verify the email
Until the address is verified the workspace can be explored but cannot verify leads or spend credits. That is the abuse control, and it is the same for everyone.
Domains and mailboxes
Bring your own or provision from inside the workspace: a quote first, then an order with a spend ceiling. Each mailbox is checked for MX, SPF, DKIM and DMARC and enters warm-up.
Warm-up runs, and is refreshed on a schedule
A mailbox stays out of rotation until it is ready. Warm-up age is refreshed for every workspace; a stale report is shown as stale.
Tell it what you sell
The knowledge base is what replies are drafted from. What the account does not know, a draft will not claim.
Build the list and the sequence
Search for free and reveal on purpose, or import a file. Write the steps and variants, set the sending window in your timezone, keep the do-not-contact list current.
Launch
The launch gate checks the checklist is complete before a first campaign can go. Then a person presses launch. Sends follow the window from mailboxes that are ready.
The loop.
Four steps, in the order they happen. The front page walks through them with the product’s own screens; the short form is here.
A reply lands
Matched to the lead and the sequence that produced it. Unknown senders are recorded, never dropped.
It is classified and answered in draft
Interested, question, objection, out of office, wrong person, unsubscribe, or unclassified. A draft is written from the knowledge base with a confidence tag.
You approve, edit, schedule or skip
The draft waits. Silence is not consent and no timer decides for you.
It sends and the thread stays whole
From the mailbox that started the conversation, in the same thread. Interested becomes an opportunity. Out of office becomes a date. A referral becomes a suggested contact for you to approve.
Read-only syncs, one pause, and the delivery of what you approved.
| Scheduled job | What it may do | What it may not do |
|---|---|---|
| Inbound sync | Pull new replies from every mailbox and match them. | Send anything. |
| Warm-up refresh | Update warm-up age for every workspace. | Mark a mailbox ready without a report. |
| Send-health check | Note when no sends have been recorded for a while. | Declare an outage. |
| Variant optimizer | Pause a losing variant and leave a note. | Edit, replace or launch anything. |
| Scheduled delivery | Send a reply a person approved, at the time they chose. | Send a reply nobody approved. |
Held by a test. The build fails if a scheduled job ever references a send path. The security page names it.
The checklist is the onboarding.
Create the workspace, verify the email, and the Setup screen tells you what is next.