Reach
Senders: mailboxes, numbers and domains
Connect the mailboxes and numbers campaigns send from, set each one’s hours, limits, warm-up and signature, and check your domain’s DNS.
On this page
Senders are what your campaigns send from: mailboxes for email, numbers for SMS, the domains those mailboxes use, and any messaging provider you connect yourself. Manage them in Reach → Senders.
- Manage senders
- Manage Reach
- A Google, Microsoft 365 or SMTP/IMAP mailbox
- SMS
- A registered business and use case, and a number that can send
- Where
- Reach → Senders (
/clients/reach/senders)
Mailboxes#
Campaigns send from your own mailboxes, as you, and replies come back to them.
Connect a mailbox#
Choose how to connect:
| Option | For | Replies |
|---|---|---|
| Gmail or Google Workspace | Seen instantly | |
| Microsoft 365 | Outlook and Exchange Online | Seen instantly |
| Any other mailbox | Zoho, Fastmail, your host … | Seen by checking IMAP every few minutes |
For any other mailbox, enter the SMTP server (to send) and the IMAP server (to see replies), the username (usually the email address) and password — an app password if your host requires one — and the security type (STARTTLS, SSL/TLS). Without IMAP, Reach never sees a reply and keeps following up with people who already answered.
After connecting, send yourself a test before a campaign uses the mailbox.
The mailbox page#
Select a mailbox to see and change everything about it:
- How it signs — the name people see, where replies go, and a formatted signature.
- How much it sends — a daily limit and the least time between sends, and whether it warms up gradually. The calculated safe volume always applies; your limit can only lower it. See Sending safety.
- When it sends — its own sending window, time zone and days, overriding the workspace default.
- Domain checks for the address it sends from.
- Last 30 days — sends, bounces, replies and complaints.
- Campaigns using it.
- Default for new campaigns, pause, send a test, disconnect.
A mailbox's settings belong to the workspace once it is used for Reach, so teammates who manage Reach see the same limits and signature.
Domains#
Senders → Domains checks the DNS of each domain you send from, so receiving servers trust your mail.
Choose Add a domain and enter the part after the @ in your sending address.
Say who sends mail as it — Google, Microsoft or another host. That decides which records the domain needs. A connected mailbox on the domain answers this for you.
Reach reads the domain's DNS and checks each record: MX, a single SPF record that names every sending provider (within SPF's 10-lookup limit), DKIM for your provider, and your DMARC policy.
For anything missing or wrong, Reach shows the host and value to create at your DNS provider, with copy buttons. If your mail host uses a DKIM selector Reach does not try on its own, enter it.
Re-check after changing DNS. Changes can take time to propagate.
Reach never invents a DKIM key or a record value — it shows what your provider publishes and what your DNS says right now.
Numbers (SMS)#
Senders → Numbers lists the numbers texts can send from, with their state — Can send, Waiting on registration, Paused for Reach or Not connected — and for each, the most texts a day and seconds between texts. Send a test text to your own mobile.
A step without a named number sends from any number that can.
Registration comes first#
Carriers need to know who is sending before any text goes out. In Reach → Settings → SMS:
- Register the business — who is sending.
- Register a use case — what the messages are, and how people agreed to receive them. A use case is approved separately from the business.
A number can only send under an approved use case.
Messaging connections#
Senders → Messaging connections lists SMS providers you connected with your own account (for example Twilio). Unobits sends from that account's numbers and reads replies to them. It never buys or releases numbers, and never changes billing on your provider account.