Some tools let one person send candidate sequences from a colleague’s inbox. A candidate sequence is a series of outreach messages that goes out to a candidate automatically, one step at a time. When that colleague is a hiring manager, the hiring manager’s name goes out on an email they never sent. The sender line doesn’t show who pressed send. The candidate sees the hiring manager’s name and replies to them.

This article lists nine tools whose own pages, read on 25 and 29 September 2026, document sending from a colleague’s mailbox, and Metaview is one of them. The table says what kind of product each tool is, so you can tell whether it may already be your applicant tracking system or sits beside it. Each entry gives the vendor’s name for the feature and quotes any limit its page states. Metaview is first because this is Metaview’s blog, and the other eight are in alphabetical order. I’d send from a colleague’s inbox only when that colleague has agreed to the message, and only when the replies are answered by the person whose name is on them or handed over openly. The questions after the entries go to all nine.

When one person sends sequences for several colleagues.

This list is built around one role, usually a coordinator’s or a sourcer’s: one person, several mailboxes. They write and run sequences for several recruiters or hiring managers, and each sequence goes out from the mailbox of the colleague it speaks for, so the candidate sees that colleague’s name. How to write those sequences is covered in Metaview’s guides to candidate outreach and personalizing recruiting outreach emails, so this list sticks to whose name they go out under.

Nine tools, and what each page says about the send.

Each vendor has its own name for the feature, from email sharing to “Send For,” and that name is the term to use when you ask each vendor about it. The table also says what kind of product each tool is, in terms taken from the vendor’s own pages, because some of the nine are applicant tracking systems or add-ons to one, and others are sourcing or outreach tools that work beside the system a team already has. Wider roundups of outbound recruiting tools and artificial intelligence (AI) candidate outreach platforms compare outreach products on other criteria.

The table doesn’t cover permission, replies, who can see a sequence, or sending limits, because I’d want those four answers from someone at each vendor, in a demo, before the first send. The four questions that follow the entries ask for them. The steps before the send are left out too, because they’re covered in the lists of sourcing tools for recruiters and email finder tools.

Metaview Outreach.

Metaview Outreach is the part of Metaview that sends candidate sequences as automated email. Its mailbox delegation lets a recruiter send on behalf of teammates.

Ashby.

Ashby sells what its homepage calls “all-in-one recruiting software,” and an applicant tracking system is one of its parts. The feature is called email sharing, and Ashby’s help center puts it in one sentence: “Ashby supports sharing your company email with other users to allow them to send emails on your behalf.” Once sharing is in place, the same page says, a “From” dropdown lets you choose an alternate email address when you send an email or a sequence in Ashby. For sequences, it adds a limit on aliases: “No-reply or default shared email aliases cannot be used when sending sequences.”

Fetcher.

Fetcher is a candidate sourcing tool: its homepage says “Sourcing candidates just got easier with Fetcher” and lists applicant tracking systems among its integrations. Its help center calls the feature “Send As” and says Fetcher “provides a simple and easy way for search Owners to ‘Send As’ other members of their teams.” A search Owner is the Fetcher user who owns a Search, the place where Fetcher keeps a search’s candidate profiles, criteria, and email templates. Several Fetcher users can work on one Search together. The sequence itself is an email campaign built from touchpoints, and Fetcher’s templates page sets its length: campaigns “have a default of three touchpoints,” and “You can also send as few as one touchpoint, and as many as six.”

Findem.

Findem is an AI product for hiring, retaining, and workforce planning. Its homepage describes it only in those broad terms, as “AI that delivers deep human insight so you can hire, retain, and plan with confidence.” Its help article calls the feature “Sending Campaigns from Multiple Senders” and sets the sender one step at a time: “When setting up multi-step email campaigns, you can choose who sends each individual step.” The same article marks where that stops: “This functionality applies to sourcing campaigns only.” It adds a condition for teams on its Gmail integration: “Threading is automatically disabled if you add a second sender.” Threading is what keeps a campaign’s emails together as one conversation in the candidate’s inbox. If a hiring manager sends a later step, raise that line in Findem’s demo when you ask where the candidate’s reply lands.

