Sending stopped, the dashboard shows the account is restricted, and the team is waiting for a decision. What happens in the following hours determines whether this becomes a two-day hassle or the loss of months of history and relationships.
In this article
The first hours determine the extent of the damage
Sending stopped, the dashboard shows the account is restricted, and the team is looking at you waiting for a decision. What happens in the following hours determines whether this becomes a two-day hassle or the loss of months of history and relationships.
The instinctive reaction is the worst of all: trying to send again, hastily creating another number, and blasting the same list. This usually turns one problem into two.
Continue reading for free
Fill out once and unlock this and all other blog articles. We charge nothing — we just want to know who we are writing for.
Takes 20 seconds. Prefer to talk directly on WhatsApp?
First: stop everything
Pause any ongoing blasts, including on other numbers in the same account. If the restriction was quality-related, continuing to send from others accelerates their decline as well.
Second: read the reason
The dashboard shows the status and, almost always, the violation category. Without this, you’ll be fixing blindly. Note the error code shown during sending — it differentiates quality, permission, and deactivated account.
Third: secure the history
Conversations are not on Meta: they are in the system you use. Confirm that the history is saved and exportable. Companies that handled directly via API without CRM discover at this moment that they have nothing to take with them.
Fourth: notify those in the middle of a conversation
Those who were negotiating cannot be left in the void. If there is another channel — phone, email, Instagram — now is the time to use it. A lead cooling off due to silence costs more than the number.
What not to do under any circumstances
- Create a new number and blast the same list on the same day.
- Try resending to see if it’s back.
- Open a new account to bypass the restriction.
- Disappear on customers who were being served.
The first three are exactly the behaviors Meta identifies as attempts to circumvent — which turn temporary restrictions into permanent bans.
Where to start
Have this written down before you need it: who pauses, who reads the reason, who notifies customers in service, and what the alternative channel is. A half-page script turns panic into procedure.
Frequently asked questions
What to do immediately when the number is blocked?
Stop any ongoing blasts, including on other numbers in the same account, because if the restriction was quality-related, continuing to send accelerates their decline as well. Read the reason on the dashboard and note the error code, which differentiates quality, permission, and deactivated account. Confirm that the conversation history is saved and exportable in your system. And notify those who were in active negotiation via another channel. What must never be done under any circumstances is trying to resend to test, creating a new number and blasting the same list, or opening a new account to bypass the restriction.
The number is an asset. The relationship is another.
With history in VeyloCRM, losing the number means losing the channel — not the memory of the operation nor the contacts in negotiation.