A WhatsApp campaign is more than a broadcast. MIA pulls the audience from the CRM, sends Meta-approved templates and, when the customer replies, the AI carries the conversation through to your team. This page covers outbound messages; for chats customers start, see the WhatsApp chatbot page.
You build the template in MIA: a media header, body text with variables such as name, model or location, and buttons. It is submitted to Meta for approval and the status syncs back to MIA, so nobody has to check elsewhere.
Audiences come from MIA’s CRM: segments, saved views and RFM segmentation (Champions, Loyal, At risk, Lost, Never purchased). Facebook and Instagram Lead Ads leads flow in automatically every few minutes.
An external system can send a template or start a journey through the API.
Not every message is a dated campaign. Many go out when something happens. Each step can be a WhatsApp template, an email or an AI call, and the next step depends on a reply, a button click or silence within a set time.
Some customers ignore messages but pick up the phone. MIA playbooks combine both channels.
After a reply, the AI picks up the conversation with the goal, tone and objection handling you gave the campaign. It collects the qualification details you set and writes them to the CRM.
When a person is needed, an operator takes the chat and MIA stops. It is the same thread as the WhatsApp chatbot, not a separate inbox.
Two variants of the same message show which one gets more replies. Each journey report counts sent, delivered, read, replied, clicks and most-clicked links.
Replies, appointments and opportunities are what count. Not messages sent.
Message only people who opted in to WhatsApp messages from you. MIA records consent per channel, including consent collected on the first WhatsApp message.
Outside the 24-hour window after the customer’s last message, you can only send approved templates. Meta sets the rules and message pricing; check Meta’s official pricing page. This page is not legal advice.
Templates, free-form messages and outbound calls use communication credits, topped up from the dashboard. Volumes and plan are covered in the demo.
What marketing and BDC teams ask before the first campaign.
The chatbot answers when the customer writes first. Campaigns start from you: approved templates, CRM audiences, event-based journeys. When the customer replies, the same AI continues.
Yes, to CRM segments, with approved templates and only to opted-in contacts. MIA shows the number’s messaging health as reported by Meta: the right audience matters more than volume.
No. MIA includes a CRM with customers, opportunities and segments. If you already use Action, Walcu, TCar or Salesforce, leads and outcomes can be sent there.
Meta’s price depends on template category and country and is on Meta’s official pricing page. In MIA, messages use communication credits.
Where WhatsApp Coexistence is available, yes. We check it on your Meta account before activation.
Chats the customer starts: response, qualification and BDC handoff.
Guide with checklists, opt-in, templates, 24-hour window, CRM and Human Control.
When the customer ignores the message, a call as the next step.
The multichannel engine: WhatsApp, email and AI calls in one journey.
From first contact and qualification to human handoff and CRM.
Customers, opportunities and segments: where campaign audiences come from.
Webchat, WhatsApp, and voice in one operational layer.
In a demo we pick an audience from the CRM, build the template and decide what the AI does when the customer replies.
Request a MIA demo