MEASURED RESULTS
What this infrastructure actually does
Numbers from our own outbound, sent on the same Microsoft 365 inboxes we provision for customers. The full spread is published, including the campaigns that replied at zero.
The number that belongs to the infrastructure
Bounce rate is the metric a provisioning service is accountable for. It reflects whether the mailboxes exist, whether authentication passes, and whether the receiving side is willing to accept the mail at all. Across 26,698 contacted leads, 461 bounced.
1.73%
BOUNCE RATE
461 of 26,698 contacted. Ranged 1.3% to 2.4% across accounts.
26,698
LEADS CONTACTED
Drawn from 936,170 loaded across 11 campaigns.
11
CAMPAIGNS
Run concurrently across two sending accounts on separate domains.
For context, a bounce rate above roughly 5% is where providers start treating a sender as a list-quality problem. Staying under 2.5% while sending from newly provisioned mailboxes is the outcome the authentication setup is meant to produce.
The numbers that do not belong to the infrastructure
Reply rate is a function of the list and the copy. We supply neither. These are published because omitting them would leave a misleading picture, not because they are a promise.
1.9%
REPLY RATE
501 replies from 26,698 contacted. Ranged 0% to 4.1% per campaign.
19%
OF REPLIES POSITIVE
95 positive replies. Share of replies, not of contacted. Ranged 0% to 50% per campaign.
0% – 4.1%
REPLY RATE RANGE
Same infrastructure and authentication throughout. The variable was the list and the message.
The spread is the useful part. The strongest campaign replied at 4.1% and converted half its replies to positive; the weakest replied at zero. All of them sent from correctly authenticated inboxes with the same bounce profile, which is the clearest statement of what infrastructure does and does not decide: it controls whether mail arrives, not whether anyone wants to read it.
Judge a provider on the first of those. The second is your list and your copy, and no inbox provisioning changes it.
The dashboards these came from
Both accounts, as the sending platform reports them. Every figure above is taken from these two summaries.
Campaign names are cropped out. They encode our own testing structure and are not part of what these numbers demonstrate.
How these were sent
One order of 100 inboxes on a single domain, three sends per inbox per day, is 300 sends per day. The campaigns above ran several such batches concurrently across separate domains, which is the same structure described in the buying guide. Authentication was SPF, DKIM and DMARC per domain, configured before first send, exactly as provisioned batches are handed over.
What this is not
These are our own campaigns, not customer results, and no customer data appears here. They are a single sender in a single market over one period. They are not a projection of what your list will do, and nothing here should be read as a guarantee of reply volume or revenue.
What they do demonstrate is that the provisioning holds up at volume: mailboxes that authenticate, land, and keep bouncing under 2.5% across tens of thousands of sends.