Any vendor quoting you a specific inbox-placement percentage is quoting you a number they cannot control and did not measure at your recipients' mailbox providers. We're not going to do that. Instead, here is exactly what CleverlyBox does to keep your mail authenticated, ramped, monitored and — when it goes wrong — stopped.
Add a sending domain and CleverlyBox generates the full DNS record set: OWNERSHIP, DKIM, SPF and DMARC. The DKIM keypair is created for you — you never touch openssl. Copy each record into your DNS, then hit verify.
Every record carries a live check with its own status. No guessing whether propagation finished. No sending from a half-authenticated domain because a TXT record had a stray quote in it.
Illustrative record set. Values are generated per sending domain in-app.
Mailbox providers judge a sending IP and domain on the pattern of behaviour, not the content of one campaign. A cold IP that suddenly floods gets filtered — and once it's filtered, weeks of your calendar belong to that mistake.
CleverlyBox has a warm-up engine with linear and exponential strategies. Each sending server gets a daily quota that steps up on a schedule. The platform enforces it. You are not relying on your own restraint at 11pm before a launch.
A rolling 24-hour window watches four numbers: sent volume, bounces, complaints and unsubscribes. Cross the threshold and in-flight campaigns pause themselves. Not a warning email you read the next morning. A pause.
This is the difference between a bad list costing you an afternoon and a bad list costing you a domain. Most platforms will happily send all 80,000 into a wall and then show you a lovely chart of the wreckage.
Deliverability is a loop, not a launch. If you don't ingest what comes back, you keep mailing addresses that already told you to stop — and that is precisely what mailbox providers punish.
IMAP and POP3 mailbox pollers read your bounce mailbox directly, and vendor webhooks deliver bounce, complaint and delivery events from providers that push them. Belt and braces — whichever your provider supports.
When a recipient hits "spam" at a provider that runs a feedback loop, the complaint comes back to a handler. That address stops receiving your mail. Immediately, and without you reading a report.
A blacklist you control, plus a platform-wide one. Bulk import addresses you already know are poison. Nothing on it ever gets sent to, from any list, by any campaign or automation.
Reputation damage is cheapest to prevent at the point of composition. These run in front of the send, not behind it.
A content check runs against the campaign before it goes out. The words that get bulk mail filtered are well documented and entirely avoidable — this is the point at which you find out you used one.
Campaigns can require approval before they send. Useful when a junior has the keys, or an agency is sending on a client's domain, or you simply want a second pair of eyes on the thing that reaches 300,000 people.
Gmail and Yahoo now require one-click unsubscribe headers from bulk senders. CleverlyBox emits them, and enforces an unsubscribe link in the body. This is not optional any more, and it is not a setting you can forget to tick.
List cleaning is not a separate vendor here — 16 verification providers are wired into the platform. The cheapest bounce is the one that never got sent. See Email Verification.
Daily roll-up records: sent, delivered, bounced (soft + hard), complained, opened, clicked, unsubscribed, deferred, rejected.
DKIM, SPF and DMARC pass rates are recorded per mailbox provider and per sending identity, then rolled up daily alongside sent, delivered, bounced soft and hard, complained, opened, clicked, unsubscribed, deferred and rejected.
Those are things that genuinely happened, observed at our end. "97% inbox placement" is not one of them, at any vendor, and pretending otherwise would be the first lie we told you. The honesty is the pitch.
None, and be very suspicious of anyone who does. Inbox placement is decided by Gmail, Microsoft, Yahoo and the rest, based on your list, your content, your history and your recipients' behaviour. No sending platform observes that decision, so no sending platform can honestly quote you a number. What we can do is authenticate your domain properly, ramp your volume sensibly, ingest every bounce and complaint, and stop you sending when the numbers turn. That's what this page is.
No — sending on CleverlyBox's own infrastructure works out of the box. You need a verified sending domain when you want mail authenticated as you, which you will want before any serious volume, and which the SMTP relay requires outright.
A rolling 24-hour window tracks sent volume, bounces, complaints and unsubscribes against thresholds. If a threshold is crossed, in-flight campaigns pause. You investigate, fix the cause, and resume — with the damage bounded to the emails already gone rather than the whole list.
Automatically, by two routes. IMAP and POP3 pollers read a bounce mailbox for providers that return them by mail, and vendor webhooks capture bounce, complaint and delivery events from providers that push them. Feedback-loop handlers catch spam complaints. Hard bounces and complaints stop receiving mail.
Yes. RFC 8058 one-click unsubscribe headers are emitted, and an unsubscribe link is enforced in the body. Both requirements are met without you configuring anything.
Yes. The blacklist takes bulk imports and is scoped to your account, alongside a platform-wide list. Anything on it is excluded from every campaign and every automation, regardless of which list the address turns up on later.
That's the whole job. We'd rather show you the machinery than sell you a percentage.