Configure the sending rail in Settings.

How to use it

1. 01Add the provider type you actually plan to send through, then confirm the route is healthy before you rely on it for a launch.
2. 02Keep provider names descriptive so operators can tell pooled, fallback, and primary routes apart.
3. 03Review quota and health indicators in Overview and Reports after setup so you can spot weak routes early.

Keep in mind

• Provider capacity and availability still depend on the external rail you connected.
• Free and paid workspaces may expose different delivery options depending on the active plan and admin access.

How to use it

1. 01Add the sending domain, then work through SPF, DKIM, and DMARC verification until the domain is genuinely ready.
2. 02Use the Warmup tab for warmup-specific controls instead of treating the Domains tab as the warmup command center.
3. 03Check that inbox connections, warmup sessions, and current warmup stage align before increasing send volume.
4. 04Before starting, confirm the selected domain, healthy provider route, approved warmup mailbox, plan eligibility, and available warmup mode.
5. 05Start a bounded session, then monitor current day, planned daily volume, stage, status, and events rather than repeatedly starting new sessions.
6. 06If a session pauses or fails, read its reason and detail, correct the underlying domain, route, mailbox, or volume issue, and resume only deliberately.

Keep in mind

• Warmup is operationally separate from the bare domain record. A verified domain is necessary, but it does not mean the domain is warmed or ready for higher volume by itself.
• Platform seed, hybrid pool, and private contributed modes have different setup requirements and are available only when the workspace eligibility response permits them.
• Warmup is asynchronous: the worker plans, executes, polls, and processes replies through queued jobs. A planned or active session may be waiting on the worker rather than broken.
• Warmup does not replace consent, suppression handling, content quality, authentication, or gradual production-volume judgment.

How to use it

1. 01Create sender identities that match the domain and team function you want operators to send from.
2. 02Attach reply routing deliberately so campaign replies land in the correct mailbox instead of a generic or unused inbox.
3. 03Use connected inboxes when the team needs reply handling, follow-up, or warmup inbox participation.

Keep in mind

• Sender identity, reply routing, and domain health should be reviewed together before launch.

How to use it

1. 01Use Billing to review the active plan, interval, and any self-serve changes that affect capacity or gated features.
2. 02Invite members only when they need workspace access, then confirm their role matches their responsibility.
3. 03Keep owners and admins limited to the operators who really need billing or infrastructure authority.

Keep in mind

• Feature access can be plan-aware. If a screen or action seems unavailable, verify both the active plan and the current role.
• Settings tabs stay fixed beneath the page topbar while you scroll, so long provider, inbox, warmup, billing, and account surfaces remain easy to navigate.
• New campaign unsubscribe behavior is off by default. Free-plan attribution is added at delivery time; paid plans do not receive it.