Customer stories in their words
Operators who run sending.ac day to day describe what they tested and what they noticed. We quote them as written and add the setup behind each one.
- 213K mailboxes under management
“I tested sending a link and a GIF in the very first email of a sequence, normally a fast way to get flagged. Still landed in primary. Ran it across a few domains to check it wasn't a fluke, same result each time.”
What they ran on sending.ac
Setup, DNS and a contained burn
Saief Tissaoui runs sending.ac on Azure mailboxes. He describes a fast setup with DNS and DKIM written for him and each domain on its own tenant, so a burned domain stays inside that tenant.
- Azure mailboxes, one tenant per domain
- DNS verified before the first send
- Link and GIF test repeated across domains
“Setup was fast, DNS and DKIM handled automatically, and each domain runs on its own isolated tenant, so a burned domain stays contained.”
From someone who has bought mailboxes before
Sergio Perea buys mailboxes. His note is about the interface he works in, where domains, mailboxes and their status labels sit in one view.
- Domains and mailboxes in one view
- Status on every domain
“You guys have the smoothest UX/UI of all the inbox resellers I've purchased from. And I've worked with ALL of them.”
How a before and after reads
Reply rate in sending.ac counts real replies only, with warm-up and out-of-office counted separately, so a before and after compares the same thing on both sides.
- Real replies only
- Per domain and per sender
Run the same test on your domains
Azure mailboxes with DNS written and verified for you. Growth is $199/mo for 350 Azure mailboxes.