WhatsApp chatbot: built for your store under Meta's rules

That's the first thing we check during the review. Meta has a mode for using both at once (coexistence): the number stays in the WhatsApp Business app on the manager's phone and is also connected to the Cloud API the bot runs on. Whether this mode is available for your number, and how much of the chat history it carries over, depends on Meta's terms at the time of connection. If it doesn't fit, we use a separate number for the bot so chats on the old one don't break.

Meta charges for every delivered message sent by a business, and bills your company directly; we're not an intermediary. Templates are priced by category (marketing, utility and authentication) and by the recipient's country. Since October 1, 2026, free-form replies within the 24-hour window beyond the first 1,000 per month per number have also become paid, as have utility templates sent within an open window. That's what the documentation at developers.facebook.com/docs/whatsapp/pricing says, checked November 5, 2026; Meta changes its rates, so before the contract we calculate them for your volume.

Only with an approved template and only to a person who agreed to receive WhatsApp messages from you. The bot can send free-form text only within 24 hours of the customer's last message. That's why we prepare order statuses and cart reminders in advance as templates with parameters (order number, waybill number) and submit them for Meta's approval together with you.

The WhatsApp Business Platform terms (section 4.7) prohibit using the API for general-purpose AI assistants where the conversation with the model is the product itself; Meta decides on its own whether that's the primary or an auxiliary function. According to Meta, the restriction has applied since January 15, 2026. The same terms prohibit training models on WhatsApp data. A store bot that answers questions about your products and delivery and takes orders is customer service: the model in it answers only from your knowledge base and passes everything else to a person.

The bot sends a link to your payment provider's payment page, and after payment it returns a confirmation and the waybill number to the same chat. The link works the same way on a phone and in WhatsApp on a computer. Cash on delivery remains an option too: the shopper picks it with a button, and the order goes through without prepayment.

Not a ready-made one. LEO Chat, our product, runs every day in Telegram, in the website widget and in OLX chats, and its WhatsApp module is in beta: it already receives messages through the Cloud API, verifies Meta's signature, and sends buttons, lists and templates, but we don't sell it as a subscription. For your store, we take from the product the answer engine measured on 45 reference questions (89.7% accurate, July 4, 2026) and the ordering flow with Nova Poshta, and we set up and test the channel on your Meta account.

It doesn't make things up; it hands the conversation to a manager with its full history, so the customer doesn't have to explain everything again. Questions the knowledge base had no answer for go into a separate list that shows what to add to the knowledge base. One detail of the channel: if the manager replies more than 24 hours after the customer's last message, free-form text is no longer possible, only an approved template.

Our stages add up to 11–24 days: review, webhook and knowledge base, ordering flow, templates with tests, and launch. Steps on Meta's side come separately: connecting the number and approving the display name and templates; Meta sets their timing, and we don't promise it. The warranty is 30 calendar days from signing the acceptance act, and we respond to requests within 2 hours during business hours.