WhatsApp Cloud API integration for your team’s software

It is Meta’s hosted way to use the WhatsApp Business Platform from software. Your system sends and receives messages through Meta’s API instead of a person typing in the WhatsApp app.

• Microsive ATS has a shared WhatsApp inbox. Recruiters import a resume in one tap, see the candidate’s profile and stage beside the chat, and send saved templates (Microsive ATS).
• Messaging bots are part of our bot builds (AI bots).

• Several people answer from one number and need the shared history.
• Chats belong on a record: a lead, candidate or order.
• Your system should send reminders and status updates on its own.

• One person replies by hand; the free WhatsApp Business app may be enough.
• Volume is low and nothing needs logging elsewhere.

• The customer service window. A message from a customer opens a 24-hour window, and each new message from them restarts it. Inside the window, your system can reply with free-form text and media.
• Outside the window. Only an approved template message can be sent, whether to restart a conversation or to send a reminder.
• Categories. Each template is marketing, utility or authentication. Meta reviews it, can move it to a different category, and can pause a template that recipients report or block.
• Writing templates that pass. Give each one a single clear purpose, mark its variables, and supply sample values for review. Submit them early, since a rejection can hold up launch.

When several people answer from one number, decide how a chat gets assigned, how a colleague sees who replied last, and what happens to chats that nobody picks up by the end of the day. Agree which saved templates each team can send, since template messages outside the window are charged.

1. Which messages are replies inside the customer’s window, and which need approved templates?
2. What happens in our system when a message fails to deliver?
3. Who answers messages on that number today, and what changes for them?

Account ownership: before the build, agree whose Meta business account holds the WhatsApp number, and what happens to it if you change vendors. We build inside your own Meta business account, on your own number, and hand control back. Nothing we set up is ours to take away.

Moving an existing number: a number already running on the WhatsApp Business app has to be migrated to the Cloud API. It is one number in one place, so once it moves it stops working in the app, and everyone answering messages there moves to the software instead. Plan that before the number migrates, not on the day.

• Follow-ups with no template ready. Once the window closes, a reply can’t go out until an approved template exists, so write follow-up templates before launch.
• Media links expire. Messages carry a media ID; the download link fetched from it expires quickly, so files are saved to your storage on arrival.
• Status arrives later. Delivered, read and failed states come by webhook after sending, and the interface should update as they arrive.

• Chat and WhatsApp bots · Workflows, messaging and payments