Ten WhatsApp bans in a row: how we gave a manufacturer its sales channel back without taking the phones off its sales team

What happened

Meta updated its algorithms and tightened its security rules for WhatsApp. And a setup that had run without complaint for years started falling apart:

• The company number was banned. Then again. And again.
• Around ten bans in a row, in total.
• Every ban is a full stop on the main sales channel. Not an inconvenience. A stop.
• Managers cannot answer customers. Customers cannot get through. Orders hang.
• Every restoration costs time, nerves, and the risk that next time the number does not come back at all.

Why it happened: the mechanics few people explain

Let us be straight about this, without blaming the services — they are hostages of the same architecture.

Services like Wazzup, Green API, i2crm and Chat2Desk connect to WhatsApp on their basic — and most popular — plan by scanning a QR code. Technically that is WhatsApp Web emulation: a third-party server pretending to be a browser with your WhatsApp open in it.

• Meta does not officially approve this connection method. It works not because it is allowed, but because for a while it is not detected.
• Meta's algorithms can recognise emulation. A sudden change of geolocation on connection, server IP addresses, activity patterns that do not look human — all of it is a marker.
• Each algorithm update makes detection sharper. That is exactly what happened to our client: another tightening of the rules, and something that had worked for a year started collecting bans.
• A ban can become permanent. You keep the phone number, but WhatsApp will never work on it again. There is no restoration.

The inputs

• Customer base in the CRM — 3,645 contacts
• Deals in amoCRM over the period — 2,680
• Average order value — around 11,000 KGS
• Number of bans — around 10

Direct losses from downtime

• 2,680 deals over roughly a year averages about seven deals a day.
• Even if each ban knocked the channel out for a single working day, that is ten days of the main sales channel being down.
• 10 days × 7 deals × 11,000 KGS ≈ 770,000 KGS of revenue not earned.

And that is the optimistic scenario, where restoration takes a day. In practice it took longer.

What that figure misses, and what hurts just as much

• Reputational damage. A customer writes on WhatsApp — undelivered. Writes again — silence. On the third attempt they write to a competitor. They do not come back.
• Live negotiations cut off. A deal at the artwork-and-price stage is the most fragile there is. A two-day pause kills it outright.
• The risk of losing the number permanently. The company number is printed on business cards, the signage, the packaging, the advertising and the website. Losing it for good is on the scale of moving office without telling anyone.
• A demoralised sales team. A manager whose tool falls over every fortnight stops believing in the system and goes back to their personal phone. At that point everything collapses.

Why WABA did not fit: it kills the phones

On a classic WhatsApp Business API connection the number moves into Meta's cloud. And this is what follows:

• The WhatsApp Business app on the phone stops working. The number is unbound from the device. A manager physically cannot open a chat on their handset.
• WhatsApp calls disappear. The call button simply vanishes from the customer's interface.
• The account cannot be added to group chats.

For many companies that is tolerable. For this client it was categorically not.

Why this mattered so much to the client

The specifics of the business matter here. This is manufacturing, not an online store:

• Managers call customers through WhatsApp from their work phones. It is the primary channel — discussing artwork, agreeing a shade, checking a size range.
• A manager walks the production floor with a phone. Photographing a fabric sample, filming the press in operation, showing a finished run — that takes ten seconds from a phone and cannot be done any other way.
• Switching off the phones means pulling the sales team's main working tool out of their hands and replacing it with a computer they walk past between tasks.

And then the crucial fact surfaced

We checked the WABA connection options available on the market, including the one Wazzup offered. Not one of them supported Meta Coexistence.

So the choice the market offered looked like this:

• Stay on QR — and keep collecting bans, at the risk of losing the number for good.
• Move to WABA — and strip the managers of their work phones, breaking the whole sales department's process.

Both options are bad. A classic dead end. That is the point at which the client came to us with a question: can we make both work at once? The answer: yes. But no off-the-shelf solution exists — it has to be built.

Why YCloud

We chose YCloud — an official Meta Business Partner with full Coexistence support.

• Official Meta partner status — direct access to the Cloud API with no intermediaries and no grey schemes.
• Full Coexistence support — precisely what the client's earlier options lacked.
• An open, documented API — you can build your own logic of any complexity instead of bending to somebody else's interface.
• Transparent pricing — you pay for message traffic, not a subscription per user and per channel.
• Works without geographic restrictions — critical for a business in Kyrgyzstan and Central Asia.

