Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
Manual messaging, avoiding broadcasts or completing Meta business verification does not remove restriction risk by itself. The real review must cover whether recipients expected the message, explicit WhatsApp consent, new-chat behavior, user feedback, connected tools and whether the business uses the Business App or Cloud API.
Starting new chats is disabled while replies in existing conversations may remain available.
During a temporary restriction, the account may still receive calls, reply in existing chats and use current groups, but it cannot start new chats and some features are unavailable. Features may return when the timer ends, yet repeated behavior can lead to longer or more severe enforcement.
The business cannot message a number it has not chatted with before, while replies in existing conversations may remain available.
The timer only shows the remaining period of the current restriction; it does not identify the root cause or prove a permanent resolution.
The quality rating in WhatsApp Manager is an important signal, but it may not fully explain behavior enforcement inside the mobile Business App.
Business Verification confirms the business entity; recipient consent, message expectations, spam feedback and messaging rules still apply.
The return of new-chat functionality after the timer ends does not mean the messaging workflow is safe. The same restriction can return unless the root cause is corrected.
WhatsApp does not publicly disclose every detection signal. The points below are not proof of a violation on their own, but they are the strongest technical and operational checks when temporary restrictions keep recurring.
Entering a phone number for a booking does not automatically prove that the customer wants follow-up messages on WhatsApp. Consent should be explicit, separate and provable.
Even when messages are sent manually, the same opening text sent to many new recipients in a short period can resemble automated or unwanted outreach.
If the recipient does not recognize the business, was not expecting the message or the booking number is incorrect, user feedback can damage account reputation.
Bulk-sending extensions, click automation, session cloning tools or unofficial clients used with WhatsApp Web can create risky account behavior.
Rapid use of the same account by several staff members across devices should be reviewed for session security and sending patterns.
A long template containing shortened links, payment links, files and location details in the first contact can increase distrust when the recipient was not expecting the message.
Without phone verification, a customer may enter the wrong number. The message can reach an unrelated person and trigger a block or spam report.
If manual first messages, Cloud API templates, shared-number use and CRM replies are mixed in one operation, the rules applied by each product must be mapped clearly.
The first diagnostic question should be: “Which product shows the restriction?” A timed warning in the mobile app and a WABA status in WhatsApp Manager can expose different screens, logs and appeal paths.
The goal is not merely to wait for the timer to expire, but to identify and change the workflow that keeps reproducing the restriction. After each step, test carefully with low-volume, genuine bookings.
While the timer is active, do not try to reach new people through another device, employee or method. Reply only where necessary in existing conversations.
Collect the last contacted number, message text, timestamp, booking record, sending device, connected tools and screenshots in one case file.
Sign out unknown sessions and remove any bulk-sending, click automation, accelerated copy-paste or unofficial WhatsApp client tools.
The checkbox should not be preselected and should clearly state what messages will be sent, the business name and how the customer can stop communication.
After booking, show a “Confirm via WhatsApp” button that lets the customer send a prefilled message containing the booking reference.
For business-initiated messages outside the 24-hour service window, use an approved utility template directly related to the booking and do not mix marketing into transactional updates.
The company name, booking reference and reason for contact should appear in the first sentence. Unnecessary links, media, payment prompts and long explanations should come later.
For the Business App use the in-app review option; for a WABA use the violation record in Business Support Home. Not every spam enforcement action is eligible for appeal.
The flow below helps customers expect the message, reduces incorrect-number risk and makes the consent record technically provable.
Validate E.164 format, country code and, where appropriate, use SMS or WhatsApp verification during booking.
Use a separate checkbox and record the text version, timestamp, source page, booking ID and phone number.
On the booking success page, provide a WhatsApp link with a prefilled message so the user sends the first message.
Use the customer name, booking reference, date and transfer details in the reply, without adding generic campaign copy.
Clear opt-out requests such as STOP should be removed from manual and automated contact lists without delay.
Replace bracketed fields with business and booking data. These examples are not legal advice and should be reviewed for the business sector and applicable law.
Turkey (Turkish)
Germany (German)
Worldwide (English)
I agree to receive booking confirmation, driver details and transfer updates from [COMPANY NAME] via WhatsApp. I can opt out at any time by replying STOP.Hello, I would like to confirm my transfer booking [BOOKING ID] via WhatsApp.Hello [NAME], [COMPANY NAME] has received booking [BOOKING ID]. Your transfer date is [DATE] and pickup location is [LOCATION]. Reply here if anything needs to be changed.Hello {{1}}, your booking {{2}} has been received. Your transfer date is {{3}} and pickup location is {{4}}. Reply to confirm the details or request a change.Evidence comes before an appeal narrative. Using the same case format for every restriction makes it easier to identify which message, device or workflow may have triggered the issue.
Include only information you can verify. Instead of broad claims such as “we did nothing wrong,” provide the event date, messaging flow, corrective actions and consent evidence.
Hello,
Our WhatsApp Business account using [PHONE NUMBER] received a temporary new-chat restriction on [DATE / TIME]. The account is used through [BUSINESS APP / CLOUD API].
We reviewed the messaging flow, linked devices and booking records before the restriction. We confirmed that no unofficial extension or automation was used / removed the identified tool. We added a separate WhatsApp consent step to the booking form, retain consent records with timestamps and booking IDs, and allow the customer to initiate the conversation wherever possible.
Event submitted for review:
- Restriction time: [DATE / TIME]
- Booking ID related to the last message: [ID]
- Message purpose: Booking confirmation / transfer update
- Consent evidence: [SUMMARY]
- Corrective actions: [ITEMS]
Please review the account and the relevant policy or spam signals again.Not by itself. The WhatsApp Business Messaging Policy requires both the person's phone number and opt-in permission confirming that they want to receive subsequent WhatsApp messages or calls. The consent should be clear and provable.
No. Manual sending does not remove risks such as unexpected messages, repeated text sent to many new recipients, blocks or spam reports.
The quality rating is an important WABA signal, but a temporary new-chat restriction in the mobile Business App can appear on a different product surface. First determine whether the restriction is app-level, phone-number-level or WABA-level.
No. Business Verification helps confirm the business identity and entity, while messaging policy, opt-in requirements and user feedback still apply.
No. Cloud API provides a more auditable setup, templates and webhook records, but explicit consent, correct template categories, the 24-hour window and message quality rules still apply.
The user's latest message to the business opens or refreshes the rolling 24-hour customer service window. Outside this window, a business-initiated message requires an approved template.
It is not recommended. The timer only indicates that the current enforcement period has ended. If consent, message text, new-chat rhythm, devices and feedback remain unchanged, the restriction can return.
No. Meta's policy enforcement documentation states that some spam violations may not be appealable and the business may need to wait for the restriction period to end.
One of the strongest approaches is to let the customer send a prefilled WhatsApp message from the booking confirmation page. The customer initiates the chat and knows why the conversation is starting.
No. Only Meta or WhatsApp makes the final enforcement and appeal decision. A technical review can help correct consent flows, integrations, devices, templates and evidence.
Opt-in, 24-hour service window, message templates, user feedback and enforcement rules.
Rules covering spam, repeated unwanted contact, unofficial clients and abuse.
Warnings, escalating restrictions, Business Support Home, webhooks and appeals.
The area for reviewing WABA violations, active restrictions and review options when available.
The WhatsApp Business App, Cloud API, booking opt-in flow, connected tools and Meta support evidence can be technically reviewed. Final account decisions are made only by Meta or WhatsApp.
Eka Software and Information Systems is not affiliated with Meta or WhatsApp and does not represent itself as an official Meta partner. WhatsApp and Meta are trademarks of their respective owners.