How to send WhatsApp messages from Loyverse (the no-wait way)

You run your business on Loyverse. Your customers live on WhatsApp — every order confirmation, every menu enquiry, every delivery update, every complaint. The first time you try to connect the two — to send an order confirmation, an auto-reply to a menu question, a delivery update — the Meta Embedded Signup process starts, the Meta business verification queue starts, and the two-to-four-week clock starts. There is a faster path. Here is what the faster path looks like on Loyverse, in the language your customer writes in, in the menu they actually order from.

Why the BSP route is slow — in every country Loyverse serves

The WhatsApp Business API market runs through Business Solution Providers — WATI, Sleekflow, AiSensy, Twilio, MessageBird, the long tail. Every BSP requires the business to go through Meta Embedded Signup themselves, which means the Meta business verification queue, which means the 2-to-4-week wait. The Meta queue is not a BSP problem; it is a Meta problem, and no BSP can solve it on their own. The businesses that have already been verified are the ones whose number is already on the Business API; everyone else waits in the same queue, in every country.

The 2-to-4-week wait is not a guess. It is what small businesses on the WATI and Sleekflow signup flows report, in the support forums, in the Facebook community groups, in the Reddit threads. The pattern is the same: you sign up, you submit the business verification documents, you wait, you get a generic response that asks for more documents, you wait, you eventually get approved. For a 6-outlet bubble tea chain in the Klang Valley, the wait is the difference between "we can start sending WhatsApp order confirmations this week" and "we can start sending WhatsApp order confirmations next month."

What Embedded Signup actually is

Meta Embedded Signup is the flow where a business authorises a third-party application to send WhatsApp messages on the business's behalf. The flow is supposed to be one click. The reality is a three-step process: the business owner authorises the application, Meta runs the business verification, the application gets the API credentials. The first step is one click. The second step is the wait. The third step is the part no BSP can shortcut — Meta owns the verification queue, the documents, and the timeline.

The documents Meta asks for vary by country and by business type. The Malaysian list usually includes: SSM registration (or the equivalent for sole proprietors), a sample of the business's website or Facebook page, and a phone number that matches the business name. The South African list usually includes: CIPC registration, a sample of the business's website or Facebook page, and the same phone-number-matches-name check. The UK list usually includes: Companies House registration, the VAT number (if registered), the same phone-number check. The phone number is the part that catches a lot of small businesses — Meta does not allow a personal WhatsApp number on the Business API, and the porting process is a separate project.

The plug-in path — what minidesk actually does

minidesk holds the Meta Business verification. When you sign up and pick Loyverse as your connector, three things happen in parallel: you connect your Loyverse org with one OAuth click, you connect your business WhatsApp number through Meta Embedded Signup, and you authorise the AI to read the Loyverse sales, items, inventory, and customers. The whole flow is twenty minutes, end to end, in any country Loyverse serves. The Meta review queue is skipped because the queue is for businesses that have not been verified yet — your verification rides on minidesk's.

The second part of the no-wait path is that the WhatsApp message already knows what the Loyverse POS says, in the right language, the right menu item, the right modifier, the right price, the right delivery ETA. When the AI sends an order confirmation to a customer in Puchong, the message reads in Bahasa Malaysia, with the menu items in Bahasa, the modifiers (less sugar, more ice, no pearls) preserved, the prices in RM, and the delivery ETA that reflects the live prep queue. The AI is reading the same Loyverse your cashier reads, in the same language the customer wrote in, in the same menu the Loyverse POS already holds.

What the conversation looks like in practice

It is 2:14pm on a Saturday in Puchong. A customer sends a WhatsApp: "Nak order brown sugar boba 2, less sugar, oat milk, delivery ke Putra Heights." ("I want to order 2 brown sugar boba, less sugar, oat milk, delivery to Putra Heights.") The AI reads the phone number, identifies the customer from the Loyverse contact list, finds the menu item with the modifiers, sees the live prep queue is short, and replies: "Selamat tengahari Puan Tan! Pesanan Puan: brown sugar boba 2 (less sugar, oat milk) pada RM 8.50 setiap. Jumlah: RM 17.00. Penghantaran ke Putra Heights dalam 30 minit. Bayar sekarang?" The reply lands at 2:14:08pm. Puan Tan confirms, the order flows to the Loyverse till at the Puchong outlet, the head barista sees it in the kitchen display, the rider picks it up 24 minutes later. The order is in the till before a cashier has touched the keyboard.

It is 11:42am on a Wednesday in Cape Town. A customer sends a WhatsApp: "Hi, can I get a flat white and a croissant for collection?" The AI reads the phone number, identifies the customer from the Loyverse contact list, finds the menu items, sees both are in stock at the Sea Point outlet, and replies: "Hi Mr Adams, your flat white and croissant are confirmed for collection at our Sea Point outlet. We'll have them ready in 8 minutes. Total: R 78.00. See you shortly." The reply lands at 11:42:04am. Mr Adams walks in at 11:50. The order is in the till. The barista never touched the keyboard.

“We chose Loyverse because it was the smartphone POS that worked. The WhatsApp AI is the part that makes the orders actually happen on the chat — Bahasa, the live menu, the live prep queue, all in one message.”

— Puan Farah, who runs a 4-outlet cafe chain in the Klang Valley

What to do if you are already on a BSP

If you are already on a Business Solution Provider — WATI, SleekFlow, AiSensy, Twilio, MessageBird, or any of the long tail — the good news is the WhatsApp number and the API credentials are already in your business name, and Meta has already verified you. The migration is the part you are weighing, not the setup.

The practical path is: keep the BSP contract running for one billing cycle while you set up minidesk in parallel. Connect your Loyverse org with one OAuth click, let the AI read your data, and authorise the Meta Embedded Signup for your existing WhatsApp number through the minidesk console — the number is yours, the verification is yours, the migration is a settings change at Meta, not a new application. Test the AI on a small set of conversations — say, the top 10 customers across your busiest outlet — and compare the messages the AI drafts to the messages your BSP has been sending. When you are comfortable, switch the routing over and cancel the BSP at the next billing date.

Common mistakes when you set this up yourself

Three mistakes we see most often, all worth naming. (1) Connecting a personal WhatsApp number instead of a business number — Meta does not allow a personal number on the Business API, and the porting process is a separate project. (2) Trying to set this up before the Loyverse item list is clean — the AI reads what is in Loyverse, and an item list full of near-duplicates ("Mango Slush - 1", "Mango Slush-1", "Mango slushie") makes every reply longer than it needs to be. (3) Skipping the test phase — the first WhatsApp the AI sends should go to your own number, so you can see the layout, the language, the modifier preservation, the speed, before it goes to a customer. We have made all three of these mistakes ourselves; that is why the install wizard walks you through each one.

What it costs (and what it does not)

The Meta conversation fees are the same fees every platform pays. minidesk does not add a per-message markup on top of Meta's. The plan is a flat monthly fee that includes the AI, the channels, the connector, and the WhatsApp API. No per-conversation surcharge. No 12-month contract. No setup fee. The pricing is on the website; the quote is the quote. The plan works the same in MYR, SGD, AUD, ZAR, PHP, IDR, and the rest of the currencies Loyverse supports.

If your business is already on Loyverse, the WhatsApp path is the part of the AI you will use the most, and it is the part that takes the least time to set up. Twenty minutes from signup to the first message. The cashier does not have to do anything different. The customer does not have to download an app. The message lands in the WhatsApp they already have open, in the language they already speak, in the menu the Loyverse POS already holds.

→ See the Loyverse integration: /integrations/loyverse