Approve what your team sends
Edit any draft and check a campaign’s recipients, senders and messages before it goes out.
Security & sending controls
Every campaign is reviewed before it launches, sends from your own mailbox within your limits, and skips anyone who opted out.

Sending controls
Edit any draft and check a campaign’s recipients, senders and messages before it goes out.
Cap daily volume, sending hours and the gap between emails. Pause a mailbox that needs attention.
Unsubscribes and blocked people or domains are skipped in every campaign across the workspace.
Access & protection

Sending and reading are separate permissions for each member and mailbox, so assigning a reply never opens the whole inbox.
Add a passkey or two-factor to each sign-in. Connection secrets are encrypted, and API tokens are scoped and expire.
Approvals, prospect updates and admin changes are recorded, with webhook delivery history.
Mailbox health
Reach-book.com reads your domain’s SPF, DKIM and DMARC records and tells you what is missing before a campaign launches.
These checks help you fix or pause a mailbox. They can’t guarantee inbox placement.
Only if you grant it. Mailbox read and send permissions are set separately for each member, so assigning a conversation to someone does not give them access to the mailbox.
Campaigns launch after review and approval. You see the rendered messages, recipients, and senders before approving, and the approved snapshot is what gets sent within the schedule and limits you set.
Set daily limits, sending hours, and the time between messages for each sender. Mailboxes with delivery problems or failed health checks can be paused so no further outreach goes out until you review them.
Recipient unsubscribes and do-not-contact entries apply across workspace outreach, so a suppressed person or domain is left out of future campaigns.
Sign-ins support passkeys and two-factor authentication. Integration credentials are encrypted, stored secrets are not shown back to team members, and workspace API tokens are scoped with an expiry date. Administrative changes are recorded in the audit history.
More answers in the help center.