The most expensive failure in recruitment software is silent: your interview invite went to spam. Authenticate your sending domain and it stops happening.
By default we send on your behalf from our own domain, which works but shows as “via jugglehire.com” in most clients. Once you authenticate your own domain, mail comes from you — and far more importantly, Gmail and Microsoft stop treating it as suspicious. Unauthenticated bulk mail to consumer inboxes is now routinely rejected outright.
Add SPF, DKIM and DMARC
In Settings → Email → Sending domain, enter the domain you send from. We generate three records to add at your DNS provider.
SPFAuthorises us to send for your domain. If you already have an SPF record, add our include to it — never publish two SPF records.
DKIMCryptographically signs each message. This is the record that matters most to Gmail.
DMARCTells receivers what to do with failures. Start at p=none and read the reports for two weeks before tightening to quarantine.
Verify
Return to Settings → Email and choose Verify. Propagation is usually minutes. Once all three pass, send yourself a test to a Gmail address and a Microsoft address — check the message headers show DKIM pass and SPF pass.
If mail still lands in spam
CauseWhat to do
New domain, no historySending reputation takes days to build. Start with low volume and real conversations rather than a bulk blast.
Spammy subject linesALL CAPS, excessive punctuation and “ACT NOW” framing get filtered. Write like a person emailing one person.
One giant recipient listUse per-candidate stage emails, not a single mass send. We personalise per recipient automatically.
Broken reply-toPoint reply-to at a mailbox someone actually reads. Mail nobody ever replies to degrades your reputation.
Did this answer your question?
Two clicks, and it genuinely shapes what we rewrite next.