Deliverability you can see.
Every platform claims deliverability. The useful question is what a platform refuses to do when it cannot verify something. These are the four layers Raechly enforces, and what each one actually checks.
Authentication that aligns
SPF, DKIM and DMARC are generated together with a custom MAIL FROM subdomain, so the bounce path sits on your domain and SPF aligns for DMARC rather than passing for a provider. Sending is blocked until DKIM verification succeeds.
Warmup you can audit
The warmup loop runs on pool inboxes you register and control, so both ends of every thread are visible to you. Sent-versus-replied is reported as raw counts, because a health score you cannot check is not evidence.
Bulk sender compliance
Every message carries List-Unsubscribe with RFC 8058 one-click POST, Precedence: bulk and a stable Message-ID. That is why messages are assembled as raw MIME rather than handed to a simpler send API.
Suppression that holds
Bounced and unsubscribed leads are suppressed permanently and never revived by a re-import. Address validation runs per lead inside the send path, not only at import time.
The measurement problem
Deliverability tooling tends to count the wrong things. Sends are easy to count and almost never fail, so a dashboard built on send counts looks healthy under almost any circumstances. The signals that actually decide placement — engagement, replies, whether a human interacted at all — are harder to observe and much easier to report optimistically.
We learned this the direct way. Two domains warming side by side: one captured 17 replies from 134 sends, the other captured zero from 99 and reported nothing wrong, because every reply was bouncing at a mail provider we did not control. The full write-up is in your warmup dashboard is probably lying to you.
The fix was not better reporting. It was making the platform refuse: a mailbox whose inbound path cannot be verified does not send, at all, for any reason. That constraint is the difference between a number and a fact.
Start with these
Email warmup
Email warmup gradually increases sending from a new mailbox while generating positive engagement, so mailbox providers build a reputation for the address before it sends cold volume.
Reply capture
Reply capture is the inbound routing that delivers replies back into your sending platform. Without it, warmup cannot be verified and genuine responses from prospects are lost.
Inbox placement
Inbox placement is the share of delivered messages that reach the primary inbox rather than spam or a promotions tab. It is distinct from delivery rate, which only counts acceptance by the server.
Sending reputation
Sending reputation is the trust score mailbox providers assign to your domain and IP based on complaint rate, bounce rate, engagement and authentication history. It determines inbox placement.
Deliverability questions
Does Raechly guarantee inbox placement?
No, and neither can anyone else. Placement depends on your domain, your list, your copy and the recipient’s provider. What Raechly guarantees is that the parts under its control are correct: aligned authentication, verified warmup, compliant headers and enforced suppression.
Why is the daily cap so low?
Thirty per mailbox per day, enforced in the pipeline regardless of configuration. Domain reputation is built over months and destroyed in days, and the damage is delayed enough that raising a limit under pressure always feels justified at the time. Scale by adding mailboxes and domains instead.
What happens when a message bounces?
Bounce and complaint notifications arrive over an SES webhook whose SNS signature is verified in the handler, then land on the lead record. Hard-bounced addresses are suppressed permanently.
Can I check whether reply capture is actually working?
Yes, and you should. The per-mailbox reply_capture flag is reconciled hourly against the routing provider, and warmup stats report sends and replies as separate raw counts. High sends with flat replies means the loop is broken.
Point your assistant at it and see.
Connect the MCP server, register a domain, publish the DNS records it hands you. You will know inside an hour whether this is the setup you want.