Why agency recruiting needs a different handoff than internal hiring
Internal hiring teams keep everything in one place because the hiring manager and the recruiter work inside the same system. An agency is structurally different: the recruiter's pool spans multiple clients and multiple searches at once, but each client should only ever see the candidates relevant to their own search, not the agency's broader pipeline or the other searches running alongside it.
Handing over full account access solves the visibility problem but creates a worse one, exposing internal notes, candidates being worked for a competitor, or pricing and process details that have nothing to do with the client's own search.
What an agency actually needs is a way to search its own pool efficiently, assemble a shortlist for one specific search, and send that shortlist out as a standalone deliverable, something a client can open and review without an account, a login, or a view into anything beyond the candidates the agency chose to show them.
How the pipeline supports an agency workflow
- 1
Search the pool by description, not exact keywords
Semantic talent search works from a plain-language description of what a client is looking for, run against the agency's own applicant pool or, separately, the opt-in Intervieux network of consenting candidates.
- 2
Assemble a shortlist for one specific search
A curated list gets built by hand for that client's requirement, kept separate from whatever other searches the agency is running for other clients at the same time.
- 3
Share it as a standalone link, not account access
The curated list goes out through a public tokenized link the client opens directly, with tracking on whether it was actually reviewed, no login and no view into the agency's broader pipeline.
- 4
Hand off a branded report when a client wants a document instead
A branded, self-contained hiring report summarizing the top candidates works as an alternative deliverable, something that leaves the agency's system entirely and gets forwarded as a file.
Features that matter here
Frequently asked questions
Does a client need a login to review a shortlist an agency sends them?
No. A curated list is shared through a public tokenized link the client opens directly, with tracking on whether it was opened, and no account or login required on their side.
Can an agency search candidates from multiple client searches without mixing them up?
Each curated list is built for a specific search and kept separate, so a client only sees the candidates assembled for their own requirement, not the agency's broader candidate pool.
What's the difference between a shared link and a hiring report?
A shared curated list stays inside the platform's link and is trackable for opens. A hiring report is a self-contained branded document, generated with candidate emails deliberately left out, meant to be forwarded as a file outside the platform entirely.
How does talent search help across many different client requirements?
Semantic search works from a plain-language description of what a client wants, rather than requiring an agency to build a new set of exact keyword filters for every distinct search.
Does a candidate know their profile is being searched by an agency?
Only candidates who opted in to the consent-gated Intervieux network are discoverable that way, and their profile stays hidden unless their most recent consent record grants visibility, so nothing gets searched without the candidate's own opt-in.
Can a shortlist for one client include a note explaining why each candidate was chosen?
A curated list is built by hand, one candidate at a time, so a recruiter can order it deliberately and attach their own read of each candidate rather than sending an unsorted export.
Related pages
Give every client a shortlist, not a login
Search your pool by description, build a shortlist for the search, and hand it off as a link or a report.