Messaging customers from your app: a link, or an API?
In India your customers are on WhatsApp. In the US they text. Either way you face the same choice: let a person tap send, or let a server do it.
Almost every small business app ends up needing to message customers: a fee reminder, an appointment confirmation, “your order is ready”. There are two very different ways to do it, and choosing the wrong one first costs weeks. One is a link. The other is an API.
The link: a person taps send
A WhatsApp click-to-chat link opens WhatsApp with the chat addressed and the message already typed. A text-message link does the same with the phone’s messaging app. No server sends anything and no account is needed.
https://wa.me/919876543210?text=Hello%2C%20your%20fee%20of%20%E2%82%B91%2C200%20is%20due
sms:+15551234567?body=Hi%2C%20your%20estimate%20is%20readyThe WhatsApp number is international format, digits only: no plus sign, spaces, dashes or leading zero. A bare Indian mobile like 98765 43210 becomes 919876543210. The message has to be URL-encoded, which encodeURIComponent does, rupee sign included. On a phone the link opens the app; on a computer it opens WhatsApp Web. The sms: link behaves slightly differently between iPhone and Android, so test it on both before you put it in front of customers.
What the link cannot do is send by itself, attach a file, tell you whether the message was delivered or read, or message anyone at 3 a.m. A person always taps the button. That limit is also a feature. You are texting a customer you chose to contact, so there is no consent paperwork to get wrong.
The API: a server sends
An API lets software send and receive messages with nobody at a desk. It is how automatic receipts, appointment reminders and bots work. It comes with setup and rules, and they differ by channel.
WhatsApp Business API. You need a business account and a phone number registered with Meta, and that number cannot be used in the normal WhatsApp app at the same time. Most small businesses go through a provider that supplies the dashboard and API. To start a conversation, or to write to someone who has not messaged you in the last 24 hours, you must use a template message that Meta has approved in advance. Inside that 24-hour window after the customer writes, you can reply freely. Template messages are billed per message by category and country, and you need the customer’s permission to send them.
Business text messages in the US. You send through a provider such as Twilio, but carriers require you to register your brand and your use case before application-to-person texts will reliably arrive. This is called 10DLC registration, and approval can take days, so start it before you launch, not after. Marketing texts also need clear prior consent, and you must honour STOP replies. Toll-free numbers have their own verification.
Business text messages in India. Commercial SMS goes through registered sender IDs and approved templates under TRAI’s rules, arranged with a provider.
All of these are accounts of yours at an outside service. A builder can write the code that calls them, but it cannot supply the account.
A rule for choosing
Use the link while a person at a desk can send the messages. A handful of reminders a day, a “Chat with us” button on a website, a “Send me the details” button: all links. Move to an API when the person becomes the bottleneck. That means messages that must go out with nobody present, a need to know delivered, read or failed per message, hundreds of customers needing the same notice, or a bot or shared inbox answering people.
Our sample school fee tracker is a good example of starting small. Every overdue row has a button that opens WhatsApp with the parent’s number and a ready message. Nothing sends automatically. For a school office that is enough, and it took no accounts and no approvals.
Save the phone number properly
Normalise numbers when you save them, not when you build the link. If half your records say 98765 43210 and half say +91-98765-43210, every link and every duplicate check turns into a guess. Store the number in the international E.164 form, +919876543210 or +15551234567, with the country kept explicitly.
Do not guess the country from the digits. A bare ten-digit number can be Indian or American, and an app that sells in both has to ask, or default from the customer’s address, or use a phone-number library that parses with a stated region. Guessing wrong sends a customer’s reminder to a stranger.
Start with the records, add messaging second
Build the app that holds the data first. A prefilled message button needs no account and is a small change to add.
Describe your appFound something wrong or out of date? Write to hello@wyberai.com and we will fix it and say so here. Rules, fees and rates mentioned in our posts change, and this one was last checked on 18 November 2026.