Sourcing that feels
personal at machine scale.
Sourcing tools blast generic notes and burn pipelines. The candidates worth hiring ignore them. A Loomal sourcing agent reads each profile, drafts a personal note, and sends from a real recruiting identity — at the volume one recruiter could never sustain alone.
API Primitives used
mail_sendReach out from a real recruiter address
Each outbound carries the recruiter's agent identity. Candidates see a verified sender, not a sourcing tool's blast domain.
mail_list_messagesCatch the response
Replies thread back into the agent inbox. Agent classifies interest and decides whether to schedule, nurture, or close.
calendar_createBook the intro call
Interested candidates get a calendar event with the recruiter immediately — no scheduling-link friction.
Sourcing tools poisoned the channel.
The best engineers and operators get 20 sourcing emails a week. They've all learned to spot the format. Generic openers, fake personalization, no real sender — straight to trash. Yet most recruiting teams still use the same broken tools because nothing else scales.
An agent fixes the scale problem without the format. It reads each candidate's actual profile, drafts a note that references real work, and sends from a real recruiter identity. The candidates still notice — but this time they reply.
How to build it.
Personalize each note
Agent reads the candidate's profile, identifies the relevant signal, and drafts a short note that earns attention without the cringe of fake personalization.
mail_sendSend from a real address
Outbound goes from the recruiter's agent identity. DKIM headers verify the sender; the candidate sees a real recruiter, not a tool.
calendar_createBook or nurture
Interested replies get a calendar event with the recruiter. Polite passes get a thank-you and a clean exit from the sequence.
Example prompt
“Source senior backend engineers in Berlin for our infra role. Personalize each note from their GitHub or LinkedIn, send from my agent's address, and book a 20-minute intro call on any positive reply.”
What recruiting teams build.
Engineering sourcing
Agent sources engineers by reading GitHub and tech-blog signal, then sends individualized notes from the recruiter identity.
Executive search
For senior roles, agent drafts the pitch and routes it through the partner for sign-off before sending.
Diversity sourcing
Agent runs targeted outreach into communities and groups with personalization that respects the context.
Re-engagement
Old pipelines get re-opened with new-role pitches, threaded against the original conversation.
Multi-recruiter coordination
Different recruiters run different agent identities so candidates never get pitched twice for the same role.
Why sourcing needs an agent identity.
Sourcing is a numbers game played at human quality. The volume needs scale; the messages need craft. No traditional tool gets both right — they pick scale and lose the candidate, or pick craft and burn out the recruiter.
An agent identity pulls both. The recruiter delegates, the agent runs the volume, and the audit trail proves who said what to whom. Pipelines stay clean, candidates stay engaged, and recruiters spend their time where it matters.
Audit per outreach
Every note, reply, and booking is logged against the recruiter's agent identity.
Candidate data internal
Conversations live in your own inbox, not a sourcing vendor's database.
Recruiter-scoped identities
Each recruiter's agent only sees their own pipeline — no cross-recruiter leaks.
Source the candidates who never reply to tools.
Real sender, real personalization, fully autonomous.