When you run a campaign with multiple senders, Recruiterflow doesn't assign recipients randomly. It uses prior email history to pick the sender most likely to get a response — and falls back to round-robin when there's no history to go on.
​

Here's the logic it follows.

If a recipient replied to an email from a specific team member in the last 6 months, that team member is assigned as the sender for any new campaign emails to that person. The next available recipient in the queue is then assigned to the next sender in round-robin order.

Example: You're running a campaign with three senders — Alice, Bob, and Charlie. Candidate Sarah replied to Alice's email 3 months ago. When Sarah comes up in the campaign, Alice is automatically assigned as her sender — even if Bob or Charlie are next in the rotation. Sarah sees a familiar name, which increases the chance she opens and responds.

If a recipient hasn't replied to anyone on the team in the last 6 months, the campaign distributes that person to senders in order — cycling back to the beginning once everyone has been assigned.

Example: You have 10 recipients with no prior engagement and three senders: Alice, Bob, and Charlie. The assignment goes: Recipient 1 → Alice, Recipient 2 → Bob, Recipient 3 → Charlie, Recipient 4 → Alice again, and so on. This spreads the load evenly and reduces the risk of any single account triggering spam filters.

Sending from a familiar name meaningfully improves open and reply rates. Recruiterflow's sender assignment handles this automatically — you don't need to manually assign senders per recipient or remember who last spoke to whom.

For campaigns with multiple senders, see also: Adding Multiple Senders to a Campaign.