Inbound
The board alerts arrive all morning. Nobody opens the afternoon's.
Candidates reach a recruitment business as email — a board alert, a CV a colleague forwarded, a referral from a client. They are read in order until about eleven, and the rest is archaeology.
How it works
Your own intake address, and adapters that know the senders.
You get an address to forward to, or to set as the destination on your board alerts. What arrives is read by whichever adapter recognises it — the major job boards each have their own, and there is a catch-all for any email that simply carries a CV.
Recognising the sender matters because a board alert is not a CV. It is a layout, and reading it as prose loses the half of it that is structured.
- New candidate14name and a way to reach them
- Someone you already had9matched on email or phone — not a second copy
- Attached to a live role6the subject named a role we could resolve
- Not source-shaped5routed here, but not an application
- Too incomplete to insert3no name, or no way to contact them
What it does with each one
Mostly, it declines.
An intake that accepts everything is a database nobody trusts by March. So the rules are strict and the outcomes are recorded.
A person needs a name and at least one way to reach them, or nothing is inserted. Somebody you already hold is matched on their email or phone and becomes the same person rather than a second copy. And where the subject line names a role you have open, the person is attached to it rather than landing in a general pile.
- Every outcome is a named state —
Created, matched to somebody you had, attached to a role, refused as not an application, refused as too incomplete. Not a silent success rate.
- The name is worked at —
From the sender's display name, the CV's filename, or the subject — in that order, and only where the subject looks like a person rather than "My CV".
- Phone and city resolve on the way in —
A bare local number resolves to its country; a neighbourhood resolves to its city. The same pass that runs on an uploaded CV.
Two things to know before you route your alerts here
Both of them limits.
›Does the attached CV become the candidate's resume on file?
No. The attachment is read to help identify the person, and it is not stored as their resume. If the document itself matters to you — and on a senior role it will — attach it on the record or use the browser extension. This is the honest gap on this page.
›Do these arrive in the recruiter inbox for triage?
No. Careers-page applications queue in the inbox; email-captured people are created directly as records. Two doors, two levels of trust, because a CV your colleague forwarded has already passed a human.
›Will it create duplicates of people we already have?
No — a match on email or phone resolves to the existing person. The outcome says which happened, so you can see whether a morning produced fourteen new people or fourteen copies.
›Which boards are recognised?
The major ones, each with its own reader, plus a catch-all for any email carrying a CV. Send us a week of your real alerts and we will tell you precisely what happens to each sender.
›What if the email is not an application at all?
It is refused as not source-shaped and nothing is written. Newsletters and replies do not quietly become candidates.
Book a demo
Forward us a morning of board alerts.
We will show you the outcome on each one — including the ones it refuses, which is the number worth looking at.