There is a category of lost sale that never shows up in your analytics: the shopper who had one question, could not find a fast way to ask it, and left. No cart, no event, no trace.
For anything above impulse price — apparel with sizing, made-to-order goods, technical products — that group is larger than most merchants assume.
Why the contact form does not work
A contact form asks someone to switch modes: compose a message, give an email address, and wait an unknown amount of time for a reply that lands in a different app entirely.
That is a lot of friction to resolve one question about whether a jacket runs small. Most people will not pay it, and the store never learns the question existed.
Meet them in the channel they already use
A WhatsApp button removes almost all of that. One tap opens a conversation in an app they already have open, with their history intact and no account to create.
The single highest-leverage detail is the prefilled message. If the conversation opens with the product name and link already attached, you skip the round trip of working out what they are looking at.
Be honest about availability
A chat widget nobody answers is worse than no widget at all — it converts a neutral experience into a broken promise.
Set business hours so the button reflects reality. Outside those hours it should set expectations rather than imply someone is waiting.
Put the button where it earns its place
It does not need to be everywhere. Product pages and the cart are where questions block purchases; a blog post rarely is.
Placement is per page type, so you can keep it out of the way where it adds noise instead of value.
- Product pages — sizing, materials, compatibility
- Cart and checkout — shipping times and costs
- Collection pages — only if your range needs interpretation
The outcome
The questions that used to end in a silent exit end in a conversation instead — usually from a phone, usually in minutes.

