Walk into any trading company, workshop, or distributor in the Gulf or India and ask where the customer conversations are. The answer is never "in the CRM." It's WhatsApp — quotes sent as photos, orders placed as voice notes, payment confirmations as screenshots — spread across the personal phones of whoever happened to answer.
It works, right up until it doesn't. This post is about the failure modes of phone-by-phone WhatsApp selling, and what changes when the conversations move into a shared inbox attached to your ERP.
The problem isn't WhatsApp — it's where it lives
WhatsApp is genuinely the right channel for these markets: customers respond in minutes there and in days by email, if at all. The problem is structural:
- The history walks out the door. When a salesperson leaves, every negotiation, every agreed price, every customer relationship in their chat history leaves with them — on their personal number, which customers keep messaging.
- Nobody else can see the thread. A customer chases their order with whoever is available; that person can't see what was promised, by whom, at what price. "Let me check and get back to you" becomes the company's most-sent message.
- The conversation and the record never meet. The deal is discussed in one place and (maybe) recorded in another. Follow-ups depend on individual memory. The quotation the customer approved by voice note isn't linked to any document.
- One number per phone. The business either publishes one person's number as "the" contact — a bottleneck — or many numbers, and customer history fragments across them.
None of this is a discipline problem you can fix with reminders to "update the CRM." The conversation is the work; asking people to transcribe it into a second system afterwards is asking for a task that will always lose to the next incoming message.
What a shared WhatsApp inbox changes
A WhatsApp Business inbox inside the CRM inverts the structure: one business number, and every conversation lands in a shared team inbox where messages are linked to the customer record automatically.
Concretely:
- The thread sits on the customer. Open a customer and the WhatsApp history is right there, alongside their quotations, orders, invoices, and balance. Anyone covering for a colleague reads the thread and continues it — no "let me check."
- Conversations become records without retyping. A price agreed in chat becomes a quotation; the customer's confirmation sits one click from the document it approved. With the assistant, "make this an invoice" is a sentence, not a data-entry session.
- Handover stops being an event. New salesperson, same number, same history. The relationship belongs to the business, with the individual doing the talking — not the other way round.
- Managers see the pipeline where it actually happens. Not a report of what people logged, but the real state of conversations: who's waiting on a reply, which enquiries went quiet, what was promised.
The etiquette part — worth taking seriously
Moving to a business number comes with obligations, and ignoring them burns the channel:
- Consent and expectations. Message people who asked to hear from you, about things they asked about. WhatsApp polices business messaging quality aggressively; a blocked number is a dead channel.
- Reply like a human. The reason customers prefer WhatsApp is that it doesn't feel like email. Template-blast a chat channel and you inherit email's response rates with none of its excuses.
- Keep personal phones personal. The clean break — business conversations on the business number — protects staff too. Nobody should field customer calls on their own SIM at 11pm as a job requirement.
Where the ERP connection earns its keep
A standalone shared-inbox tool solves the visibility problem. Putting the inbox inside the ERP solves the better one: context. The person answering sees not just the thread, but the account behind it — outstanding balance before promising another credit order, stock on hand before promising Thursday delivery, the open service case before apologising for the wrong thing. And follow-through has somewhere to go: enquiry to quotation to order to invoice, each linked back to the conversation that produced it.
That linkage is also what makes the history auditable. "We agreed 12% off list in March" stops being an argument about screenshots.
How BIZA helps
BIZA's CRM includes a WhatsApp Business team inbox: one business number, conversations tied to customer records, shared visibility for the team, and the full path from chat to quotation to invoice inside the same system — bilingual, like everything else in BIZA, because your customers' messages will be.
See our CRM features, or talk to the team — on WhatsApp, naturally.