Every candidate conversation on the candidate record

Most days a recruiter is doing both. A careful individual note to a candidate they have been courting for six weeks, and a templated update to the forty people who applied to a requisition that has now closed. Splitting those into separate products is how agencies end up with a marketing tool nobody in delivery uses.

Both start from the list. Select one candidate and compose; select forty and the same composer opens in bulk mode, showing exactly how many recipients survive the consent and suppression checks before anything is sent. The count shown is the count that will be delivered, so a recruiter is not guessing about the gap between the filter and the send.

A merge field is a promise that a spreadsheet column will be correct. In recruitment it usually is not: the first name column holds a full name, the role column holds a requisition reference nobody outside your office understands, and the salary column holds three currencies. The result is the message every candidate recognises on sight and deletes.

Surhires merges from the structured candidate and requisition records instead. First name comes from the parsed name field, current title from the normalised title, notice period from the notice field, rate in the currency it was quoted in, and the consultant block from the record owner. Where a field is empty, the template can fall back or the send can be held rather than going out with a visible gap in it.

The composer, the bulk actions and the send pipeline ship today. What is being added for the Wave 1 release is a recruitment-specific template library, so a new desk is not starting from an empty box. The set covers the messages agencies actually send rather than a generic marketing pack: first approach to a passive candidate, availability check, interview confirmation and directions, document chase, post-interview holding message, offer communication, and the rejection that a candidate will not resent receiving.

Templates are editable, versioned and shareable across the team, and a manager can mark one as the house standard without forbidding a recruiter from writing their own. Performance is tracked per template so the desk can see which approach earns replies rather than arguing about it.

Every record carries its consent basis, the date it was captured and the channel it came through, and a suppression state per channel. A candidate can be reachable by email and suppressed on WhatsApp, or suppressed everywhere after asking to be left alone. Unsubscribe and STOP handling writes to that state directly rather than to a list that somebody exports weekly.

The check runs at send time. This sounds like a technicality and it is the whole point: a bulk list built at nine in the morning and sent at four in the afternoon will exclude anyone who opted out during the day. Email footers carry the unsubscribe link and the physical postal address of the sending entity. Whether a particular campaign is lawful in your jurisdiction remains your decision; the product gives you the fields, the enforcement point and the audit trail.

Different candidates answer on different channels, and a desk that only knows how to send email loses the ones who do not read it. Each record can carry a preferred channel, and the composer defaults to it. Email works everywhere. WhatsApp is generally available for the India market at Wave 1 and comes to the US market in Wave 2, once template approval clears.

Whichever channel a message goes out on, it lands in the same activity stream and the same reporting. Outreach sent, reply rate and time-to-first-reply are counted by channel on the Recruiter Performance Dashboard, so the argument about whether email still works becomes a number instead of an opinion.

It is not a marketing automation platform. There are no lead scores, no landing-page builder and no drip campaigns aimed at people who have never heard of you. Candidate communication assumes a relationship exists or is being deliberately started by a recruiter who can explain why.

It is also not a shared inbox replacement for the whole business. Client and vendor correspondence belongs to the client record and to your normal mail client. What lives here is the candidate conversation, because that is the one that has to survive a desk change, an audit and a disputed placement fee.