Candidate pipeline updates

As interviews and screenings happen, a Beam agent reads the outcome and moves each candidate to the correct stage inside Recruit CRM. Triggered by a status note or a completed step, it applies the agency's approved rules for advancement, records the reason, and notifies the assigned recruiter. Stalled candidates are surfaced so no one is forgotten in the pipeline. When feedback is contradictory, a candidate qualifies for two roles at once, or a rule does not fit the situation, the agent leaves the record untouched and asks a recruiter to decide the next move.

Job and client record sync

Agencies juggle many open roles, so a Beam agent keeps job and client records in Recruit CRM current as details change. When a hiring manager sends an update, it reads the message, aligns it to the right job, and updates fields like status, salary band, or requirements under approved rules. It then notifies the owning consultant of the change. Requests that alter commercial terms, conflict with an existing agreement, or lack a clear matching job are escalated to a person, who confirms the change before any record is altered.

Candidate sourcing and dedupe

New applicants arrive from many channels, so a Beam agent reads incoming profiles, checks them against Recruit CRM, and adds those that are genuinely new. It applies the agency's rules for required fields, tags, and ownership, then writes the candidate record where permissions allow. Likely duplicates are grouped rather than merged blindly. Profiles with partial data, an uncertain match to an existing contact, or conflicting employment history are routed to a recruiter, who decides whether to merge, keep, or discard the profile before anything is finalized.