The two meanings of white-label, and which one your clients feel
Ask ten cold email tools whether they are white-label and ten will say yes. What they usually mean is a custom domain for the dashboard and your logo in the corner. Your client still knows they are inside somebody else's software, their staff still need accounts on that software, and the moment they want to read replies they are back in Gmail or Outlook with the passwords you had to hand over.
emailcampaign.ai does the dashboard version too. What it adds is a door: a complete webmail and administration console that lives at an address the client owns, such as mail.theirbrand.com, shows only their brand, and is where their people sign in, read, reply, search, file, and where their administrator runs the rules. Nothing about it says us, and a guard makes sure it stays that way on every deployment.
What the client's administrator can do from their own console
| Area | What it does |
|---|---|
| People | Add and retire mailboxes, issue and rotate app passwords (shown once), suspend, sign out everywhere, set who administers |
| Connected Google and Microsoft accounts | Connect an account once as the administrator; staff sign in with the address and an app password, never the provider password; the link is re-checked four times a day and only the administrator can disconnect |
| Joining rules | Who may sign up: nobody, named domains, or any work email; approval per person; personal Gmail and Outlook allowed or not; throwaway addresses always refused; two-factor optional or required |
| Privacy | Hide every correspondent's address from staff; show or hide the company; unhide specific contacts for everyone or for named people; names and pictures for outside contacts; audited reveals |
| Forwarding | Every forward, only outside forwards, or none, parked for the administrator's approval; approve and send, or decline with a reason |
| Deleted mail | A copy of everything staff delete is kept for the administrator, graded for sensitivity (copied, outside the company, hidden recipient, contact exposure), readable per person and removable only by the administrator; staff see nothing of it |
| Files and Google Drive | Storage allowances per person; Google Drive linked per account under administrator control, with outside sharing held for approval |
| Activity | Sign-ins, password issues, changes, reveals and reviews, in plain sentences with the address they came from |
What their staff see
A sign-in page in their brand at their address, with "keep me signed in on this device". A mail client that behaves like the one they know: threads, search across the whole mailbox, labels, snooze, scheduled sending, templates, signatures, attachments, filters, a vacation reply. Hidden addresses appear as names or as "Contact at company.com". If the administrator has allowed it, one sign-in can switch between several mailboxes. On a phone it is a phone layout, not a shrunken desktop.
What you run for them on the campaign side
- Infrastructure per client, at cost. Domains bought, Google Workspace or Microsoft 365 mailboxes created, DNS written, warm-up run, all behind one approval per client. Prices are itemised on the client's invoice, not hidden in yours. See how the infrastructure is built.
- Unlimited mailboxes and warm-up on every plan. A client with sixty mailboxes costs you the same plan as a client with six.
- A load balancer and client scorecards on Pro: sends spread across each client's fleet by health, and a per-client view of placement, bounces, refusals and replies you can put in front of them.
- One unified inbox that knows whose send a reply answers. Out-of-office messages are not counted as replies, and warm-up traffic never appears in it.
- Deliverability that acts. A 5.7.x refusal from a provider pauses that sender for that provider automatically; a domain whose placement slips is paused before replies dry up; DMARC reports are read for you.
- Invoicing built in. Numbered invoices, card and bank payment, receipts to the payer and to you, reminders, and a hosted invoice page. Bill each client for their own fleet.
Setting up a client door
- Create the client's workspace and add their domain; verify it with a CNAME or an A record. The platform issues the certificate and keeps it renewed.
- Upload their logo and colours. The sign-in, the client and the console take the brand at once.
- Add their people, or open sign-up to their domain, and issue app passwords. Connect any Google or Microsoft accounts they already use.
- Set the privacy, forwarding and two-factor rules the client wants; everything can be changed later from their console or yours.
- Hand over the address. From then on they administer their own door; you keep the campaigns, the infrastructure and the invoices.
Pricing for agencies
| Plan | Price | Included |
|---|---|---|
| Trial | Free for 14 days | Unlimited mailboxes and warm-up, 1,000 active leads, 3,000 emails a month |
| Basic | $39 a month | Unlimited mailboxes and warm-up, 2,000 active leads, 6,000 emails a month, reply tracking |
| Pro | $94 a month | Everything in Basic, 30,000 active leads, 150,000 emails a month, reply intelligence, load balancer and client scorecards |
| Infrastructure | At cost plus $5 setup per mailbox | Google Workspace seats at $8.40 a month, Microsoft 365 at the provider's rate, domains at about $12 a year, self-hosted servers from $39 a month |
Questions, answered straight
- What does 'white-label' actually cover?
- Two levels. The campaign side, where you run outbound for many clients from one account with unlimited mailboxes, per-client load balancing and scorecards. And the door: a webmail and admin console on the client's own hostname, carrying only their brand, where their staff sign in and work their mail. Most tools offer the first with your logo on the dashboard. The door is the part clients notice.
- Do clients ever see emailcampaign.ai?
- No. A client's door shows their name, logo and colours, and a guard checks every deployment and every thirty minutes that not one mention of us appears on any door page, in the sign-in, the mail client or the console. The application host and the doors also carry separate robots rules, so a client's door is never indexed under our name.
- How does a client's team use their Gmail without me giving out the Google password?
- The client's administrator connects the Google account once, from their console, by signing in as that account. The platform keeps a refresh token that does not expire on its own. Staff get a mailbox address and an app password issued by the administrator; they read and send the Gmail through the door and never hold the Google credential. Disconnecting is the administrator's act alone.
- Can I hide client contacts from junior staff?
- Yes. A workspace policy masks every correspondent's address, showing a name or the company instead; the administrator can unhide a specific contact for everybody or for named people, give outside contacts a display name and picture, and reveal an address on the record when needed. Reveals are rate limited and written to the activity log.
- What happens when a staff member forwards a client's mail outside?
- If the workspace rule says so, the forward is parked, finished and signed, until an administrator approves or declines it. Approval sends it exactly as written from that mailbox with a Sent copy; a decline tells the person why. The rule can cover every forward, only forwards to outside addresses, or none.
- How is it priced for an agency?
- The plan covers campaigns and doors; infrastructure is at cost with a one-time setup per mailbox. Pro at $94 a month includes the load balancer and client scorecards; unlimited mailboxes and warm-up are on every plan. The calculator prices the exact fleet per client.
Published 19 September 2026. Updated 19 September 2026. Written by the team that runs the infrastructure; numbers come from the platform's own provisioning and sending, and from the providers' published documentation at the time of writing.