Designing for Conversation
Most product teams design for screens. We design for conversations.
It sounds simple. It’s not.
When your primary interface is a chat thread — not a landing page — every UX decision changes. Navigation becomes dialogue. CTAs become questions. Onboarding becomes a conversation.
The Constraints That Made Us Better
Building on WhatsApp means working within tight constraints:
- No custom fonts or colors
- No drag-and-drop interfaces
- No video embeds (mostly)
- Character limits on messages
At first, these felt like limitations. They turned out to be gifts.
Constraints force clarity. When you can’t rely on fancy UI, your product has to work through words alone. That forces you to nail your messaging, your value proposition, and your flow logic.
What We Got Wrong First
Our first version of the product flow looked like this:
- Click ad
- Land on WhatsApp
- See a wall of text
- ???
- Purchase
The drop-off was brutal.
We learned that on WhatsApp, messages need to be short, visual (via emoji), and action-driving. Each message should do one thing.
The Redesign
We rebuilt every flow with three rules:
- One idea per message
- Every message has a clear next step
- Never ask for information you don’t need
Conversion rate tripled within two weeks of shipping.
Lessons for Product Teams
If you’re building conversational products:
- Treat the chatbot as a sales rep, not a form
- A/B test your opening message constantly — it’s your headline
- Give users an easy way to talk to a human when they need to
- Measure conversation completion rate, not just conversion rate