WhatsApp Business API integration · Udupi & Mangaluru
We connect the WhatsApp Business API to your billing, order or booking software, so receipts, updates and reminders go out on their own and replies reach your team. Meet us at our Udupi studio; we stay on once the messages start.
In short
WhatsApp Business API integration connects your own software to WhatsApp so it sends messages by itself: a receipt when a bill is saved, an update when an order ships, a reminder before a payment falls due. Messages the business starts must use templates approved by Meta, which runs WhatsApp. Whirl Designs, based in Udupi in coastal Karnataka, adds WhatsApp messaging to billing, order and booking systems.
Start here
WhatsApp can serve a business in three ways, and the API is only one of them. Plenty of shops are well served by the first two, so our first conversation with you is about which one fits.
Best for: One phone and a few dozen chats a day
Best for: Broadcasts and a shared inbox, with nothing to build
Best for: Messages that depend on your own bills, orders and dues
If the app or a ready platform is enough for you, you will hear that from us first, along with help setting it up.
Our work
Jayalaxmi Jewellers
Retail jewellery · Karkala
Jayalaxmi Jewellers, in Karkala, has been trading in gold since 1990. We built two things for it: a brand website with collections and appointment booking, and a separate retail ERP that handles POS billing, savings schemes, old-gold exchange and stock.
The shop's WhatsApp messages come from inside that ERP. Customers receive their receipts and reminders on WhatsApp, sent from the system through the WhatsApp Business API, and each message is built on a template that was approved in advance.
What you get
The plan names each one for your business: which account, which messages, which events send them, and who answers.
How it runs
You see every message on your own phone before a customer gets one.
Together we list each message a customer should get: what triggers it, what it says, and who handles the reply. Three or four messages are usually enough to start.
Your Meta business account is set up and verified with your business documents, such as your GST certificate, and the phone number is registered. Verification can take a few days, so it starts first.
Each template is written with you, in the language your customers read, and sent to Meta. Its rules are followed from the first draft: no blank at the very start or end, no two blanks side by side. Any that still come back rejected are reworded and sent again.
Your software is connected, and messages go to your own staff's phones first, from test bills and orders. The wording, the timing and every filled-in detail get checked.
The most useful message, usually the receipt, goes live first. We watch the delivery log for the first weeks, add the rest, and stay on as Meta changes its rules.
Not a fit
Sometimes the honest advice is a simpler tool, or no build at all.
Questions
The app is a phone app that a person uses; the API has no screen of its own and is used by software. The app suits a shop that answers chats by hand. The API lets your billing, CRM or booking system send messages by itself, lets a team share one number through a shared inbox, and keeps a record of every message sent.
A template is a message Meta approves in advance, with blanks your system fills in, such as a name, an order number or a due date. A business needs one to start a chat, or to write again more than 24 hours after the customer's last message. Inside those 24 hours, your team can reply in its own words.
Usually two to four weeks for a first set of three or four messages sent from your own system. Part of that time is on Meta's side: business verification can take a few days to two weeks, and templates are usually approved within a day or two. Older software that has never been connected to anything takes longer, and we tell you so after the first look.
Not automatically, and no developer can promise it. The old green tick is now a blue tick, and Meta alone decides who gets it: a well-known brand can apply for an official business account, and other businesses can apply through Meta Verified. Connecting the API does not add a tick by itself. We get your business profile and documents ready so an application has what it needs.
Often, yes. Meta now lets many numbers that already run on the WhatsApp Business app connect to the API too, so the app keeps working alongside it, with its chat history. Meta decides which numbers qualify, based on things like how long the number has been active, and a few app features, such as broadcast lists, are switched off. We check yours first. If it does not qualify, a separate number for automatic messages is often simpler.
Yes. WhatsApp templates can be written in Kannada, and Meta reviews each language version on its own. For a business in Udupi, Karkala or Mangaluru, we can set up the same receipt in Kannada and English, and your system sends the one that matches each customer's choice. We check the Kannada text on real phones before it goes live.
No, a BSP is optional: Meta's Cloud API lets your own software send messages with no one in between. A Business Solution Provider (BSP) is a company that adds its own dashboard, broadcast tools and support on top. We connect directly when messages come only from your system, and through a provider when your team also wants its shared inbox. The WhatsApp account and number stay in your business's name either way.
In most cases, yes. If your software can tell another system when a bill, order or payment is saved, the WhatsApp step can be added to it, or built into a custom system we make for you. Shopify and WooCommerce stores often have a ready plug-in, and we will say when that is enough. For software that cannot be changed, its add-ons are the first place we look.
Worth reading first
Clean, documented, tested code on a modern, proven stack — the foundation that keeps your whatsapp business api integration fast and dependable for years.
Ready when you are
Share the messages you wish your customers got today, and our written reply will name each template, the event that sends it, and how it gets tested.