Gem.

Gem calls itself “the AI-first recruiting platform,” and its homepage offers it two ways: run recruiting end to end in Gem, with its own applicant tracking system, or add Gem’s tools on top of the one a team already has. Its name for the feature is Send On Behalf Of, and its help center describes it this way: “With Gem, you can send email sequences on behalf of a teammate using Send On Behalf Of (SOBO). This helps teams coordinate outreach while keeping messages sent from the teammate’s inbox.” The division of work is spelled out: “You can set up the message templates and schedule, but the emails are sent directly from your teammate’s inbox.” The page sets two limits. “SOBO only works with email sequences.” So InMail and text message sequences are out. The second limit is the domain: “You can only send messages from email accounts on your own domain.”

Greenhouse Sourcing Automation.

Sourcing Automation is, in Greenhouse’s words, “an add-on product in Greenhouse Recruiting,” and Greenhouse describes what it sells as applicant tracking software. In Sourcing Automation, the sequence is a campaign pool, which Greenhouse’s help center calls “the primary function of Sourcing Automation”: each step in a campaign pool is an email sent to a prospect automatically, at the cadence you set. Greenhouse documents “Send on behalf of” for Sourcing Automation: “Sourcing Automation users can send campaign pool emails on behalf of other users in your organization or on behalf of an email alias.” According to the same article, once permission is in place, their address shows up in the “From” dropdown whenever an authorized user configures senders for a campaign pool step. On aliases, the page is specific: “Sending on behalf of email aliases is available for Gmail accounts only.” It also lists the feature for certain subscription tiers, so availability depends on your Greenhouse plan.

Juicebox.

Juicebox is a sourcing tool, with “Agents that source for you” as its homepage headline, and the same page lists the applicant tracking systems it syncs with. It sets a mailbox for each step, and its sequences documentation shows it with a hiring manager: “if I want step 1 to come from my mailbox and step 2 to come from my Hiring Manager’s email, I would select my mailbox for step 1, and my Hiring Manager’s mailbox for step 2.” Its email integrations page calls a colleague’s mailbox a SOBO mailbox, which lets you “send on behalf of other stakeholders, such as hiring managers, executives, or teammates” from that person’s own address. The sequences page draws the channel line: “Only emails will be automated by Juicebox.” How many mailboxes you can connect depends on your plan.

Lever.

Lever is, in its homepage’s words, “a modern applicant tracking system.” It calls its version “Send For” and scopes it in one sentence: “Lever’s ‘Send For’ feature allows you to send emails on behalf of other users in your Lever environment including recruiters, hiring managers, and executives.” The sequence here is a Nurture campaign, which Lever describes as a way “to send email campaigns with multiple touchpoints to passive candidates in your pipeline.” The Nurture page connects the two: “If you have Send For permissions for other users in your Lever environment, you can include emails from them in the touchpoints of your campaign.” Lever’s pages mark two limits. “Note that it is not possible to send emails on behalf of another user as part of an automation workflow.” And: “Keep in mind that if you have enabled the Send emails as replies setting for the campaign (via the checkbox at the top of the campaign editor), email touchpoints sent using a Send For will not be included in the email thread.” That second line is the one to raise in Lever’s demo when you ask where the candidate’s reply lands.

SeekOut.

SeekOut’s homepage presents an “AI Recruiting Platform” for “Outbound sourcing, inbound evaluation, and personalized outreach in one platform,” and says it integrates with major applicant tracking systems. SeekOut runs the send through its Candidate Outreach feature, and its help center starts there: “All SeekOut accounts include the ability to send automated, multi-step email campaigns using the Candidate Outreach feature.” SeekOut’s page calls the colleague’s address a “Send on Behalf” email: “You can also link multiple email addresses in the event that you want to send campaigns on behalf of your hiring manager or another recruiter.” The same page says the sending address can only be chosen before a campaign starts, and that “Candidate Outreach does not support using alias emails to send messages.”

Questions to ask before you send candidate sequences from a colleague’s inbox.

