First WhatsApp message: structure that gets replies
AndySendy academy
← All posts

✍️ How to write a first WhatsApp message people want to reply to

Up to 70% of potential clients are lost on first touch - not because the product is bad, but because the first message tries to sell instead of opening dialog. 82% of WhatsApp message interactions happen within the first hour. If they didn't reply - they probably won't. What makes someone tap the keyboard.


Main mistake: first message as a pitch

Most first messages are sender-centric: "We're company X, we offer Y, here's the link, here's the price" - see when to name the company and why discount in first touch loses. Monologue structure, not dialog.

The reader doesn't know why to reply. Everything's already said. Replying means buy or refuse - both take effort they won't spend.

First message job - get a reply, not a sale. Any meaningful reply - yes, no, not relevant - opens the next step - see first cold message.


Why people reply: three conditions

Operator practice (not official Meta):

  1. Simple question - no long thinking what to write
  2. Short answer - one word, yes/no, a number
  3. Question about them, not you - their situation, task, context

Anatomy of a strong first message

Context → Question about client's situation → Simple next step

Context explains why you're writing this person. Without it, the question looks random.

Question focuses on their situation, not your product. "Are you solving X right now?" beats "We offer solution X."

Simple next step - they know what to do: yes/no, one symbol, confirm or decline.


Open or closed question

Closed (yes/no) - minimal effort. Works on cold B2C - see cold vs warm.

Open ("How do you handle X now?") - fuller reply, better B2B; rigid "1/2" feels like bot script.

Compromise: closed first, open after reply - see follow-up.


Easy opt-out: why "no" is valuable too

"Not relevant - send minus, won't write again" - see handling rejection. Lowers spam reports - easier to type a symbol than Report. Forum data: complaints down 60–70% [unofficial]. "No" still qualifies and cleans the list.


Mini case: situational question vs pitch

Restaurant automation company, cold managers list.

Template A: "Hello! We offer restaurant CRM that boosts revenue 15%. Our site..." - 1% response, ban at send 30 - see ban mechanics.

Template B: "Good day [Name]. At [Venue] do you use order automation or manual checks? Seeing delays?" - 34% response, zero blocks. Pitch strictly step two.

Forum case - no public verified methodology.


What kills response rate

Element Why it hurts
Links in message one Ad marker, no trust yet
Long copy (400+ chars) Closed in 2–3 seconds unread
Multiple CTAs Unclear what to do
Company story before question Focus on sender
Price/proposal in first touch Ends dialog before it starts

Working range 120–200 characters - see message length. 400+ often closed unread.


Why reply matters technically: WABA

Client reply opens 24-hour Customer Service Window - free-form chat without templates - see WABA.

One client reply = 24 hours template-free dialog - whether yes or no.


What you can't guarantee

Community claims not officially confirmed: any reply auto-boosts Trust Score, Meta promotes fast-reply messages, guaranteed antispam linguistic formulas. Use practices that work in observation - don't promise clients hard guarantees.


Three first-message logic formulas

Situation → question "Are you [client situation] right now? Still relevant?"

Context → choice → question "[Name], [context]. Is [topic] a priority now or not yet?"

Confirm → clarify (warm list) "[Name], you asked about X before. Has that changed?"

No universal formula. Test on real list via A/B.


🎯 Next step

Check current template: specific question about their situation? Easy yes/no? No links or product pitch? If any is no - rewrite and compare on small sample.

Conclusion

Practical rule:

First message shouldn't give answers - it should ask a question that's easy to answer.