27 iMessage Templates for B2B Sales Teams (With the Reasoning Behind Each One)

The rule behind all 27: one decision per message#

Sales texts charge decision cost: Who is this? Do I care? Is it worth time? Tuesday or Thursday? Most texts ask four questions and get zero replies.

Keep cost at one decision; two if trivial. This constraint fixes more messages than clever openers. Every template below is short, answerable with one thumb while walking.

Each template comes with three lines: why it works, when to send it, and what to change. Read those before you copy the text. A template you can't explain is a template you'll fire at the wrong moment.

Why do good sales texts get ignored?#

Four message killers: no name so readers can't identify you; links that read as broadcast; more than two lines; questions with multiple answers.

Ask for time only after earning attention.

The rest is timing and voice.

• Wrong hour. 7:40am Monday and 5:30pm Friday both get swiped away. 10am to 4pm on their clock, Tuesday through Thursday, is the boring answer that keeps working.
• Marketing voice. If the words "solutions," "reach out," or "exploring" are in there, it reads as a campaign, and campaigns get ignored.
• No exit. On a cold text, one line telling people how to stop is both a courtesy and a habit that keeps you out of trouble.
• Token personalization. The same 60 words sent to 400 people with the first name swapped is still the same 60 words.
• Three messages in four days with no gap. Silence between touches does work that words can't.

Speed to lead: text inside 60 seconds#

Harvard Business Review study (March 2011, 1.25M leads): firms contacting within one hour were 7x more likely to qualify. Average response time: 42 hours.

Texting is the only channel where answering in 60 seconds reads as service, not desperation.

• **1. The 60-second acknowledgment.** "Hey Dana, Marcus from Northwind. Saw your pricing request come through. Want the short version now, or should I call in 5?" Why: gives before it asks. When: inside a minute of the form fill. Change: name the exact asset they grabbed.
• **2. The one-question qualifier.** "Hi Priya, Marcus here from Northwind. Quick one before I send anything over: is this for your team or the whole org?" Why: qualifying that feels like service. When: inbound you can't size yet. Change: ask the one question that changes your pitch.
• **3. The two-slot close.** "Hey Sam, Marcus at Northwind. I've got 2:15 or 4:40 open today. Either work? Takes 12 minutes." Why: odd times read like a real calendar. When: demo requests and high intent. Change: the duration, and keep it under 15.
• **4. The after-hours hold.** "Hey Jordan, Marcus from Northwind. Your request came in at 11:40pm so I'm not calling now. I'll try around 9:15, or text me a better time." Why: restraint is rare enough to be memorable. When: nights and weekends. Change: nothing.

Cold open: earn a reply, not a meeting#

A cold iMessage has one job. Get a reply, any reply. Openers that book a meeting on the first message exist, but building a process around them is a mistake. Ask something answerable in three words.

• **5. The trigger open.** "Hey Alex, Marcus from Northwind. Saw you're hiring three AEs in Denver. Are you handling ramp in-house or outsourcing it?" Why: proves you looked. When: within a week of the trigger. Change: stale triggers read as scraped, so keep them fresh.
• **6. The permission ask.** "Hi Renee, Marcus from Northwind. Cold text, so I'll be quick. Worth 30 seconds on how [peer company] cut their no-shows? A no is fine." Why: naming the cold outreach disarms it. When: no trigger to work with. Change: the peer has to be genuinely comparable.
• **7. The right-person check.** "Hey Chris, Marcus at Northwind. Are you the one who owns outbound tooling there, or is that someone else on your team?" Why: decision cost of one, and even a wrong answer hands you a name. When: unverified titles. Change: the function.
• **8. The number open.** "Hi Tanya, Marcus from Northwind. We took [similar company] from [X] booked calls a month to [Y] without adding headcount. Want the how?" Why: a specific outcome beats a description of your product. When: you have a real case study. Change: use their vertical's numbers, never a rounded brag.

Follow-up after no reply: shorter每 time#

Cadence rule: each follow-up shorter than the last, gaps roughly double: day 0, 2, 5, 12. Four touches, then close the loop.

Growing messages read as desperation; growing gaps read as somebody busy.

• **9. The one-liner.** "Hey Dana, still worth a look?" Why: five words, zero pressure, trivially easy yes. When: day 2. Change: nothing. Resist adding context.
• **10. The parked question.** "Hi Priya, guessing this landed at a bad time. Circle back in March, or drop it?" Why: the graceful exit is what pulls the reply. When: day 5. Change: name a real month, not "later."
• **11. The value drop.** "Hey Alex, no reply needed. Here's how [peer] runs their handoff. Steal whatever's useful." Why: the only message in the sequence that asks for nothing. When: day 12. Change: attach something genuinely useful, not a brochure.
• **12. The close-the-loop.** "Hey Sam, I'll stop here so I'm not that guy. If it comes back up, this number reaches me directly." Why: reciprocity, and a surprising share of replies come from exactly this message. When: final touch. Change: nothing.

Post-demo: arm the champion, don't chase them#

