Across 50+ implementations, we have seen the same pitfalls when connecting Wazzup. Here are the issues that break most often, so you do not have to repeat someone else's experience.
Mistake 1. Connecting the director's personal WhatsApp as a "work channel"
The reasoning: "Our director has 5 years of customer correspondence in WhatsApp, let's just connect that." A week later, Meta detects mass messaging and bans the number. The customer history stays on the director's phone, and the company loses the channel.
What to do: set up a dedicated work number (virtual or a SIM card). The Personal API should only be used for inbound messages and a small volume of outbound ones. For bulk messaging, use the Business API.
Mistake 2. Not configuring chat distribution
All inbound chats land on a single manager (the administrator by default). Until they assign an owner, no one else can see the chat. During peak hours, customers wait 30+ minutes for a reply.
What to do: in the Bitrix24 "Open Channels" settings, enable queue-based or load-based distribution. Every chat is immediately routed to an available manager.
Mistake 3. Ignoring the 24-hour window in the Business API
In the Business API, you can message a customer freely only for 24 hours after their last message. After that, you can only reach out via an approved template. Managers are unaware of this, write as usual, and the messages are not delivered.
What to do: get 5-10 core templates approved in Meta in advance (greeting, appointment confirmation, payment details, reminder, NPS survey). Managers can then use them in a single click.
Mistake 4. Not accounting for Business API messaging costs
The Personal API has unlimited messages (you only pay the Wazzup plan). With the Business API, however, Meta charges for each conversation: a utility message costs about 10 KZT, and a marketing one about 30 KZT. At 1,000 messages per day, you can accidentally rack up a bill of 300,000 KZT per month.
What to do: before launch, estimate your messaging volume and decide whether you actually need the Business API or whether Personal is enough. For most SMBs, Personal covers 90% of use cases.
Mistake 5. Not tracking channels in the customer record
A customer writes via Instagram, then WhatsApp, then calls. In Bitrix24 this becomes three separate leads, three records, and three managers. No one sees the full picture, and the customer has to retell their story to each one.
What to do: enable automatic merging by phone number and email in your CRM settings. All inquiries from a single contact will be consolidated into one record.
