WhatsApp automation

WhatsApp Cloud API Services

The WhatsApp Business app cannot be connected to another system, and no amount of budget changes that. The Cloud API can — which is what makes an agent on the number, appointments written into a calendar, and reminders sent days later possible at all.

What we build

Agents that answer and act

A conversation that answers the questions that arrive every day, and books, quotes or routes at the end of it instead of handing the customer back to a queue.

Template messaging

Reminders, confirmations and status updates that go out days after the last message — approved templates, designed for approval from the start rather than submitted at the end.

CRM and calendar integration

Every conversation and outcome landing in the system that holds the customer record, with the source attached, rather than staying on a phone.

Migration from the Business app

Moving the number onto the platform, planned around the fact that a number cannot be in both and the app's chat history does not travel with it.

Where it stops

Every tool has limits worth knowing before you build on it. These are the ones that change a decision.

  • Messages are charged, and there is normally a second cost for whatever inbox software your team works from. Free is not one of the options here.
  • Outside the customer service window you can only send approved templates. Template wording is submitted for review, so campaigns cannot be written on the day they go out.
  • Meta Business verification gates everything. It decides your timeline more than anything technical does, and a business that cannot be verified cannot use the platform at all.
  • A number cannot be on the Business app and the platform at once, and the chat history stored in the app does not migrate. Anything worth keeping has to be exported first.

WhatsApp Cloud API FAQ

Do we need the Cloud API, or is the Business app enough?
The Business app is enough for replying by hand, greetings and away messages, and a couple of people sharing a phone. The platform becomes necessary — at any volume — the moment WhatsApp has to exchange data with another system, send scheduled or triggered messages, reach people who have not saved your number, or be worked by a real team. Those are capability limits of the app rather than questions of size, so growing into it is not an option.
Can we keep our existing number?
Yes, but it has to be migrated, because a number cannot be active in both places at once. The part that surprises people is that the chat history stored in the app does not come with it — export or archive anything you need before you start, and plan the switch for a quiet window rather than the middle of a campaign.
Why do reminders have to be templates?
Because they go out after the window in which WhatsApp allows free-form replies has closed. Outside that window only pre-approved templates can be sent, which means the wording is submitted for review in advance. It is a constraint to design for from the start rather than discover the week you planned to launch.
Will an agent on WhatsApp annoy our customers?
It does when it has no exit. An agent that answers the common questions instantly and hands anything else to a person is usually better than the alternative, which is a message read four hours later. The design that fails is the one with no route to a human — customers who cannot reach a person do not complain, they leave.

Need help automating a process?

Tell us about the repetitive work on your team—we’ll map a practical custom automation plan.