KEY TAKEAWAY
What this article covers
The WhatsApp 72-hour free entry-point window is generally tied to qualifying ad or entry sources; it is not a blanket allowance for free messaging. Learn how it differs from the 24-hour customer service window, what number screening can tell you, and how to prepare and review a contact list before sending.
Direct answer:The 72-hour free entry-point window generally refers to a billing period associated with qualifying WhatsApp Business Platform entry sources, such as certain ads. It is not a free allowance for every WhatsApp message. Its eligibility and start conditions differ from those of the 24-hour customer service window; check current account information and official policies for the rules that apply.
When preparing a WhatsApp contact list, treat number status and permission to message as separate questions. Screening may help identify formatting problems, duplicates, or some number states, but it cannot establish marketing consent, guarantee delivery, make a message free, or ensure that an account will not face restrictions. This guide explains the entry-point window, list preparation, and a practical pre-send review.
Distinguish the 72-hour entry-point window from the 24-hour service window
The phrase “72-hour free” usually refers to a free entry-point conversation billing period associated with qualifying sources, such as certain click-to-WhatsApp ads. Eligibility, supported message types, and billing treatment can change with product, region, and policy updates. Do not treat it as a general period in which any business can message any contact for free.
The 24-hour customer service window is generally associated with a user-initiated message and the business’s ability to respond under applicable rules. The 72-hour entry-point window has its own qualifying-source and triggering conditions. A past ad click—or simply having a phone number in a list—does not establish that a conversation window is open. The two windows should not be assumed to share a start time or pricing rule.
- Confirm whether you are using the WhatsApp Business Platform or another WhatsApp product.
- Check that the message came through a qualifying entry source and that current trigger conditions were met.
- Verify window, template, and pricing details in the account interface or current official guidance.
What starts the clock—and how to handle uncertain status
An entry-point conversation may depend on the user initiating a chat through a qualifying source and the business responding within a required period. The exact determination should follow current policy and account records. An ad click alone may not be enough to open a conversation. Do not substitute list-import date, screening date, or ad-impression time for the actual conversation event.
Track each contact as a separate record. Keep the entry source, time of the user’s message, time of the business’s first reply, and any account-displayed conversation status. If a timestamp is missing, a status has not updated, or the source cannot be verified, mark the record for review rather than assuming the window has started or is still active.
- Record the user’s actual message time, not only an ad click or import time.
- Use a clearly defined time zone so local and account timestamps are not mixed.
- When status is unclear, check the conversation record and current billing information.
What number screening can tell you and how to prepare a WA/WS list
Screening can help flag formatting issues, duplicate rows, or statuses the selected tool is able to identify. A result reflects information available at the time of screening. “Unknown” means the state could not be confirmed; it does not mean valid, invalid, or opted out. A number marked as available is still not proof of consent or a promise of successful delivery.
For a WA or WS task, read the tool’s task description and field definitions instead of guessing what an abbreviation means. Normalize country and area codes, remove extra punctuation and hidden characters, and check for spreadsheet formulas. A TXT file may require one number per line; an Excel file should use clear headers and only necessary fields. Test a small sample before processing the full list.
- Keep an untouched copy of the original file and clean a working copy.
- Check country codes, duplicate numbers, blank rows, and malformed entries.
- Choose a task based on its current on-screen definition; look up unclear WA/WS options.
- Separate confirmed, invalid, unknown, and error results; do not treat unknowns as ready to send.
A practical workflow from entry click to follow-up
Use four steps: confirm the entry source and the user’s permission; record when the user actually starts a conversation; check the number and conversation status; then choose a response method that fits the applicable window. If you plan to contact someone outside that window, separately verify whether an approved template and additional charges apply.
Use screening as a review aid, not as automatic authorization to send. Before a message goes out, check what the recipient was told to expect, message content, opt-out or suppression records, template status, and timing. If a number or conversation state is uncertain, pause and resolve the gap rather than treating an assumption as a confirmed status.
- Confirm how the contact supplied the number and record the scope of permission.
- Keep traceable records of the entry event, user message, and business reply.
- Check template eligibility, approval status, and current pricing information.
- Validate the fields and process with a small batch before proceeding under your compliance review.
Privacy boundaries, measurement, and the final launch check
Process only the data needed for the task, restrict file access, and follow a defined retention period. Do not share phone numbers with unauthorized parties or use a technically identifiable number as permission to market. Consent, privacy notices, and opt-out handling remain separate obligations under applicable requirements; number screening does not replace them.
Measure entry performance using distinct events: source, user-initiated conversations, timely replies, meaningful follow-up interactions, and costs. Do not judge performance solely by imported contacts or screening results. Because features and billing can change, record the rule set and measurement method used for each reporting period.
- Remove unnecessary fields and delete or archive lists according to internal retention rules.
- Recheck consent, opt-outs, templates, entry source, and timestamps.
- Keep unknown states in a review queue rather than using them as an automatic send signal.
- Before launch, confirm window and pricing details against the current account or official policy.
FAQ
Does clicking a WhatsApp ad automatically start the 72-hour clock?
Not necessarily. Eligibility can depend on the user actually initiating a conversation and on other current conditions. Confirm it in the account conversation record and current policy rather than inferring it from a click alone.
Is the 72-hour free entry-point window the same as the 24-hour service window?
No. Their triggers, start conditions, and billing treatment may differ. Check which window applies to the particular conversation and follow current WhatsApp Business Platform rules.
If screening says a number is available, does that prove marketing consent?
No. Screening reports a number state the tool could identify at that time. It does not prove consent, template approval, or message delivery.
Which WA/WS task should I choose?
Choose based on the task definitions and output fields currently shown in the tool. Do not infer a task’s meaning from its abbreviation; consult its instructions or validate the parsing with a small sample.
Conclusion
Managing a WhatsApp 72-hour entry-point window means verifying the qualifying source, recording real conversation events, and keeping billing windows separate from number screening. Prepare and review the list, then check consent, conversation status, templates, and current pricing. Pause on unknowns. These steps can reduce avoidable mistakes, but they cannot guarantee delivery, free messaging, or protection from account restrictions.
Explore the related NumSift product capabilities and result boundaries
EXPLORE MORE