Once the call ends, your deal lives inside somebody else's Slack thread. Post-demo texts exist to make your champion's internal job easier. Write things they can forward without editing.

• **13. The forwardable recap.** "Great call Renee. Writing this so you can forward it: [problem in one line], [fix in one line], [one number]. Pricing lands in an hour, anything you want in it?" Why: your champion has to sell this without you in the room. When: within 10 minutes of hanging up. Change: the number has to be theirs.
• **14. The objection pre-load.** "Hey Renee, what's the one question your CFO will ask that I didn't answer today? I'll put the answer in writing." Why: surfaces the real blocker while goodwill is still high. When: same day. Change: swap CFO for whoever signs.
• **15. The held slot.** "Hi Chris, I put a hold on Thursday 11am for the technical piece. Keep it or move it?" Why: a hold is easier to keep than a blank slot is to book. When: right after the demo. Change: name who else should be on it.

No-show recovery: assume collision, not rejection#

Most no-shows are calendar collisions. Somebody got pulled into something at 1:55. Texting wins here because it reaches the person who is currently sitting in the wrong meeting.

• **16. The live rescue.** "Hey Tanya, I'm on the call, no rush. Want me to hang on 5 more or grab a new time?" Why: catches them mid-collision, when a two-word reply still saves the meeting. When: 4 minutes in. Change: nothing.
• **17. The no-blame reset.** "Hey Tanya, looks like we got crossed up at 2. Happens. Want 15 minutes tomorrow, or should I text you next week?" Why: no guilt, two easy options. When: 30 minutes after. Change: strip out any hint of scorekeeping.
• **18. The third strike.** "Hey Tanya, third one that slipped, so I'll take the hint on timing. Text me when it's real and I'll clear a slot." Why: honest without being petty, and it hands control back to them. When: third no-show. Change: nothing.

Pipeline revival: bring a changed fact#

Closed-lost is the cheapest list you own. A revival text works when it carries a changed fact: new feature, new price, new job title on their end. Without one, you're just asking the same question again.

• **19. The changed fact.** "Hey Jordan, we shipped the [thing] you called a dealbreaker last March. Worth 15 minutes now?" Why: gives the message a reason to exist. When: within days of shipping. Change: quote their objection from your notes, word for word.
• **20. The clean-slate.** "Hi Alex, cleaning out old pipeline. Is [project] dead or just parked?" Why: permission to say dead is exactly what makes people say parked. When: quarterly sweep. Change: name their project, not your product.
• **21. The new-seat text.** "Hey Priya, saw you moved to [company]. Congrats. Same problem as last time, or a different one now?" Why: your best buyers are the ones who already sat through your demo somewhere else. When: within two weeks of the move. Change: nothing.

Referral ask: name the person#

Referral asks die when they're open-ended. "Do you know anyone who..." makes the other person do research on your behalf. Name the person you want, or at minimum name the shape of them.

• **22. The named ask.** "Hey Renee, is [name] at [company] the right person for this, or would you point me elsewhere?" Why: naming somebody turns a chore into a yes or no. When: after any positive interaction. Change: do the homework so the name is plausible.
• **23. The post-win ask.** "Hi Chris, glad [result] landed. Who else in your world is fighting the same thing? Happy to just answer questions, no pitch." Why: "no pitch" removes the social risk of making an intro. When: within a week of a visible win. Change: cite the specific result, never "the project."
• **24. The pre-written intro.** "Hey Sam, would an intro to [name] be weird? If not, I'll write the note so you just forward it." Why: removes the work, which is the real reason referrals stall. When: warm accounts only. Change: send the draft inside the hour.

Renewal and expansion: get there before procurement does#

Renewal texts should land 60 days out, while nobody is defensive yet. At day 15 you're negotiating. At day 60 you're still consulting.

• **25. The early check.** "Hey Renee, renewal's 60 days out. Anything you'd want changed before this turns into paperwork?" Why: invites the complaint while there's still time to fix it. When: day 60. Change: nothing.
• **26. The usage nudge.** "Hi Chris, looks like [team] hasn't touched [feature] since March. Want me to run a 20-minute refresh before renewal?" Why: churn shows up in usage long before it shows up on a call. When: 90 days out. Change: pick the feature tied to their original reason for buying.
• **27. The straight-talk expansion.** "Hey Priya, you're at [X] of [Y] seats. Adding the tier now costs less than adding it at renewal. Want the math?" Why: telling somebody the cheaper path buys credibility you'll spend later. When: at 80% of any usage limit. Change: have the math ready before you offer it.

What should you change before you send any of these?#

Three edits: delete the first sentence; replace one generic noun with company-specific detail; run screenshot test: would they send this to a colleague without shame?

Measure the right metric. Reply rate flatters lazy messages ("who is this" counts). Booked appointments that get held pay rent; teams sending through Blue Reacher see 2-3x more.

Scheduled sends fire on recipient clock, delivery states and read receipts show if landed, no A2P registration needed.

Frequently asked questions