How to send WhatsApp messages from Sage (the no-wait way)
The Meta Embedded Signup process for the WhatsApp Business API takes 2–4 weeks for most UK, US and South African small businesses. There is a faster path. Here is what it looks like on Sage — in GBP, USD, ZAR, and every language your customer writes in.
minidesk · Editorial team, minidesk
You run your business on Sage. Your customers live on WhatsApp — every invoice reminder, every balance enquiry, every delivery update, every complaint. The first time you try to connect the two — to send an invoice reminder, a balance reply, 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 Sage, in GBP, USD, ZAR, and every language your customer writes in.
Why the BSP route is slow — in every country Sage 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.
The 2-to-4-week wait is not a guess. It is what UK, US and South African 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 22-person wholesale group in Birmingham, the wait is the difference between "we can start sending WhatsApp invoice reminders this week" and "we can start sending WhatsApp invoice reminders 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 UK list usually includes: Companies House registration, the VAT number (if registered), a sample of the business's website, and a phone number that matches the business name. The US list usually includes: EIN, a sample of the business's website or Facebook page, and the same phone-number-matches-name check. The South African list usually includes: CIPC registration, the VAT number, a sample of the business's website, and 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 Sage as your connector, three things happen in parallel: you connect your Sage org with one OAuth click (cloud) or one translator install (on-prem), you connect your business WhatsApp number through Meta Embedded Signup, and you authorise the AI to read the Sage invoices, contacts, reports, and bank transactions. The whole flow is twenty minutes, end to end, in any country Sage 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 Sage ledger says, in the right currency, the right tax label, the right contact name for the country the invoice was raised in. When the AI sends a message to a customer in Birmingham, the message reads in English, in GBP, with the VAT line, on the Sage invoice number. When the AI sends a message to a customer in Austin, the message reads in English, in USD, with the sales tax line. When the AI sends a message to a customer in Johannesburg, the message reads in English (or Afrikaans or Zulu), in ZAR, with the VAT line. The AI is reading the same Sage your bookkeeper reads, in the same currency, the same tax label, the same language the Sage invoice was raised in.
What the conversation looks like in practice
It is 3:14pm on a Tuesday in Birmingham. A wholesale customer in Manchester sends a WhatsApp: "Can I get an update on INV-7841?" The AI reads the phone number, identifies the customer from the Sage contact list, finds the invoice, sees the payment landed this morning, and replies: "Hi Mr Thompson, yes — INV-7841 for GBP 4,200 was paid this morning via your Barclays account. The receipt has been emailed. Let me know if you need anything else." The reply lands at 3:14:08pm, London time. Mr Thompson reads it on the train. The bookkeeper in the office is at a client meeting. The conversation is handled.
It is 10:42am on a Wednesday in Austin. A customer in Dallas sends a WhatsApp: "What's my current balance?" The AI reads the phone number, identifies the customer from the Sage Intacct contact list, finds the open balance across two invoices, and replies: "Hi Ms Rodriguez, your current outstanding balance is USD 8,400 across two invoices. The most recent is INV-7842 for USD 5,200, due 14 August. Let me know if you need a statement." The reply lands at 10:42:04am, Central time. Ms Rodriguez reads it on her phone. The conversation is handled.
“We operate in three countries, three currencies, and three time zones. The WhatsApp AI is the first tool that handles all of them without us having to teach it the difference.”
— James, who runs a 22-person wholesale group in Birmingham
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 Sage 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 wholesale customers across the three countries — 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 Sage chart of accounts is clean — the AI reads what is in Sage, and a chart of accounts full of one-off accounts 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 currency, 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 GBP, USD, ZAR, AUD, SGD, and the rest of the currencies Sage supports.
If your business is already on Sage, 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 bookkeeper 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 currency the Sage invoice was raised in.
→ See the Sage integration: /integrations/sage