Recruiting candidate reply loop with owned inboxes
The identity and inbound layer for AI recruiting agents that email candidates and process replies. Each sourcing agent gets its own inbox, message.received events, threaded replies, and labels before the ATS write.
The problem
Shared recruiter Gmail and Google Workspace give the agent a human OAuth seat, so replies land in a mailbox nobody owns and credential sharing gets flagged.
Instantly AI Reply Agent and outreach workflows are strong for cold email sequences and mailbox warm-up, not an agent-owned inbox API wired to ATS state.
Nylas Agent Accounts provision agent email and calendar via grant_id, with a calendar-heavy surface and connected-account heritage rather than a recruiting reply loop.
Infraforge and Mailforge optimize per-agent cold outreach mailboxes, DNS, warm-up, and throttle, not thread-state plus ATS reply classification.
Greenhouse, Lever, and Workable built-in email keep candidate history in the ATS but are not programmable per-agent identity or webhook-first agent loops.
The solution
AgentMail is the first email provider built for AI agents.
AgentMail is the identity and inbound layer for recruiting agents that process candidate replies. The ATS stays the system of record.
Dedicated inbox per sourcing agent
Create an API inbox per agent with no OAuth seat so candidates reply to a persistent address the agent owns.
message.received and message.bounced webhooks
Subscribe to message.received and message.bounced so the agent reacts when a candidate replies or a bounce lands, without polling.
messages.reply with message_id
Reply with the inbound message_id so the answer stays in the same thread the candidate already opened.
Labels and Drafts before ATS write
Label interested, not interested, or escalate, and use Drafts for human review before the agent writes stage state to the ATS.
What your recruiting reply agents can do
Outreach
Own the candidate conversation
Each sourcing agent sends from its own inbox so reply reputation and audit history stay tied to that agent, not a shared recruiter seat.
Triage
Classify replies in realtime
On message.received, the agent reads from_, classifies intent, and applies labels before any ATS mutation.
Reply
Stay in the same thread
messages.reply with message_id keeps follow-ups in the candidate thread instead of starting a new conversation.
Handoff
Escalate edge cases to humans
Drafts and escalate labels park hard cases for a recruiter before Greenhouse, Lever, Ashby, or Workable is updated.
AgentMail is built to scale.
Redundant infrastructure spanning multiple regions, so a message to your agent lands even when a region does not.
Provision an inbox in milliseconds. Nothing to verify, nothing to wait on.
Typed SDKs, REST endpoints, and webhooks. Your first send goes out the same afternoon.
Wire the reply loop
Signatures from https://docs.agentmail.to/documentation/examples/auto-reply-agent, https://docs.agentmail.to/webhooks-overview, and https://docs.agentmail.to/sending-receiving-email.
FAQ
Common questions about AgentMail and recruiting candidate reply loop with owned inboxes.
Close to this but not quite your situation? Describe yours and the Workbench draws the blueprint, with a prompt your coding agent can build from.
Agents get a JSON build plan. Humans, use the button on the left.
Give your agents their own inboxes
Free tier. No credit card required. Inboxes ready in under a second.