Layer 1. WhatsApp via Coexistence

• Connecting the official Cloud API to the existing working number — no number change and no loss of audience.
• The WhatsApp Business app on the managers' phones keeps working unchanged.
• Inbound messages received through webhooks in real time.
• Outbound sending: text, images, documents, audio, video.
• Replying to a specific message (quoting) — exactly as in ordinary WhatsApp.

Layer 2. amoCRM — a proper conversation, not notes on a deal

Many integrations simply append the message text to the deal's notes. It looks poor and you cannot reply from there. We built a native integration through the amoCRM Chats API (amojo):

• Registering our own channel in amoCRM.
• Conversations land straight in Chats / Imbox — the same place as Instagram, Telegram and the other channels.
• The manager replies from inside the deal card — the message goes to the customer on WhatsApp and is mirrored into the chat on their phone.
• Media renders inline: photos have previews, documents download, voice notes play.
• Files are additionally attached to the deal through the Files API — artwork or a spec will not get lost in the message feed.

Layer 3. Contacts and deals created automatically

• A message arrives from a new number and the system creates the contact and the deal in amoCRM automatically.
• Numbers are normalised to international format with Kyrgyz specifics in mind: local numbers in the form 0XXXXXXXXX convert correctly to +996XXXXXXXXX.
• The search for an existing contact runs across every way the number can be written — no duplicates pile up.
• The deal is linked to the contact, and the conversation to both the contact and the deal.

Layer 4. A WhatsApp widget inside MoySklad

A separate piece, and probably the client's favourite — a built-in widget for MoySklad:

• A live WhatsApp chat opens directly inside a customer order or counterparty card.
• A production manager or warehouse clerk writes to the customer without leaving MoySklad or switching tabs.
• Messages from the widget mirror into amoCRM — management sees all communication in one place.
• Receiving and sending work without reloading the page.
• Attachments are supported — send a photo of the finished run straight from the inventory system.

Layer 5. Reliability — what separates production from a prototype

This is where "knocked together in an evening" ends and engineering begins:

• A queue with retries. If amoCRM is temporarily unavailable the message is not lost — it queues and is resent with increasing back-off (5 sec → 30 sec → 5 min).
• Message deduplication with a 48-hour TTL — Meta webhooks can arrive twice, and the customer must not see duplicates.
• Webhook signature validation — an outsider cannot inject a fake message into your CRM.
• Rate limiting on every public endpoint — protection against overload and abuse.
• Admin endpoints protected by a separate access key.
• 88+ automated tests and a CI pipeline — every change is checked before it reaches production.
• Telegram alerts — if something goes wrong the team knows within seconds rather than hearing it from an angry customer.

The customer's name instead of "Deal #57198241" in the inbox

When a conversation is linked incorrectly, amoCRM shows the system deal name in Imbox instead of the customer's name. The manager sees a column of faceless numbers and cannot tell who is writing to them.

We went through the official Kommo/amoCRM documentation on Conversation Import, worked out the mechanics of the links, and attached the conversation to the contact rather than the deal — the way Kommo itself and the larger integrators do it. We also wrote a migration script that renamed 355 existing deals from auto-generated names to real customer names.

Coexistence limits we flag honestly

We do not sell magic. The technology has known limits:

• Group chats do not synchronise with the API — they stay in the phone app only.
• Disappearing messages and view-once are switched off for the number.
• Live location sharing is not supported.
• Status updates are not passed to the API.
• Broadcast lists in the app become read-only — bulk sending goes through the API.
• Throughput is up to five messages per second.
• The number has to be a live one: Meta rejects connections from freshly registered numbers with no real conversation history.

For the overwhelming majority of B2B scenarios none of these are critical. But you should know about them before the project, not after.

What this means for the business

• The sales channel stopped switching off. The sales team works without downtime.
• Nobody had to be retrained. The phone in the pocket works exactly as it did. That matters: integrations more often fail through a team quietly refusing an awkward tool than through technology.
• The company's main number is protected. It stays on the business cards, the signage, the packaging and the advertising — and there is no longer a way to take it away.
• The customer base belongs to the company. The whole conversation history is in the CRM, not on the personal phone of an employee who has left.
• Analytics work. First response time, conversation-to-deal conversion, manager workload — all measurable and manageable.