PlatformEmail Outreach
Written, sent, followed up. Then it stops.
A three-step sequence from your own inbox that halts the moment they reply.
Kandi · Email Outreach
How it runs
Write
One hook per candidate, from their real history. Never mail-merged.
Check
Two checks first. A failing draft is held.
Send
From your own Gmail or Outlook. Fifty a day, paced.
Follow up, then stop
Day 3 and day 7. A reply cancels the rest instantly.
Built in
Replies land with you
The thread is in your inbox; the board moves to Replied.
Opt-outs are permanent
One "unsubscribe" blocks every job in your organisation.
Domain watched
SPF, DKIM, DMARC and blocklists scored live.
Questions buyers ask
Does the QA check slow sending down?
No. The per-send pass is deterministic and instant, and the model review runs once per campaign's content rather than per message — a 200-person sequence costs one review, not two hundred.
What happens to a held message?
It waits with its reason attached and the field named. Nothing goes out while it's held; you fix the field and release each message — edit, send, or skip.
Can I turn a check off?
The content checks can be relaxed per agent. Opt-outs can't: an opt-out is enforced before a message is drafted, and detecting one never depends on a model's judgement.
Which mailbox does it send from?
Yours. Gmail and Outlook connect directly, so replies land in your inbox and the thread reads like you wrote it, because you approved it.
How do candidates opt out?
By replying — "unsubscribe", "stop emailing", any clear no. Detection is deterministic, an opt-out is permanent, applies across every job in your organisation, and is enforced before a message is drafted rather than after.
See it on one of your own roles.
Bring a clinical role. See how the platform handles sourcing, outreach and initial screening for your team.