How to Contact Facebook Support When Your Account Is Blocked
When a Facebook account is blocked, a support request should be short, factual, and consistent. This article explains where to contact support, what to include in the first message, which screenshots to attach, and which wording to avoid so the review does not become more confusing.
When a Facebook account is blocked, the goal is not just to “write to support”, but to create a request that a specialist or review system can understand quickly. The more emotions, contradictions, and unrelated details you add to the first message, the harder the case becomes to review. It is better to start with facts: which account is restricted, when it happened, what notification Facebook shows, and what you have already checked.
Do not write that the block happened “for no reason”, blame the system, demand urgent access, or make promises that are not connected to the issue. Support needs a clear picture, not an argument: who owns the account, which access was lost, which business assets are affected, and why you believe the restriction should be reviewed.
Choose the correct support channel first
If a personal Facebook account is blocked, the starting point is usually the message shown during login. It may include a button to request a review, confirm identity, or recover access. If you still have partial access to the account, also check Account Status and in-account notifications.
If the restriction is connected to ads, Business Manager, a Page, or an ad account, it is better to start from Business Support Home or Account Quality. This connects the request not only to your text, but also to a specific object: profile, business portfolio, ad account, Page, or ad material.
If Facebook offers a specific form or a “Request review” button, use that option instead of searching for random forms online. Different forms are intended for different situations, and an off-topic request may simply not reach the right review flow.
What to write in the first message
The first message should be short. State which account is blocked, when you noticed the issue, what error text you see, and what you are asking support to do. There is no need to describe the full history of the account unless it is directly related to the restriction.
A calm wording example: “Hello. My Facebook account has been restricted. The interface shows a block message, but the exact reason is not fully clear to me. I kindly request a review of this decision. I am ready to confirm account ownership and provide additional details if needed.”
If the block affected work assets, add specific context: “The restriction affected access to a Page, ad account, or business portfolio.” It is important not to mix everything into one complaint. A personal profile, Page, ad account, and Facebook Business Manager are different objects, and support needs to understand which level you are talking about.
Which details and screenshots to attach
You can attach a screenshot of the block message, the account or business object ID, the date of the restriction, a link to the Page or profile if it is available, and a screenshot from Account Quality or Business Support Home. Two to four clear images are usually better than ten files without explanation.
If Facebook asks for a document, submit only the type of confirmation shown in the interface. The image should be readable, with no cropped edges, glare, or heavy editing. Do not attach someone else’s documents, “owner letters”, or data that does not match the account: this does not strengthen the request and may make the case less clear.
Screenshots should prove the issue, not simply show the whole dashboard. A good set includes the block notification, account status page, the specific restricted object, and, if needed, the rejected ad material or system message.
What not to write to Facebook support
Do not mention proxies, anti-detect browsers, rented accounts, or unusual work environments as an argument in your favor. These details do not explain why the restriction should be reviewed and may shift the case in the wrong direction. If the issue is technical, describe it neutrally: device, browser, login error, confirmation code, email access, or phone access.
Do not promise that “it will not happen again” if you do not understand which action caused the block. Do not send different versions of the story: today “it is a personal account”, tomorrow “it is a company account”, and later “access was lost because of hacking”. Support should see one consistent explanation.
Also avoid sending new tickets every few hours. If a case already exists, it is better to wait for a reply or add new facts to the existing case if that option is available. A repeated request makes sense only when you have found new information: a document, exact ID, screenshot of the reason, access confirmation, or a fixed issue.
How to continue the conversation after the first reply
If support replies with a template, do not send a long emotional response. Break the message down into points: what exactly was requested, which document is needed, which object is being checked, and what next step or timing is mentioned. Answer only what was asked.
If identity confirmation is requested, submit the document or video check according to the instructions. If the question is about a business asset, clarify the ID, Page name, ad account, or business portfolio. If the reason is related to ad policy, do not argue in general terms — explain which material was corrected or why you believe the decision was incorrect.
A good message to Facebook support does not guarantee that the account will be restored, but it reduces confusion. When the text is short, the data matches, screenshots are clear, and the story stays consistent from message to message, the review process has a better chance of understanding what happened and whether the decision can be reconsidered.