Comparison

Your Client Already Named the Job, the Time and the Budget. A Per-Message API Still Bills the Follow-Up as New

A few paint brushes resting on a folded canvas drop cloth next to a small burnt orange ceramic jar.

A client already told you everything you need for tonight's job. The job type, the time that works, the access detail and the budget they have in mind. That should be enough to confirm the booking in the same reply. Instead, a lot of WhatsApp platforms bill that client's next message as if none of it happened.

What a per-message API is built to do

A developer messaging API lets a business send and receive WhatsApp messages through code, for alerts, reminders, support replies and verification codes. Providers in this category typically charge per message sent and received, on top of WhatsApp's own usage fees. For a team building custom notification flows across many services, that flexibility is genuinely useful. It is a pipe. Not a booking assistant. Nobody on the other end of that pipe already knows this client's job.

Why an evening follow-up still gets billed as new

How does a per-message API price a booking conversation. Usually per message, both ways, with no memory of the last one included. A client who messages again after the first reply is billed as another message on the account, not a continuation of the job you already discussed. For you, running one number for the whole business, that is a charge that stacks with every reply, arriving exactly when a client needs a quick answer after hours.

The cost of losing the thread

Picture the client who already named the job, the access code for the gate and a budget range for the work. A per-message API does not carry that into the next reply. You have to ask again. Clients do not wait for a recap. They call someone else. Every repeated question is one more chance to lose a booking you had already agreed in principle.

One remembered booking thread confirms the job

A business messaging platform must mean somebody remembers what the client already said, surely? No. The platform counts messages. It does not carry what the client told you about the job. One remembered booking thread on your own WhatsApp number does that job instead. It holds the job type, the time, the access detail and the budget from the client's first message to the confirmed booking, so nobody has to repeat themselves before the work starts.

Why YunaChat wins for tradespeople and small service teams

YunaChat is a sales assistant that runs on your own WhatsApp number, not a per-message pipe billed by the provider. It answers every enquiry instantly, captures the job brief and keeps one remembered booking thread running from the first question to the confirmed slot. It never quotes a price on your behalf. There is no per-message charge stacking on top of WhatsApp's own fees, so the booking confirms without a recap. See pricing and start free.

Confirm tonight's booking without recap

Frequently asked questions

What is the difference between a per-message WhatsApp API and a WhatsApp sales assistant?
A per-message API is billed per message sent and received, and it does not remember a job on its own. A WhatsApp sales assistant has the booking conversation itself, captures the job brief and remembers it inside one thread.
Will a WhatsApp sales assistant quote a price to my client?
No. It qualifies the enquiry and captures the project brief, the job type, the timing and the budget range, then hands you a ready lead so you can quote the work yourself.
How does a sales assistant handle a booking that comes in after hours?
It replies immediately, in the client’s own language, asks the questions you would ask and keeps the detail in one thread so the booking is ready to confirm when you next check your phone.
Does switching away from a per-message API mean losing message history?
No. A sales assistant keeps every message inside the same WhatsApp thread on your own number, so nothing about the job needs to be re-entered.