The 24-hour customer service window, and Business Verification

Two unrelated mechanics that both gate what a business is allowed to send: a free-form reply window that opens only when a customer messages first, and a one-time verification process that lifts a new account's low daily sending cap.

Intermediate

4 min read

The rule: templates outside a conversation, free text inside one

Everything covered so far — approved templates, categories, review — applies to messages a business initiates. The moment a customer messages the business first (or replies to something the business sent), that opens a 24-hour customer service window: for the next 24 hours, the business can reply with plain, free-form text, no template or approval needed, exactly like a normal support conversation.

This is why a button tap or a free-text reply to a reminder matters beyond just "the customer responded" — it's also the mechanism that unlocks a conversational reply. A patient who taps "Cancel" on an appointment reminder and gets back a plain "Your appointment has been cancelled" isn't receiving a special new kind of message — that's a normal free-form send, made possible because the tap itself opened the window.

Why this shapes how re-engagement has to work

If a business needs to reach someone again after the window has already closed — a follow-up reminder, a "did you still want that?" nudge — that's back to template-only territory, since the customer hasn't initiated anything new. This is a real design constraint on any conversational or AI-assistant-style feature: a bot can chat freely for 24 hours after being messaged, but re-opening the conversation on its own initiative later requires an approved template, not just "send whatever the bot wants to say."

New accounts start capped, low

A brand-new, unverified WhatsApp Business Account starts at a modest limit on how many business-initiated conversations it can start per rolling 24 hours (Meta refers to this as a messaging limit tier). This is deliberately low to prevent abuse from day one — it's not a bug or a mistake in setup, it's the default starting point every new account begins at.

Business Verification: what it actually checks, and what it unlocks

Business Verification confirms that the legal entity behind a Business Portfolio is real, using official government-issued business documents — it is a check on the company, not a KYC check on an individual, and it's a separate process from App Review (which is about specific API permissions, not the business's legal identity).

What it unlocks: verification raises the messaging limit tier substantially, and it's also a prerequisite for adding additional phone numbers to an account without running into the same low unverified-account caps. It is not required for the integration to function at all — an unverified account can send real messages today, just at a lower ceiling.

What's typically needed

The business's exact legal name, matching official registration documents precisely (including any legal suffix)
A government-issued business registration document (a commercial registration, articles of incorporation, or equivalent for the relevant jurisdiction)
A registered business address matching the registration documents
A working, publicly reachable business website that clearly represents the same business being verified
A reachable phone number for a verification call or SMS
Two-factor authentication already enabled on the account, which Meta enforces as a baseline

Common, avoidable rejection reasons

Legal name mismatch — the account's name doesn't exactly match the registration document (missing/extra legal suffix, different transliteration).
Address mismatch — a different office/branch address than what's on the registration document.
Illegible or cropped documents — low-resolution scans, glare, missing corners.
Expired documents — an out-of-date registration certificate.

Verification review typically takes a few business days, though it can range from under a day to considerably longer if Meta requests additional documentation. Rejection isn't final — Meta generally states a reason, and resubmission after fixing the specific issue is normal, not exceptional.

The separate, later step: the "Verified" checkmark badge

Passing Business Verification does not automatically grant the green "Verified" checkmark seen on some business profiles. The checkmark is a separate, optional, discretionary badge Meta grants to businesses with public brand recognition, applied for after verification. It's a trust/visual signal for end users — messages send identically with or without it, so it's worth pursuing later as a polish item, not a blocker for anything technical.