These four questions go past what the entries quote to what happens around the send, and the answers decide how a sequence in someone else’s name lands. Put them to every vendor on your shortlist before the first send, Metaview included:

1. What permission does sending from a colleague’s mailbox need, and who grants it?
2. Where does the candidate’s reply land, and who answers it?
3. Who can see the sequence, including the colleague whose name is on it?
4. When one mailbox sends for several sequences, whose sending limits apply, and do those sequences share them? A sending limit is the cap an email provider puts on how much one mailbox can send.

The second question is the one I’d press hardest, because it’s where the candidate’s expectation meets the software. Metaview’s piece on why candidate replies get lost after outbound outreach sets a rule I’d apply to every sequence sent in a colleague’s name: “Every reply needs an owner, a next action, and a due date.”

The candidate expects the person named on the email.

A candidate who gets a message from a hiring manager expects the hiring manager, and expects them to be there when the reply goes back. That’s why my rule has two halves: the colleague agrees to the message before it goes out, because it’s their name on it, and the named person answers, or whoever takes the thread over says so in the first reply. If Metaview’s Notetaker is on the intake call where the hiring manager signs off on their name going out, it captures every spoken word, so what they agreed to is on record before the first send.

Both halves protect the working relationship that comes with a hiring manager’s name. In Metaview’s 2026 AI & Hiring Alignment Report, a survey of 505 recruiting leaders and hiring managers at companies with 200+ employees across North America, Europe, the Middle East, and Africa, 58% of them said they sometimes or often wish they could work around their counterpart. The same report measured the relationship from the other direction too: 90% of the same 505 respondents rate their working relationship as good or excellent. Read side by side, the two figures describe a relationship most of them rate as good or excellent and many of them still, at least sometimes, want to work around. That’s the tension Metaview’s piece on recruiter and hiring manager alignment takes apart. The survey measured the working relationship, not outreach, so neither number describes an email. I read them only as a reason for the two colleagues to agree before either name goes on a sequence.

Two episodes of Metaview’s podcast, 10x Recruiting, cover the discipline behind that rule. Chris Adams, Uber’s first sourcer and the founder of TalentHerder, took it from a sourcer’s side, and Metaview’s recap of his episode spells it out: before hiring-manager outreach starts, the hiring manager commits to taking the calls it produces, and if they can’t, that lane stays closed. The recap puts the cost of skipping that step in one sentence: “Sending a hiring-manager alias message and then ghosting the responder destroys the trust the first message was supposed to build.”

Chandler Martin, Zocdoc’s senior director of people, comes at the same practice from the other direction in episode 24, where he makes the case for disciplined outbound. For senior roles, Metaview’s recap of the episode describes the chief technology officer or chief executive sending the first message: “The recruiter owns the orchestration and follow-up; the executive owns the first-touch outreach.” The recap frames that as “a willingness to swap the sender,” and it doesn’t say whose inbox the first message goes out from. Either way, the executive’s name is on it and the recruiter follows up, so both halves of my rule apply. Did the executive agree to the first message, and will the candidate know when the recruiter takes over?

In practice, an open handover takes one line in the first reply from anyone other than the named sender: who they are, and why they’re the one writing. Then the candidate never has to guess who’s on the other end.

Chris Adams’s episode, the first of those two, is below.

Answering the replies these sequences produce takes recruiter time. A Workleap case study shows where one team found more of it. It says Workleap’s recruiters can invest more time in “building relationships, improving candidate experience, and proactively sourcing top talent,” and that time came out of screening. “It’s reduced my screening time by up to 50%,” says Johnny Drexhage, a senior recruiter at Workleap, about Metaview’s Application Review, which reads each application against the role’s criteria. Of those three, proactive sourcing is the one that can go out in a colleague’s name, and when it does, the candidate should be talking to the person whose name they see.

Shahriar Tajbakhsh, one of Metaview’s co-founders, has put the value of those conversations in one line:

So take the four questions into every demo on your shortlist, write down each vendor’s answers in its own words, and compare them before anyone’s name goes on a sequence.