Hiring pipelines usually get tested with a colleague's borrowed Gmail and the same three test accounts, reused until nobody remembers which offer letter went where. The decline path rarely gets run at all. Reclario gives your team a private catch-all domain for $49/mo per domain. Put candidate-4821@yourteam.reclar.io on a candidate record and mail to it arrives, with nothing to set up first. Each test applicant keeps their own thread, and the address tag decides how they answer interview invites.
If your ATS can send email, it can send to Reclario. You don't build an integration, and you don't configure anything per candidate.
Your team's private catch-all domain: $49/mo per domain, unlimited addresses, and only your team can see the mail.
yourteam.reclar.ioCreate the candidate in your ATS with any address you make up on your domain. It receives mail from the first send.
candidate-4821@yourteam.reclar.ioMove the candidate through your stages and each email shows up in a shared live inbox. When an interview invite arrives, Reclario sends the RSVP to the organizer.
REPLY: acceptedThe first email a candidate ever gets from you. Check that it arrives, renders, and links back to the right requisition, for every source and every job.
Screening links, assessment invites and self-schedule emails, checked in the delivered message rather than a preview pane in your ATS.
Send a real ICS invite to a tagged address and Reclario replies to the organizer. Add a delay when you want the candidate to take their time.
Offer emails carry attachments and formatting that has to be right. Open the rendered message, download the PDF, or pull the raw .eml to see what the candidate received.
Rejection wording, silver-medalist nurture, and the re-engagement campaign that goes out months later. Few teams test these, and each test candidate keeps their own thread so you can follow one through.
Candidate names, salary bands and offer details stay out of public inboxes. Your domain is unlisted and unsearchable, and only members you invite can read it.
Scheduling is where hiring flows break, and it is the hardest step to test because someone normally has to click Accept. On Reclario the address tag picks the answer: interview+accept@ accepts, interview+decline@ declines, and +maybe answers tentative. Add +delay5 and the reply goes out five minutes later, the way a candidate who isn't watching their inbox would answer. Each reply is a real iTIP message to the organizer, so your ATS updates the interview as it would in production. Calendar invite testing covers the rest of the mechanics.
Invite your recruiters, recruiting ops and the engineers who own the templates to one shared live inbox. When someone asks what the candidate saw, everyone can open the same email instead of passing screenshots around. For regression testing, API keys and webhooks let CI provision addresses, read messages and assert on delivery, so a broken offer template fails the build before it reaches a real candidate. Email testing for QA goes further into the automation side.
interview+accept@yourteam.reclar.io and Reclario sends the acceptance to the organizer. Other tags decline (+decline), answer tentative (+maybe) or wait five minutes before replying (+delay5), and counter-proposals with a new time are supported. Calendar invite testing has the details.candidate-4821@yourteam.reclar.io starts receiving the moment something sends to it. You don't create inboxes one at a time or change DNS on your side. Use one address per applicant, per requisition or per test run, whichever matches how you test.METHOD:REQUEST) gets a real RSVP back. There is no integration to build: put a Reclario address on the candidate record and send.A private catch-all domain for your team is $49/mo per domain. You can also run your first test candidate through the free public sandbox at public.reclar.io (work email required, no credit card). If you're still comparing tools, see email testing tools compared.
Start free See pricing