Article summary
The WhatsApp 72-hour concept is not a universal free-marketing period. Learn how entry-point conversations differ from customer-service windows and templates, and how WA number checking fits into list preparation without replacing consent or pricing rules.
The phrase “72 free hours on WhatsApp” is often stretched into a claim that a business can send any marketing message for three days after a customer writes. That is too broad. The 72-hour concept is generally associated with qualifying free entry-point conversations, while customer-service windows, template categories, and current message pricing are separate rules.
Direct answer: Do not treat 72 hours as a universal free allowance. Confirm whether the conversation came from an eligible Click-to-WhatsApp ad or Facebook Page call-to-action, identify the actual start time, and check what happens outside the window. Number checking can organize platform-status fields; it cannot change pricing, create opt-in, or guarantee account safety.
Separate the three windows that are commonly mixed together
| Concept | Question it answers | It is not |
|---|---|---|
| User-initiated service window | When a business can respond inside a customer conversation | A free period for every marketing template |
| Free entry-point conversation | Whether a qualifying ad or Page entry creates a defined window | A 72-hour window for every source |
| Template and message category | What can be sent outside a window and how it is charged | Free because a number is registered |
| Pricing version | How the current country and category are priced | A rule copied permanently from an old screenshot |
Pricing and definitions can change. Use the current Meta WhatsApp Business Platform pricing documentation and account notices, and record the review date in the operating procedure.
When does the 72-hour period begin?
The decisive event is not when a company uploads a list. It is when an eligible user entry creates the relevant conversation. Operations should retain the ad or Page entry, the user-message timestamp, and the conversation identifier. A phone number or registered status cannot calculate this window.
A conversation from another source should not automatically inherit the free-entry rule merely because the user once sent a message. Confirm the qualifying entry, start condition, reset behaviour, and eligible message types in the current Meta documentation.
What number preparation can and cannot solve
| Preparation step | It can help with | It cannot establish |
|---|---|---|
| Country-code normalization | Format and matching consistency | That a person still uses the number |
| WA Registration Check | Whether the task returns a WhatsApp registration signal | Opt-in |
| WA Activity Check | Task-returned activity time and active-day fields | A future reply or purchase |
| Deduplication | Keeping one operational record per normalized number | Eliminating complaint risk |
| Consent suppression | Preventing opted-out records from re-entering | Something number checking generates automatically |
Conversation-window management and number quality are both useful, but they belong to different evidence layers. A properly formatted, registered number may still have no permission and no qualifying free conversation.
Prepare a WA list for AppShai
- Select only numbers with a defined provenance and processing purpose.
- Normalize each country calling code and deduplicate.
- Create UTF-8 TXT with one phone number per line.
- Select the required task on the AppShai WhatsApp Number Checker page.
- Export Excel and retain the unedited result.
- Store task result, check date, and CRM permission in separate fields.
Excel and CSV are not the direct upload formats. Do not place chats, customer names, advertising parameters, or other business fields in the TXT file.
Choose the WhatsApp task by the question
| Task | Core result fields | Question it supports |
|---|---|---|
| Registration / Fast Registration | Phone and registration status | Was a registration signal returned? |
| High-precision Registration | Phone, business-account field, mapped phone | Are those additional fields required? |
| Activity Check | Phone, activity time, active days, mapped phone | Is activity-related grouping needed? |
| Profile Picture Check | Phone, business-account field, picture, mapped phone | Are picture-related fields needed? |
| Full Format | Activity, demographic, image, business and mapping fields | Does every column have a defined business purpose? |
More fields are not automatically better. The existence of a free entry-point conversation is determined by entry and conversation data, not by the number-checking Excel file.
From ad click to follow-up: the operating chain
- Explain in the ad and entry flow who the user will contact and why.
- Store the entry source and timestamp of the user’s message.
- Use the conversation window first to answer the user’s request.
- When a template is required outside the window, confirm category, approval, and current pricing.
- Respect opt-outs and synchronize the suppression list.
- Write conversation outcomes to CRM instead of substituting number-check fields for interaction.
Why number checking is not an anti-ban guarantee
Account restrictions can involve permission, complaints, message quality, sending patterns, business authenticity, and platform policy. A registration check can reduce work spent on numbers without a returned registration signal, but it cannot make unsolicited bulk messaging compliant.
A free entry-point window is not a risk exemption either. Businesses still need to follow the WhatsApp Business Messaging Policy, including obtaining permission before contact and respecting opt-out requests.
Measure the entry-point funnel without mixing evidence
Separate ad clicks, conversation starts, in-window resolution, out-of-window templates, replies, opt-outs, and business conversions. Calculate counts and costs at each stage instead of treating “message sent” as the final outcome.
A number-check result can support the number layer. Window utilization comes from timestamps, and customer value comes from orders and CRM. This separation shows whether the problem lies in the entry, response time, message quality, or list governance.
Pre-launch review
- Is the rule taken from the current Meta documentation, with a review date?
- Did this conversation come from a qualifying free entry point?
- Can the team store the user-start and window-end timestamps?
- Are template category and price outside the window confirmed?
- Are provenance, permission, and opt-out traceable?
- Does the selected number-checking task match the needed Excel fields?
The 72-hour window is a specific conversation rule, not a marketing shortcut. Keep entry, time, template, permission, and number-result data separate so one attractive phrase cannot drive an incorrect sending decision.
