Recruitment email sync should put every candidate email on that candidate's record, matched to the right job, with replies kept in the same thread. Personal messages should come from a real address candidates can answer, never a no-reply one. Automated notices can come from a dedicated hiring address, as long as replies still reach your team.
By Dev Rishi Khare, former machine learning engineer at Amazon (search and recommendations) and Synopsys
What does recruitment email sync actually mean?
Good recruitment email sync connects email activity to the hiring record. When a candidate replies, you should see the message beside their application, job, stage, and earlier correspondence. Your team shouldn't have to search several inboxes to reconstruct the conversation.
Two-way sync means the ATS can record incoming mail and send replies through the connected account. One-way connections handle only part of that exchange. Some can send messages but can't bring replies back to the candidate record. Others can import messages but can't send from the recruiter's address.
Look past a generic "email integration" label. A vendor may request three separate permissions:
- Email Sending allows the ATS to send mail through your account.
- Inbox Sync lets it read relevant incoming messages and connect them with candidate records.
- Calendar access supports scheduling through the connected account.
Those permissions shouldn't be bundled into vague language. You should be able to tell what each connection does before granting access. An ATS email inbox for Gmail and Outlook should also show which candidate, job, and thread each message belongs to.
Should candidate emails come from your own inbox or a system address?
The right sender depends on the message. An interview follow-up benefits from a recognizable person. A shared hiring mailbox can be safer when several recruiters need access. A per-job ATS address can make application routing more reliable.
The wrong choice is a no-reply address for a conversation that may need an answer.
| Sender | Can the candidate reply? | Who sees the thread if the recruiter leaves? | Does the ATS need to read your mailbox? | What candidates may think |
|---|---|---|---|---|
| Personal work inbox | Yes | Depends on account ownership and ATS records | Usually, for incoming sync | A real person is handling the process |
| Shared hiring mailbox, such as jobs@ | Yes | The hiring team can retain access | Usually, if messages sync into the ATS | The company has a monitored hiring channel |
| Per-job ATS address | Yes, if replies are supported | The team can retain the ATS thread | No personal mailbox access is required | The address is procedural but usable |
| No-reply address | No | There is no candidate reply thread | No | Questions aren't welcome |
Sender choice affects more than tone. It determines whether a candidate can correct an attachment, answer a scheduling question, or tell you that another offer has changed their timeline.
A founder described the cost plainly: "I didn't reply to people who weren't a fit, I lost candidates mid-process (good ones, probably)."
Automation can create a different problem when nobody can trace its source. One employer wrote, "It is a little difficult to manage automated messages. We sometimes cannot locate where the message originated to turn it on or off."
When your own address is the right sender
Use your work address for messages that invite a personal response. Interview follow-ups, requests for clarification, offer discussions, and updates after a long process all fit.
Candidates can reply without changing channels, and the sender is easy to recognize. The ATS should retain the thread on the candidate record so colleagues can see the hiring context without gaining access to unrelated mail.
A personal address does create a continuity risk. If one recruiter leaves or loses access, the company still needs the hiring record. Check whether the ATS preserves messages already attached to candidates and whether another authorized team member can continue the conversation.
When a dedicated hiring address is better
A shared address such as jobs@ works when several people monitor applications. It separates hiring mail from personal correspondence and gives the company control when responsibilities change.
A per-job address adds routing. Applications for an operations role can land in that job without someone manually forwarding each resume. This is useful when the same team has several open roles with similar titles.
Shared access needs clear ownership. Decide who answers messages, who can connect the account, and how the ATS handles mail that doesn't match an open job.
Why a no-reply address costs you candidates
Candidates reply for practical reasons. They may need to replace a resume, correct a phone number, disclose a scheduling conflict, or ask which interview format to expect.
A no-reply address blocks that path. The candidate has to find another contact, start a new thread, or give up. Your ATS may still show that an email was sent, while the hiring team misses the response that would have kept the process moving.
What should sync do with an application email?
An application email needs more than storage. The system should identify the intended job, create or update the candidate record, attach the resume, and retain the original thread.
At minimum, check how a vendor handles these cases:
- The email contains a PDF or DOCX resume and names a specific role.
- The candidate has already applied to the same job.
- The resume lacks a required answer or contact detail.
- The email could match several open jobs.
- The message doesn't match any job.
Duplicates should be detected by candidate and job, not by name alone. Two people can share a name, and one person can apply to separate roles.
Unmatched mail shouldn't disappear into a general inbox. It needs a review queue where your team can assign it. The vendor should also explain whether unmatched messages trigger any automatic response. Silence is safer than sending the wrong job acknowledgement.
Gmail or Microsoft 365, what changes?
Both Gmail and Microsoft 365 work accounts can connect through OAuth, but address behavior may differ by provider. Ask the vendor to explain those differences before you publish an application address.
The settings should separate sending, inbox access, and calendar access. A calendar permission doesn't automatically explain what the product can read from email. Likewise, permission to send doesn't prove that candidate replies will return to the ATS.
Confirm these details:
- Whether mail is sent from your connected work address.
- How incoming messages are matched to a job.
- What happens when no job can be identified.
- Whether the provider supports per-job address tags.
- How polling affects the delay before a message appears.
Don't accept "works with Outlook" as the full answer. Ask specifically about Microsoft 365 work accounts, incoming mail, outgoing mail, calendar permissions, and job routing.
How do automated stage emails stay human?
Stage automation should handle predictable notices while leaving judgment and personal replies with the recruiter.
Write each message in your own voice. Give the automation a name tied to its stage, such as "Interview confirmed" or "Portfolio review update." That makes the source easier to find when someone needs to change or stop it.
An optional delay can prevent an email from arriving the moment you move a candidate. That pause gives you time to correct an accidental stage change. It also avoids making every message feel mechanically attached to a pipeline action.
Keep rejection handling separate. A stage move shouldn't silently send a rejection unless you deliberately configured and reviewed that behavior. A practical guide to rejecting applicants without ghosting can help your team set the message, timing, and ownership. For routine updates, documented stage-move emails make each trigger easier to audit.
What should you ask a vendor before connecting a mailbox?
Mailbox access deserves a direct security review. Start with the OAuth scopes. Google's read permission can cover the whole mailbox, so ask what the product reads, which messages it stores, and how it limits processing to hiring activity.
Then ask:
- How are OAuth tokens encrypted?
- Who in the organization can connect or disconnect a mailbox?
- What stored data is removed after disconnection for each provider?
- Are applicants retained after raw email content is cleared?
- Can outgoing messages use your connected address?
- Does the integration poll for mail or use push delivery?
- How are unmatched messages handled?
Provider behavior may differ. Don't assume that disconnecting Gmail and Microsoft 365 produces the same deletion result. Request a provider-specific answer in writing.
For one example, see how Curriculo protects mailbox and calendar tokens: it uses AES-256-GCM encryption for them.
How does Curriculo handle recruitment email?
Curriculo's Email Agent gives each job a default apply address in the format engg+<6-character job code>@curriculo.me. It works without a connected mailbox.
Applicants who use that address can receive one automatic round of questions if required details are missing. The questions stay in the same thread. Once the required details arrive, the candidate receives "Application received." PDF and DOCX resumes are supported.
Emails found through a connected Gmail or Microsoft 365 work inbox can become applicants when they match an existing job. Unmatched mail goes to Review needed and triggers no automatic candidate email. Connected inbox applicants don't receive the automatic questions or acknowledgement used by the default apply address.
With Gmail connected, a job's apply address can use you+CODE@yourdomain. An organization can connect up to five Gmail mailboxes. Microsoft 365 uses the connected work address without a per-job code. Sending from that Microsoft 365 work address is supported.
Your team can reply from the candidate's Conversation tab, with the message sent through the connected address. Curriculo's Settings page separates Email Sending, Inbox Sync, and Calendar. The Microsoft card labels its calendar permission "Calendar & Teams." An organization admin connects these under Settings, then Organization. The Email Agent setup guide covers the connection steps.
Curriculo ATS scores every candidate from 0 to 100 against your job, with a written AI summary of the fit.
The Email Agent and mailbox connection are available on Starter and Pro. Starter is free forever. Pro is $50/mo early-bird, which is 50% off the $100 list price. Neither plan has per-seat fees. You can start free on Starter.
FAQ
What is two-way email sync in an ATS?
Two-way email sync lets an ATS send messages through a connected mailbox and bring candidate replies back to the relevant record. The conversation should remain attached to the candidate and job. Check whether the vendor supports both directions, since some integrations only send email or only import selected incoming messages.
Can candidates reply to emails an ATS sends?
They can when the ATS uses a monitored personal, shared, or per-job address and supports incoming replies. They can't answer a no-reply address. Before choosing a vendor, test the full path from an outgoing message to the candidate's response and confirm where that response appears for the hiring team.
Does connecting Gmail give an ATS access to my whole inbox?
Google's read scope can cover the whole mailbox. Ask the vendor what its software reads, how it identifies hiring messages, what content it stores, and what happens after disconnection. A product may process only hiring-related mail while still requiring a broad provider permission, so the written data-handling explanation matters.
Does recruitment email sync work with Outlook and Microsoft 365?
It can work with Microsoft 365 work accounts, but the behavior may differ from Gmail. Ask about sending, inbox matching, calendar access, job routing, and unmatched messages separately. In Curriculo, Microsoft 365 sends from the connected work address and uses one plain address without Gmail-style per-job codes.
Which recruiting agents integrate with Gmail or Outlook?
Ask whether the recruiting agent reads a connected work inbox or only monitors a dedicated apply address, and confirm which messages it sends automatically, such as questions or acknowledgements. Also check how replies, unmatched mail, and job routing work for each provider. Curriculo's Email Agent works with Gmail and Microsoft 365 work mailboxes, and per-job codes apply on Gmail only.
Is email sync included on Curriculo's Starter plan?
Yes. Curriculo's Email Agent and mailbox connection are available on Starter and Pro. Starter is free forever, while Pro is $50/mo early-bird, which is 50% off the $100 list price. There are no per-seat fees. An organization admin can connect a supported work mailbox under Settings, then Organization.