Recruiting & interviews

One address per applicant. Hundreds of candidates. Zero real inboxes.

Testing a hiring pipeline usually means begging colleagues for their Gmail, reusing the same three test accounts, and never quite exercising the decline path. Reclario gives your team a private catch-all domain for $49/mo per domain — invent candidate-4821@yourteam.reclar.io and it exists. Every applicant persona gets its own address, its own thread, and its own RSVP behavior.

candidate-4821@yourteam.reclar.io interview+accept@yourteam.reclar.io interview+decline+delay5@yourteam.reclar.io offer+exec@yourteam.reclar.io
How it works

Three steps to a pipeline that tests itself.

If your ATS can send email, you can test it here. There is nothing to wire up per candidate and no integration to build.

1

Claim a domain

Your team's private catch-all domain — $49/mo per domain, unlimited addresses, nothing public.

yourteam.reclar.io
2

Put an address on each applicant

Create the candidate in your ATS with an invented address. It works instantly — no provisioning, no DNS.

candidate-4821@yourteam.reclar.io
3

Run the pipeline and watch

Every stage email lands in a shared live inbox. Interview invites answer themselves and reply to the organizer.

REPLY: accepted
The whole pipeline

Every stage email, end to end.

Application received

Confirm the first email a candidate ever gets from you actually arrives, renders, and links back to the right requisition — for every source and every job.

Screening invites

Screening links, assessment invites, and self-schedule emails — checked with real delivered mail rather than a preview pane in your ATS.

Interview invites that auto-RSVP

Send a real ICS invite to a tagged address and it answers itself: accept, decline, tentative, or propose a new time — with a human-like delay when you want one.

Offer letters

Offer emails carry attachments and careful formatting. Open the rendered message, download the PDF, or grab the raw .eml to check exactly what the candidate received.

Rejection and nurture

The paths nobody tests: rejection wording, silver-medalist nurture sequences, and re-engagement campaigns months later. Each persona keeps its own thread.

Private by default

Candidate names, salary bands, and offer details never sit in a public inbox. Your domain is unlisted and unsearchable — only invited members can read it.

Interview invites that answer themselves.

The scheduling step is where hiring flows break, and it is the hardest thing to test because a human normally has to click Accept. Reclario answers for you: the address tag decides the response, so interview+accept@ accepts, interview+decline@ declines, +maybe answers tentative, and +delay5 waits five minutes to simulate a candidate who is not glued to their inbox. Every answer is a real iTIP reply back to the organizer, so your ATS updates exactly as it would in production. Full mechanics in calendar invite testing.

Recruiters and engineers, watching the same inbox.

Invite your recruiting team, recruiting ops, and the engineers who own the templates into one shared live inbox — no forwarding, no screenshots, no "can you check what the candidate actually saw?" And when you want the pipeline regression-tested rather than eyeballed, API keys and webhooks let CI provision addresses, read messages, and assert on delivery, so a broken offer template fails a build instead of reaching a real candidate. QA teams go deeper in email testing for QA.

FAQ

Recruiting email testing, answered.

Can I test interview invites automatically?
Yes. Send a real calendar invite to a tagged address and Reclario answers it for you — interview+accept@yourteam.reclar.io accepts, +decline declines, +maybe answers tentative, and +delay5 waits five minutes first so you can watch pending states and reminder logic. Counter-proposals (propose new time) are supported too. Details in calendar invite testing.
Is candidate data private?
Yes — that is the point. Your domain is private by default: nothing is listed, nothing is searchable, and only the teammates you invite can read the mail. Public throwaway-inbox services are the wrong place for candidate names, salary bands, or offer letters, because anyone who guesses the address can read them.
How many test addresses can I create?
As many as you want. Your domain is catch-all, so every address works instantly — candidate-4821@yourteam.reclar.io exists the moment something sends to it. There is no per-inbox provisioning, no limit, and no DNS work on your side. One address per applicant, per requisition, or per test run.
Can non-engineers use it?
Yes. Recruiters, recruiting ops, and QA all work out of the same shared live inbox in the browser — no CLI, no API key required. Invite teammates and everyone watches the same pipeline in real time instead of forwarding screenshots.
Does it work with our ATS?
If your ATS sends email, Reclario receives it — Greenhouse, Lever, Workday, Taleo, SuccessFactors, iCIMS, Phenom, or something you built yourself. Mail arrives over real MX, and any standard ICS invite (METHOD:REQUEST) gets a real RSVP back. There is no integration to build: put a Reclario address in the candidate record and send.

Stop testing your hiring pipeline on real people.

Claim a private catch-all domain for $49/mo per domain — or run your first candidate through the free public sandbox at public.reclar.io (work email required, no credit card). Comparing options? See email testing tools compared.

Start free  See pricing