WhatsApp Business API

What businesses actually use the WhatsApp Business API for

Editorial Team 6 min read

Most businesses on the WhatsApp Business API are using it as a faster phone line — one person, one conversation at a time, typed by hand. That works, and it is a fraction of what the platform is for. The value is in the sequences that run without anyone typing: the update that goes out when an order ships, the catalogue that arrives when someone scans a code, the reminder that catches an enquiry before it goes cold.

Here are seven that earn their place in a building materials business, and what each one replaces.

1. Turning a showroom visitor into a contact

The situation. Someone walks into your experience centre, spends half an hour looking at display panels, takes a photograph of two designs and leaves. You have no idea who they were.

What happens instead. A dynamic QR code beside the display opens WhatsApp with a message pre-filled. The customer sends it, a short registration runs in the chat, and the catalogue arrives on their phone before they have left the building. Because the code is dynamic, you can point it at a different collection next season without reprinting anything.

What it replaces. A printed brochure that stays in the car, and a visitor who was anonymous. The catalogue is the reason they engage; the contact is what you keep.

2. Order and dispatch updates

The situation. Your team spends a meaningful part of every day answering “has my order gone” and “when will it reach”.

What happens instead. Confirmation when the order is accepted, a message when it dispatches with the vehicle details, and one on delivery. Triggered by your own system, so nobody is checking a screen and typing.

What it replaces. Inbound calls, and the customer’s uncertainty that caused them. This is the use case with the clearest return, because you can count the calls it removes.

3. Keeping dealers informed

The situation. Dealers phone your office to ask what is in stock, what their scheme balance is and where their last order has reached. Your team answers the same questions all week.

What happens instead. The answers reach them on WhatsApp, which is the one application they open forty times a day. Where those numbers come from a system like Sales360, the messages are generated rather than composed.

What it replaces. A dealer portal nobody logs into. We have written about why that happens in why your dealers do not use the app you built them — the short version is that WhatsApp wins because it is already open.

4. Payment and account reminders

The situation. Outstanding balances age quietly, and the reminder call is one nobody enjoys making, so it happens late.

What happens instead. A statement before the due date and a short reminder after it. Neutral, automatic, and not attached to a relationship — which is precisely why it works. Most late payment is oversight rather than refusal, and a message clears it without anyone having a difficult conversation.

What it replaces. The call your accounts person keeps postponing.

5. Feedback after delivery

The situation. You have no idea whether the last hundred deliveries went well. Emailed surveys go unanswered.

What happens instead. One message a few days after delivery with two or three tappable options. Response rates on WhatsApp are unrecognisable from email, because answering takes a tap rather than opening a browser.

What it replaces. Finding out about a problem when it becomes a complaint. Catching a damaged delivery or a shade mismatch early is considerably cheaper than hearing about it publicly later.

6. Catalogue and sample requests

The situation. Enquiries arrive as “please send details”, with no indication of what they want or where they are.

What happens instead. A short conversation captures the product, the quantity and the location, then sends what they asked for and routes the enquiry to whoever serves that area. The customer got something useful; you got a lead with context attached rather than a name.

What it replaces. A contact form submission nobody can act on. This is the mechanic behind product catalogues and dealer locators, with WhatsApp as the front door.

7. Reviving a quiet enquiry

The situation. Someone visited, asked for an estimate, and went silent. Your team assumes they bought elsewhere. Usually the project simply moved.

What happens instead. A short sequence over several weeks, spaced out and specific to what they were looking at, stopping the moment they reply. Building materials projects run for months, and the follow-up nobody sends is the one that catches the delayed customer.

What it replaces. Writing off recoverable business after a fortnight. We have written about the mechanics in WhatsApp drip campaigns.

What decides whether this works?

Four things, and getting them wrong costs you the channel rather than the campaign.

  • Opt-in that would survive scrutiny. Recorded, specific, and covering marketing separately from transactional messages. See what counts as valid opt-in.
  • Templates in the right category. One promotional line reclassifies an entire utility template — why templates get rejected.
  • Restraint. Blocks and reports lower your quality rating, which reduces how many people you may message at all. What lowers it.
  • Stopping when someone replies. An automated message arriving mid-conversation reads as though nobody is listening.

There is also a cost change worth planning for: from 1 October 2026, messages sent inside the 24-hour customer service window become chargeable, having been free. Sequences that continue after a customer replies now carry a cost — see what changes on 1 October.

What does not suit WhatsApp?

Suits itDoes not
Order and dispatch updatesLong documents and detailed specifications
Short, tappable feedbackAnything needing a signature or formal record
Time-sensitive informationBulk marketing to a list with weak consent
Catalogue and sample requestsNegotiation and pricing disputes
Reminders and confirmationsComplaints, which need a person
Dealer stock and account informationAnything the customer would rather email

The most common mistake is putting everything on WhatsApp because it gets read. Being read is exactly why over-using it is expensive — the recipient has fewer ways to ignore you, so they block instead.

Where this runs

Every sequence above needs three things: an approved template, a trigger from a system that knows something happened, and somewhere for the reply to land.

Our WhatsApp Business API platform provides all three — a shared team inbox, template management, a CRM, and an automation builder that triggers sequences from a field change, a new contact or an incoming message. It connects to systems you already run, so a dispatch update comes from your own order data rather than from someone retyping it.

If you are working out which of the seven would be worth doing first, tell us what your team spends its day answering. That question usually identifies it.

Common questions

Which of these should we start with?

Whichever removes the most repeated calls. For most building materials businesses that is dispatch updates or dealer stock enquiries — both are measurable, both are uncontroversial, and neither needs marketing consent.

Do we need consent for order updates?

Transactional messages relating to a purchase sit differently from marketing, but record the scope either way. The common failure is someone consenting to order updates and receiving promotions, which from their side is spam.

Can this work with our existing systems?

Usually. The requirement is that your system can signal when something happens — an order dispatched, a stage changed. If that has to be typed by a person, the sequence still works but the saving is smaller.

How many messages a month does this add up to?

Fewer than expected if the sequences are well designed, and considerably more if they are not. Measure messages per resolved conversation rather than total volume — see sending fewer messages without reaching fewer people.

More on this: Business App vs API and WhatsApp drip campaigns. See also WhatsApp Business API.

Editorial Team

The Concord Technosoft editorial team writes from the work - building software since 2006, and still running much of it. Everything here comes from systems we operate rather than projects we delivered. Where we cite a rule, a rate or a platform policy, we check it first and date it.

Keep reading

More on WhatsApp Business API

Tell us what you are building

We will tell you how we would approach it, and whether we are the right fit.