The B2B cold outbound playbook for 2026 is a short multichannel sequence: a LinkedIn connection request, a same-day WhatsApp intro, a WhatsApp follow-up on day 3 and one email on day 7. LinkedIn builds recognition, WhatsApp carries the conversation, and email covers contacts without a phone number.
| Touch | Day | Channel | Action | Purpose |
|---|---|---|---|---|
| 1 | 1 | Connection request (no note, or short contextual note) | Low-friction warm intro. No pitch. Just visibility. | |
| 2 | 1 (same day) | Short intro message referencing LinkedIn | Immediate engagement. LinkedIn accept is fresh in mind. | |
| 3 | 3 | Follow-up with value hook or social proof | Re-engage non-responders. Give them a reason to reply. | |
| 4 | 7 | Email backup if no WhatsApp reply | Cover contacts who saw the message but didn't reply on chat. |
Send a connection request. No pitch in the request, the goal is just to become visible. If they accept, the "just connected" mental context makes Touch 2 feel organic.
Template (no note): Just the connection request. Acceptance depends heavily on how well the prospect fits your ICP, so track it per list.
Template (short note, optional): "Really admire {{company}}'s work in {{industry}}, would love to connect." Only use a note if there's genuine context; a generic note adds nothing.
Send within 2-4 hours of the LinkedIn accept. Reference the connection to create context. Keep under 80 characters.
Template: "Hey {name}, just connected on LinkedIn. Saw {custom1} is growing fast. Quick question about how you handle {custom2}?"
Why same day: The LinkedIn notification is still in their mind, so your WhatsApp message has context instead of arriving from nowhere. Waiting a day loses some of that recognition.
If no reply to Touch 2, send a value-forward follow-up. Don't reference the fact they didn't reply, just provide a reason to engage.
Template: "We helped [a company like {custom1}] [real result with {custom2}]. Happy to share how if you're interested." Only quote a result you can back up. Add a link only if it's relevant.
If no reply to either WhatsApp message, send a single email. This also covers contacts whose WhatsApp number you couldn't find or who prefer email. Keep it short: under 80 words is a good rule.
Template: "Hi {{first_name}}, I reached out on WhatsApp a few days ago. Wanted to share one thing: {{one_value_sentence}}. Let me know if it's worth a quick chat."
There is no trustworthy public benchmark for cold WhatsApp reply rates, and figures quoted online are rarely sourced. Measure your own, per channel and per touch:
| Metric | How to calculate it | What moves it |
|---|---|---|
| LinkedIn accept rate | Accepted requests ÷ requests sent | ICP fit, profile quality, note or no note |
| WhatsApp reply rate | Contacts who replied ÷ contacts messaged | Targeting, the first line, message length, timing |
| Email reply rate | Replies ÷ emails delivered | Deliverability, relevance, brevity |
| Meeting rate | Meetings booked ÷ contacts in the sequence | Offer, follow-up speed, how you ask |
Run the 3-channel version against a 2-channel version (LinkedIn plus email) on two halves of the same list. If WhatsApp earns its place, you will see it in replies and meetings within a few weeks.
Wassuply handles the WhatsApp layer of the multi-channel sequence:
The rest of the stack: LinkedIn (manual connection requests or Sales Navigator), email (your existing email tool for Touch 4), and Wassuply for Touches 2 and 3. New numbers need warm-up first: plan the first 30 days of each new number before the sequence goes live, and read our guide to avoiding WhatsApp bans before you scale. Tool cost for the WhatsApp layer: a one-time $397 early-bird licence.
Unlimited accounts. Smart delays. Anti-ban protection. Powers LinkedIn → WhatsApp → Email.
Get lifetime access · $397Related reading: LinkedIn vs WhatsApp for B2B and cold calling vs WhatsApp.