Messaging restrictions
Page restricted from messaging
In short
A messaging restriction is when Meta stops a Page from sending Messenger messages for a period of time after a policy violation, such as using Message Tags outside their approved use cases or taking high-volume actions that might bother others. Meta still enforces it in 2026. Sending through the API while restricted returns error code 10, subcode 1893063, and you can appeal through Page Status or Business Support Home.
What gets a Page restricted
Under Meta's Messenger Platform policy, using Message Tags outside their approved use cases can get a Page restricted from messaging. Meta sends details of the violation by email and to the Page Support Inbox.
An example in Meta's Page Integrity documentation is the SPAM violation type, described as high-volume actions that might bother others.
Users can block, mute or report a Page at any time, so Meta recommends tracking block and spam report rates in Page Insights.
Page status and restriction length
The Page Integrity API that Meta announced in January 2026 shows 4 Page status levels. Restrictions of type page_messaging and page_messaging_api come with an expiry date; examples in Meta's documentation include both 1-day and 3-day restrictions.
If you believe the restriction is a mistake, you can appeal through Page Status or Business Support Home.
- ok: the Page is in good standing
- warning: the Page has received a warning
- restricted: some Page features are restricted
- suspended: the Page is suspended
Errors you'll see and rate limits
If a Page is temporarily restricted, sending through Meta's API returns error code 10, subcode 1893063 (temporarily restricted from sending messages), which Meta added to its error codes documentation on June 25, 2026.
Beyond policy enforcement, the Messenger Platform also has API rate limits:
- The Send API allows 300 text message calls per second per Page
- Audio or video messages are limited to 10 calls per second
- Sending more than 40 messages per second may pause sending temporarily
- Sending too many messages in a single conversation can also be limited
What sellers who broadcast should do
- Remember that being able to send doesn't mean it's safe. Only send content that is genuinely relevant to that group of customers.
- Use labels to segment customers and send to the right group instead of everyone on the Page.
- Send in batches instead of firing off a huge volume at once, and don't send several messages in a row in one conversation.
- Check blocks and spam reports in Page Insights after every send. If they go up, send less often.
- Use Message Tags only for cases Meta allows, and check your email and Page Support Inbox when you are notified of a violation.
Need to message customers who last wrote more than 24 hours ago? See sending with Facebook-approved templates
FAQ: Page restricted from messaging
- How many days does a messaging restriction last?
- It depends on the case. Restrictions of type page_messaging come with an expiry date, and examples in Meta's Page Integrity documentation include both 1-day and 3-day restrictions.
- What is error 1893063 in Messenger?
- Error code 10, subcode 1893063 means the Page is temporarily restricted from sending messages. Messages sent through Meta's API during this time fail until the restriction expires.
- Where do I appeal a messaging restriction?
- You can appeal through Page Status or Business Support Home, according to Meta's Page Integrity documentation, and see the violation details in your email and the Page Support Inbox.
- How often can I broadcast without getting restricted?
- Meta has not published a block rate or message count that is safe from restrictions. There are only technical API limits, such as 300 calls per second per Page, which don't guarantee you won't be restricted under the policy. The best approach is to send relevant content, use labels to pick your audience, and track blocks.
Sources
Last checked against Meta's documentation on September 14, 2026
Ready to start broadcasting?
15-day free trial. No credit card required.
Use the Chrome extension