The WhatsApp channel lets a Clone receive and reply to WhatsApp messages your customers send to your business number. It runs on the WhatsApp Business Platform (the API-based product, sometimes called the Cloud API) — not the free WhatsApp Business phone app, and not your personal WhatsApp. You connect through Meta's embedded signup (a Facebook login plus phone-number verification), and two Meta rules shape everything afterward: the 24-hour customer-service window and the pre-approved message template requirement for messaging outside it. This guide covers all of it.
WhatsApp requires a phone number dedicated to the WhatsApp Business Platform — it can't be in active use on the consumer WhatsApp app or the WhatsApp Business app under the same identity. If your number is on the WhatsApp Business app, Meta may offer Coexistence mode during signup so you keep the app and automate through IcloneU; if it's on the consumer app you'd migrate it (a one-way move) or, more simply, use a fresh dedicated number. See What you need first below.
What the WhatsApp channel is
WhatsApp is Meta's consumer messaging product, and its business side runs on the WhatsApp Business Platform. IcloneU integrates with the Platform (API-based) — not the WhatsApp Business phone app, which is a separate, manual, phone-only product that can't be connected. A few consequences are worth knowing up front:
- You connect through Meta, not a form. Unlike Email, there are no server addresses to paste — you're redirected into Meta's embedded signup, log in with Facebook, pick or create a WhatsApp Business Account, and register/verify your phone number.
- Inbound routes through Meta's webhooks. Every message a customer sends to your business number arrives in IcloneU's Messages surface tagged with the channel; your Clone reads it, retrieves from Knowledge, and replies.
- Meta's 24-hour window applies. Your Clone can send free-form replies only within 24 hours of the customer's most recent message; outside that, it needs a pre-approved template. This is enforced by Meta, not IcloneU — see The 24-hour window.
- Messaging volume scales on a tier ladder. New numbers start able to message a capped number of unique customers per day and graduate automatically as the account builds a good reputation — see Frequently asked.
WhatsApp is one of the channels you add from the Connections page. Once active, it shows up there as a row identified by the phone number, and incoming messages appear in the Messages surface tagged with the channel.
What you need first
Before you start the connect flow, line up three things. Getting these ready first is what turns a 30-minute setup into a 10-minute one.
- A Meta Business Account (also called Business Manager) — the same umbrella object used for Facebook Pages and Instagram business accounts. If you don't have one, create it free at business.facebook.com. You need to be its owner, or a user with permission to authorize apps and register WhatsApp numbers.
- A phone number for WhatsApp Business that can receive an SMS or voice call for verification, and that is not currently active on the consumer WhatsApp app or the WhatsApp Business app under the same identity.
- An IcloneU account with a free Connection slot on your current plan. Each channel you connect (WhatsApp, Facebook, etc.) counts against your plan's Connection cap.
The connect flow itself doesn't free up a busy number — you do that beforehand at Meta. If your number is on the WhatsApp app: delete the account from the phone (Settings → Account → Delete my account) — uninstalling alone does not release it. If it's in a WhatsApp Business Account (WABA) already: disable two-step verification for it in WhatsApp Manager. If it's with another provider (BSP): ask them to release it, or remove it in WhatsApp Manager — and disable two-step verification there before you go. In Twilio that means doing it before you delete the WhatsApp sender. A PIN left active at the old provider is the single most common reason a migrated number won't activate, and recovering it once the sender is gone means going back to that provider's support.
No pre-existing WhatsApp business presence is otherwise required — Meta's embedded signup creates the WhatsApp Business Account record and verifies the number, and IcloneU then finishes the activation and subscribes the webhook (see Connecting a WhatsApp number). For the full prep-by-scenario walkthrough (personal-app number, WABA number, other-provider number), IcloneU shows a scenario guide right inside the permissions step.
Connecting a WhatsApp number
The flow starts in IcloneU, hands off to Meta's embedded signup for the login, business-account pick, and phone verification, then returns you to IcloneU. Most of the elapsed time is on Meta's side and largely outside IcloneU's control — budget 10 to 30 minutes.
Start a new WhatsApp connection
Open Connections in the left sidebar, click New connection, and pick WhatsApp. IcloneU shows a short intro that explains you'll click a button to open the WhatsApp signup flow, notes that if you already use the WhatsApp Business app on your phone you may be offered the option to keep using it alongside IcloneU (Coexistence mode), and says that otherwise the flow guides you to register or migrate your number. It links out to this guide for the detail. On Meta's side, the embedded signup grants IcloneU the WhatsApp business messaging and management permissions.
Log in with Facebook
Click through and IcloneU redirects you to Meta's login. Sign in with the Facebook account that owns (or can manage) your Meta Business Account, and approve the permissions Meta presents.
NoteIf your Facebook account isn't linked to a Meta Business Account yet, Meta walks you through creating one before continuing.
Select or create the WhatsApp Business Account
Meta asks which WhatsApp Business Account this connection should attach to. Pick the right one (most people have only one), or let Meta create one.
Heads upReconnecting? Always pick what already exists — the existing WhatsApp Business Account here, and the existing number in the next step. Every "create new" on a reconnect leaves an orphan WhatsApp Business Account behind in your Business Manager. They're harmless, but they pile up and make later troubleshooting confusing. Clear leftovers under Business settings → WhatsApp accounts.
Register and verify the phone number
Enter the phone number to use for this connection, including the country code — double-check the country selector, since Meta's default is sometimes wrong. Meta sends a 6-digit code by SMS or voice call; enter it to verify ownership. If the number is already on the Business Platform under your account, pick it from the existing-numbers list instead. If you want to keep the number working in the WhatsApp Business app as well, take the Coexistence option where Meta offers it — see the note below.
TipNo code arriving? SMS can be filtered on VoIP numbers — wait a couple of minutes, then request a fresh code and try the voice option. If Meta says the number is "already in use," it's still active on a WhatsApp app somewhere: delete that account (or use a different number) and retry. And if Meta's popup fails with a generic “Sorry, something went wrong” on both the existing-number and new-number paths, that's the same cause wearing a different mask — see the note on releasing a number below.
Let Meta finish its review (first-time only)
For accounts new to WhatsApp Business, Meta runs a brief review of your business (display name, category, legal info). This often completes instantly; occasionally it takes a few hours. You can proceed — the connection becomes active once Meta clears the review.
Choose which numbers IcloneU connects
Back in IcloneU on the WhatsApp Phones step, the subtitle confirms "Your account was successfully authenticated. Choose the WhatsApp phone numbers that you want IcloneU to connect to." Select your number and finish. It now appears on the Connections page as a row identified by the phone number, with an active status indicator.
If the number is on the WhatsApp Business app and you want to keep answering from the phone as well as through IcloneU, take the Coexistence option in the connect flow. Verification is by QR scan — no SMS or voice code — and it only works when all four of these are true: the number is on the WhatsApp Business app (not regular WhatsApp), the app is on its latest version, the number has been registered on that app for more than 24 hours, and the phone is online while you run the flow. If any one of them is false, use a fresh number or release this one from the app first.
If the number should leave the WhatsApp Business app and live only in IcloneU, it has to be released from Meta's side before it can be registered anywhere else. Uninstalling the app does not release it. The symptom when it hasn't been released is distinctive: Meta's popup fails with a generic “Sorry, something went wrong” on both the existing-number and the new-number paths, or the verification call and SMS simply never arrive. To fix it, open WhatsApp Business → Settings → Account → Delete my account on the phone (reinstall the app first if you'd already removed it), then wait — Meta describes this as minutes, but in practice it can take up to 24 hours — and reconnect, adding the number as new and verifying by SMS.
One link in that chain is IcloneU's, not Meta's. Meta's embedded signup creates the WhatsApp Business Account and verifies the number, then deliberately stops short of the final Cloud API registration — the call that makes a number able to send and receive. Left undone, the number sits at Pending and nothing arrives. So whenever IcloneU finds a connected number whose status is not CONNECTED, it makes that call itself. Meta wants a two-step verification PIN with it, so if the number doesn't already have one IcloneU generates a six-digit PIN and saves it against the connection before registering — losing it would strand the number the next time it had to be registered.
A failed registration doesn't stop the connection from being created; it stops the number from going live. IcloneU flags the connection on the Connections page with a warning marker — hover it to read why — and there are three answers. A PIN left behind by a previous provider (the usual case for a number migrated from another BSP): "This number has a two-step verification PIN set by a previous provider. Recover or disable that PIN and reconnect the number to finish activating it." No payment method on the WhatsApp Business Account: "Meta requires a payment method on your WhatsApp Business Account before this number can be activated. Add one in WhatsApp Manager (Business settings, Billing and payments), then reconnect the number." Anything else: "The number could not be registered for messaging:" followed by Meta's own explanation — IcloneU reads the detail field of Meta's rejection rather than repeating its generic top-level error, so the sentence is usually actionable. These specific reasons appear instead of the generic status warning, not alongside it. There is also a fourth message for a number that never finished Meta's code verification: "Phone number has not completed verification. Complete the verification in Meta Business Suite."
The three specific reasons above are worked out during the connect attempt itself. The generic warning — "This WhatsApp number is not yet active (status: …)" — is the one recalculated from Meta every time you open the Connections page, so it is what you'll see on any later visit, even when the real cause was the previous provider's PIN or the missing payment method. Those are precisely the two causes waiting will never fix. So if the number has any prior WhatsApp or provider history, work the cause rather than the clock; only a genuinely new number with no history is likely to be waiting on Meta's review. And note the second half of the fix: correcting the cause on Meta's side does not activate the number by itself. IcloneU makes the registration call when a connection is made, not on a timer — so after you add the payment method or clear the old PIN, you still have to reconnect (or disconnect and reconnect) for the number to go live.
Attaching a Clone and enabling it
A connected number does nothing on its own — incoming messages will queue in Messages but won't be auto-replied until a Clone is attached. Open the WhatsApp connection's settings panel from the Connections page to wire it up.
- Clone — pick the Clone that answers on this number from the dropdown ("The clone that will reply on behalf of this integration."). On a fresh connect it may auto-populate your Clone, but you must Save for it to persist.
- Enabled — the master switch. "When off, incoming messages and comments for this account are ignored. Tokens are kept so you can re-enable without reconnecting."
- Reply timing — "Inherit the team's reply schedule and delay, or customize them for this account." Use this to hold replies to business hours or add a human-like delay.
- Direct-message review — under the "Response authorizations required for" card, tick the reply types that need review, then choose "Send immediately" (the default), "Hold until approved", or "Auto-send after a delay". In delay mode you set the minutes (5–240; 30 by default) — "Minutes before the reply sends automatically. You can approve, edit or cancel it during this time." A parked reply shows as "In review" in the thread, and a new message from the customer cancels it so the Clone can answer everything in one reply.
WhatsApp's panel is DM-style: it has Enabled, Clone and Reply timing, but no "Post options" section (that's for comment channels like Facebook). It does include the "Response authorizations required for" card with the "Direct-message review" modes above. On WhatsApp, holding has a catch the panel warns about while hold mode is on: "This platform only allows replies within 24 hours of the customer's last message. A reply that isn't approved in time expires and can no longer be sent." With the default "Send immediately" mode, once a Clone is attached and Enabled is on, your Clone answers incoming WhatsApp messages automatically, within the 24-hour window.
For the full attach-and-enable walkthrough that applies across every channel, see Assigning a Clone to a platform. To confirm it works, have someone message your business number from a different phone — the inbound should land in Messages within seconds, and if a Clone is attached, its reply follows within seconds too.
The 24-hour window and message templates
This is the single most important WhatsApp rule to understand, because it decides whether your Clone can reply at all. It's Meta's anti-spam mechanism, enforced at the platform level — IcloneU cannot bypass it.
When a customer messages your business number, a 24-hour customer-service window opens. Inside it, your Clone can send free-form replies — plain or formatted text, images, audio, video, documents, stickers, contacts, locations. Every new message from the customer resets the clock, so a back-and-forth conversation stays inside the window naturally. The window starts on the customer's message timestamp and resets on inbound — your Clone replying does not extend it.
Once 24 hours pass without a new inbound message, the window closes and free-form text is blocked. The only way to message that customer again is a pre-approved message template — a fixed message you submit to Meta and get approved in advance, with {{1}}, {{2}} placeholders you fill at send time. Templates are also the only way to start a conversation with a customer who hasn't messaged you first.
The window also disciplines review mode: if you set "Direct-message review" to "Hold until approved", each held reply shows an amber hourglass pill in the thread — "approve before 9:15 AM" — counting down to 24 hours after the customer's last message. If nobody approves it in time, IcloneU marks it "Undeliverable": WhatsApp would reject the send, so the reply can no longer go out. If you want review without that risk, pick "Auto-send after a delay" — the reply sends itself before the window can close on it.
Even inside the 24-hour window, interactive components — reply buttons, call-to-action buttons, and list messages — require a template. They aren't part of free-form messaging on the WhatsApp Business Platform. Plain and formatted text plus media are the free-form set.
The window is per-customer, not per-account: Customer A's window and Customer B's window are independent, and inbound messages from customers are always delivered no matter how long it's been. So in practice, an actively-replying Clone rarely hits the wall — the window only bites when a customer goes silent for 24+ hours and you want to follow up.
You create and submit message templates in Meta's WhatsApp Manager, where each is classified as Utility, Marketing, or Authentication and reviewed by Meta (typically minutes via automated triage; up to 48 hours if it needs human review). Only approved templates can be sent — if IcloneU finds none, it tells you "No approved templates found for this account. Create and get templates approved in WhatsApp Manager first." Submitting a template that isn't approved yet won't send: "WhatsApp will reject sends until it's Approved in WhatsApp Manager."
Disconnecting a WhatsApp number
To remove a WhatsApp connection, select its row on the Connections page and click Remove in the toolbar, then confirm. Disconnecting in IcloneU stops the message pipeline — incoming WhatsApp messages stop reaching IcloneU within minutes, and the attached Clone stops auto-replying.
The Remove dialog explains that removing the connection disconnects the account and deletes its settings, while your conversation and post history is preserved and reattaches automatically if you reconnect the same account later. Permanent deletion is opt-in: a separate checkbox — "Also permanently delete all conversation and post history for this account" — is off by default, and only when you tick it does IcloneU warn that this action cannot be undone. So a plain Remove is safe to reconnect from; tick that box only if you truly want the history purged.
What disconnecting does not do: it doesn't delete the phone number from the WhatsApp Business Platform (it stays registered under your Meta Business Account, so you can reconnect it later), and it doesn't automatically revoke IcloneU's access grant on Meta's side. For a security disconnect, also revoke the integration in Meta Business Manager → Business Settings → Integrations (or Apps / System Users, depending on your setup). And note that disconnect can't recall replies the Clone already sent — WhatsApp is fire-and-forget once Meta accepts a message.
When IcloneU completed the Cloud API registration for you, it set the number's two-step verification PIN — and that PIN is never displayed anywhere in IcloneU. Removing the connection deletes the copy IcloneU kept, so treat it as gone. That costs you nothing while the number stays active: an already-active number reconnects with no registration call at all. It bites when the number has to be registered again — moving it to another provider, or reconnecting it after it stopped being active — because IcloneU will offer a fresh PIN and Meta will reject it with the previous-provider message above. Clear two-step verification for the number in WhatsApp Manager first.
Troubleshooting
Two symptoms cover almost everything: a customer's message never reaches IcloneU, or it arrives but the Clone doesn't reply. Diagnose by looking at the conversation in the Messages surface first — whether the inbound message shows up tells you which side the problem is on.
The inbound message never appears in Messages. That points at the webhook side (Meta isn't delivering to IcloneU):
- The connection status is amber/red — an authentication or permission issue on Meta's side. Try Reconnect from the Connections toolbar to refresh the grant.
- Meta's first-time review is still pending — a brand-new WhatsApp Business Account can show amber until Meta clears its review. Check the connection's detail for the specific pending step and wait.
- The number never finished activating — different from the review above, and waiting is usually the wrong move: two of the three causes need an action from you (a two-step verification PIN left by a previous provider, or a missing payment method on the WhatsApp Business Account), and neither takes effect until you reconnect. The warning you see on a return visit is the generic one whatever the cause, so don't take it as evidence that Meta is still reviewing. See Connecting a WhatsApp number for what each message means.
- The webhook isn't registered or points at the wrong place — in Meta Business Manager → WhatsApp Manager, confirm the webhook is subscribed to the messages event and shows no recent 4xx/5xx failures to IcloneU's endpoint. If it's out of sync, disconnecting and reconnecting re-registers it.
- Meta restricted the number — a low quality rating or policy issue can make Meta stop delivering. Check Meta Business Manager for any health notice on the number.
The inbound appears, but no reply goes out. That's the Clone side. Work down this list:
- No Clone is attached — open the connection's settings, pick a Clone, and Save.
- The connection is Enabled off — the master switch ignores all incoming messages while off. Turn it on.
- The 24-hour window has closed — the most common cause. If the customer's last message is more than 24 hours old, free-form replies are blocked and only a template will send. Check the customer's most recent inbound timestamp in Messages.
- The reply is held for review — if this connection's "Direct-message review" is set to "Hold until approved", the Clone's reply sits in the conversation thread waiting for your approval (an amber "approve before ..." pill shows the deadline, and past it the reply flips to "Undeliverable"); on "Auto-send after a delay" it shows "In review" and sends itself after the set minutes. Approve it in the thread, or switch the mode back to "Send immediately".
- The Clone's Knowledge library is set to refuse — "Answer from library only" on with no matching content, or lookup strictness set too tight, can silence the Clone. Loosen strictness or confirm the library covers the question.
- The Clone tried and the send failed — look for a failed outbound entry against the customer. A window-related or template-required failure means you're outside the window; other failures are worth reporting to support.
If you've worked through all of the above and a fresh test message from a different phone still doesn't get answered, escalate to support with: the connection's phone number, the affected customer's number, the timestamp of an inbound that wasn't replied to, and screenshots of the Connections page (showing status), the Messages surface (showing the inbound), and the Clone's Knowledge tab.
Frequently asked
Not the consumer-app number as-is. WhatsApp needs the number on the Business Platform. If it's on the WhatsApp Business app, Meta may offer Coexistence mode during signup — you keep the app and automate the same number through IcloneU (offered conditionally; not every number qualifies). If it's on the consumer app, you'd migrate it — a one-way move: delete the WhatsApp account to free the number, and chat history doesn't come with it. For most people a fresh dedicated business number (a second SIM or a VoIP number) is the simplest, least-disruptive path.
They're two different Meta products. The WhatsApp Business app is a free phone app for small businesses messaging customers manually — it cannot connect to IcloneU. The WhatsApp Business Platform (a.k.a. the API or Cloud API) is the programmatic product built for automation and integration — that's what IcloneU connects to. Moving a number from the app to the Platform is supported but one-way.
Meta assigns your number a messaging tier that caps how many unique customers you can start a conversation with per rolling 24 hours. New numbers start at the lowest tier (often 250 unique customers/day) and graduate automatically — up the ladder toward 1K, 10K, 100K, and unlimited — as your account builds messaging volume with a good quality rating. There's no flat tier to buy; the scaling is automatic. A low (red) quality rating pauses advancement. Note this cap is on business-initiated conversations — replying to customers who messaged you first is not what the tier limits.
Because of what your number was doing before. When a number already has WhatsApp history — most often one moving off another provider like Twilio or 360dialog — Meta treats re-registering it as a migration, and it won't complete a migration into a WhatsApp Business Account that has no payment method of its own. It's a one-time condition for activating the number, not a charge from IcloneU and not a new per-message cost: replying to customers inside the 24-hour window is unaffected. A number with no previous WhatsApp history generally never runs into it. Add the payment method in WhatsApp Manager under Business settings → Billing and payments, then reconnect the number in IcloneU.
Yes. Each number is its own Connection in IcloneU — add as many as your plan's Connection cap allows, and attach the same Clone to each or a different Clone per number (e.g. a sales persona vs. a support persona). Meta also has its own per-Business-Account number limit, but for typical use (1–3 numbers) neither cap is binding.
The documented path is to add a new Connection with the new number, attach your Clone to it, verify end-to-end, then disconnect the old Connection. In-place editing of a Connection's phone number isn't the documented flow. Approved templates are held per Business Account, so whether they carry to the new number depends on Meta's policy at the time — this carry-over is open for confirmation; expect to potentially re-submit your most-used templates. Customers messaging the old number stop reaching you once it's disconnected, with no automatic forwarding.
Meta bills conversations and template messages separately from your IcloneU plan, and its pricing model changes regularly. Exactly how IcloneU surfaces or packages those Meta costs is open for confirmation — refer to Meta's WhatsApp Business Platform pricing page for the current rate sheet, which is Meta's, not IcloneU's.
Last updated August 29, 2026 · Platform connections
