When InMail isn't enough

Effective multichannel outreach beyond InMails.

Recruiters bounce across three tools while candidates ignore one channel and find yours in week three.

MartyHR

Cadence — branches on no-reply

Day 1 Email AI-personalized opener
Day 4 LinkedIn Connection request
Day 7 SMS Short follow-up
Day 14 Voice Call task (manual)

Sample 4-step cross-channel cadence — UI mockup

6

outreach channels

12-step

cadences with conditional branching

AI

personalization at send-time

1 unibox

every reply, every channel

Where one-channel outreach falls short.

Reply rates fell year-over-year

Cold email and InMail reply rates have dropped as recruiters crowd the same channels. Single-channel sequences die when candidates don't check that channel.

Your stack fragments the workflow

A cold-email tool for email, LinkedIn for messages, a spreadsheet to track who's where. Candidates fall through the gaps between tools.

One channel, one chance

Email-only sequences stop the moment a candidate ignores email. Switching channels manually means rebuilding the sequence and missing the timing window.

No safe-sending guardrails

Sending too many cold emails from one inbox kills your domain reputation. Most outreach tools leave that math to you.

Reach candidates on the channel they actually answer.

Sequence candidates across email, LinkedIn (messages, voice notes, connection requests, profile visits), SMS, WhatsApp, Telegram, and direct calls — up to 12 steps per sequence. Each step runs automatic (system-sent) or manual (queued for the recruiter as a task with a soft pause until they complete it).

Conditional triggers branch the sequence on response. If email gets no reply after three days, the sequence switches automatically to a LinkedIn connection request, then SMS if the candidate is still silent.

Personalized at scale, without spam-folder risk.

AI personalization runs inline. Drop {*ai: write a one-line opener about their work at {{company}}*} into any message and the system generates the line at send time using the candidate's profile data. Dynamic variables fill names and company; spintax {Hi|Hey|Hello} shuffles greetings to protect deliverability.

Safe-sending is built in: per-channel daily limits (Gmail 100, Outlook 75, LinkedIn 10 connections plus 30 messages), randomized 5–9 minute delays between sends, suppression lists at company/candidate/location level, and 30-day cooldowns between accounts contacting the same candidate.

Built so positive replies never cool off.

Sequencing the candidate is half the work. Reading the reply on the right channel — before they go cold, before a teammate double-touches, before the context gets lost — is the other half.

The unibox is where MartyHR closes that gap. Every reply on every connected channel lands in one threaded inbox per candidate, sentiment-tagged, with auto-unenroll the moment they respond.

MartyHR

One thread, every channel

Anna Müller

Email

Yes, interested. When can we talk?

Anna Müller

LinkedIn

Thanks for connecting!

Anna Müller

WhatsApp

Friday at 3pm CEST works.

One thread per candidate, every channel, sentiment-tagged.

Catch positive replies in minutes, not days.

Sentiment auto-tags every reply positive, neutral, or negative. Positive replies push to your Slack or Teams channel of choice the moment they land — so a Friday-evening “yes, interested” doesn't cool off over the weekend.

Never double-touch a candidate again.

The moment a candidate replies on any channel, every active sequence stops across the team. Two recruiters can't accidentally email the person who already answered the third one's LinkedIn DM.

See the whole conversation, not one channel.

Replies thread by candidate, not by tool. Email, LinkedIn, WhatsApp, SMS — the full back-and-forth lives in one inbox per candidate, so you walk into every follow-up with the context already assembled.

Triage by intent, not by inbox order.

Filter the unibox by sentiment to surface qualified replies first. Skip the auto-replies and unsubscribes; act on the responses that move a placement forward.

Frequently asked questions

How does MartyHR avoid the spam folder? +
Per-channel daily limits (Gmail 100, Outlook 75, LinkedIn 10 connections plus 30 messages), randomized 5–9 minute delays, suppression lists at company/candidate/location level, and 30-day cooldowns between accounts contacting the same candidate.
What happens if a candidate replies on a different channel than the sequence step? +
Auto-unenroll. The active sequence stops the moment any reply lands — regardless of channel — and the conversation joins the candidate's threaded unibox. No double-touching across tools or teammates.
Which channels' replies show up in the unibox? +
Email and LinkedIn at launch. WhatsApp and SMS planned. Voice-call transcript threading is on the roadmap.
How accurate is the sentiment classification? +
It's a recommendation, not gospel. Recruiters override freely; the system learns from corrections per workspace. Positive replies push to Slack/Teams in real time so qualified responses don't cool off.
Can I bring my own LinkedIn account, or does MartyHR use a shared one? +
Bring your own. Every recruiter connects their own accounts via Unipile-hosted auth. No shared sender pool, no risk of cross-customer cross-pollination.
Is the AI personalization GDPR-compliant for B2B recruiting? +
Outreach runs on a legitimate-interest basis. Suppression lists at country, company, and candidate level plus a GDPR-deletion mechanism are built in.

Reach the next candidate on MartyHR.

MartyHR opens to design partners on the launch list. Get a 30-minute project setup call with the founding team, design-partner pricing, and direct line on the roadmap.

Join the launch list