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

You run your F&B business on StoreHub. 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 StoreHub, in Bahasa Malaysia, in the menu your customers actually order from.

Why the BSP route is slow in Malaysia

The Malaysian 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.

The 2-to-4-week wait is not a guess. It is what Malaysian F&B businesses on the WATI and Sleekflow signup flows report, in the WATI and Sleekflow support forums, in the Facebook community groups, in the Reddit threads. The pattern is the same: you sign up, you submit the SSM documents, you wait, you get a generic response that asks for more documents, you wait, you eventually get approved. For a 14-outlet kopitiam 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, but 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 phone number is the part that catches a lot of small F&B 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 StoreHub as your connector, three things happen in parallel: you connect your StoreHub org with one OAuth click, you connect your business WhatsApp number through Meta Embedded Signup, and you authorise the AI to read the StoreHub sales, menu, inventory, and customers. The whole flow is twenty minutes, end to end. 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 StoreHub POS says, in the right language, the right menu item, the right price, the right delivery ETA. When the AI sends an order confirmation to a customer in Petaling Jaya, the message reads in Bahasa Malaysia, with the menu items in Bahasa, the prices in RM, the delivery ETA that reflects the live prep queue, and the rider availability the StoreHub POS is already tracking. The AI is reading the same StoreHub your cashier reads, in the same language the customer wrote in, in the same menu the StoreHub POS already holds.

What the conversation looks like in practice

It is 8:14am on a Saturday in Petaling Jaya. A customer sends a WhatsApp: "Nak order nasi lemak 2, teh tarik 1, delivery ke Seksyen 14." ("I want to order 2 nasi lemak, 1 teh tarik, delivery to Section 14.") The AI reads the phone number, identifies the customer from the StoreHub contact list, finds the menu items, sees the live prep queue is short, and replies: "Selamat pagi Puan Lim! Pesanan Puan: nasi lemak 2 (RM 5.80 each), teh tarik 1 (RM 2.50). Jumlah: RM 14.10. Penghantaran ke Seksyen 14 dalam 25 minit. Bayar sekarang?" The reply lands at 8:14:08am. Puan Lim confirms, the order flows to the StoreHub till at the Petaling Jaya outlet, the head chef sees it in the kitchen display, the rider picks it up 18 minutes later. The order is in the till before a cashier has touched the keyboard.

It is 9:42am on a Wednesday in Subang Jaya. A customer sends a WhatsApp: "Meh menu sarapan apa?" ("What's the breakfast menu?") The AI reads the StoreHub menu for the Subang Jaya outlet, sees the breakfast items are available until 11am, and replies with the menu in Bahasa, with prices, with the delivery ETA. The reply lands at 9:42:04am. The customer orders. The order is in the till. The cashier never touched the keyboard.

“We chose StoreHub because it was the cloud 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 Siti, who runs a 6-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 StoreHub 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 menu enquiries per day across the 14 outlets — 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 StoreHub menu is clean — the AI reads what is in StoreHub, and a menu full of one-off items makes every answer 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 price, 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 RM, SGD, USD, and the rest of the currencies StoreHub serves.

If your F&B business is already on StoreHub, 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, with the live menu the StoreHub POS already holds.

What the first 30 days actually look like

Most F&B operators that turn the AI on for the first time expect the AI to be the whole answer on day one. The honest answer is that the first 30 days are the calibration period — the AI is learning the per-outlet sales pattern, the prep queue rhythm, the Bahasa-vs-English preference for each outlet, the menu items that only run at certain outlets, the promo lines that only count at certain times. The head chef is teaching the AI which inventory items should be on the reorder list, which suppliers the WhatsApp should go to, which low-water marks need the operations manager's attention. The operations manager is teaching the AI which questions are daily, which are weekly, which are promo-specific.

By day 7, the AI is sending the first 3 workflows — the morning per-outlet sales summary, the live menu auto-reply, the MyInvois e-invoice batch — with no human in the loop. By day 14, the AI is handling the 80% of customer WhatsApp messages that are routine (menu enquiry, order confirmation, delivery update, opening hours) without a cashier touching the keyboard. By day 30, the AI is the layer that reads StoreHub in Bahasa and English, writes the WhatsApp with the live menu, and posts the MyInvois batch to LHDN — and the morning operations meeting starts with a WhatsApp the AI drafted at 7:30am, not with a spreadsheet someone built at 8:45am.

The number that matters most at the 30-day mark is the same one Mr Tan watches in his own chain: how many of yesterday's customer WhatsApp messages were handled by the AI, and how many needed a human. The honest target, for a Malaysian F&B chain running on StoreHub, is 70% handled by the AI at 30 days, 85% at 60 days, 90% at 90 days. The remaining 10–15% is the part that genuinely needs a human — the supplier negotiation, the customer complaint, the menu engineering decision. The AI is not trying to replace those. The AI is trying to clear the 85% so the head chef and the operations manager have the time for the 15%.

Common questions F&B operators ask before they start

1. 1Does the AI replace the cashier? No. The AI is the layer that lets the cashier stop typing the same menu reply 30 times a day. The cashier still owns the till, the cash, the discount decisions. The AI is the new chat surface, not the new cashier.
2. 2Does the AI write to StoreHub? No. Every order and every inventory adjustment stays in the StoreHub POS, exactly where the cashier made it. The AI is a reader of StoreHub and a writer of WhatsApp, never a writer of POS. The data isolation is the product (see the security page) — the wall is in the database, not in a prompt.
3. 3Does the AI handle the MyInvois e-invoice batch? Yes. The AI reads the day's StoreHub sales, drafts the consolidated e-invoice, and posts it to LHDN through your existing MyInvois credentials. The bookkeeper reviews the draft before submission, or the AI submits and the bookkeeper gets the confirmation WhatsApp.
4. 4Does the AI work in Bahasa Malaysia and English? Yes. The AI matches the language the customer wrote in. The reply to a Petaling Jaya customer is in Bahasa. The reply to a Singapore customer is in English. The reply to a Bangkok customer is in Thai. The menu items are in the language the StoreHub menu holds them in.
5. 5What if I am not on StoreHub yet? Sign up for StoreHub first (storehub.com), connect your outlets, and let the till settle for a week. Then sign up for minidesk, pick StoreHub as the connector, and the AI starts reading the POS the moment the OAuth is authorised.

→ See the StoreHub integration: /integrations/storehub