Meta Account Suspension & Recovery — Capitol Bank Case Study

Overview

During the offboarding process with ^[1], their internal marketing team disclosed a recent Meta advertising account suspension that resolved itself without clear explanation. The episode illustrates a recurring pattern with Meta's enforcement system: opaque violation notices, inaccessible customer support, and unpredictable reinstatement — leaving account owners reluctant to make any changes even after the suspension lifts.

This case is useful reference material for client risk briefings, Meta account hygiene conversations, and setting expectations around platform support.

What Happened

Approximately two weeks before the offboarding call, every admin on Capitol Bank's Meta Business account received an email stating the page was "in violation of Meta's advertising standards." No specific violation was cited.

Timeline:

Suspension notice received — All admins notified simultaneously via email.
Verification attempted — Capitol Bank's team (Ben Kjorlie and Amy) completed a Meta account verification process, believing the issue was resolved.
Suspension persisted — Meta indicated the verification was insufficient; advertising remained disabled.
Unexplained reinstatement — Ads began running again on their own, with no communication from Meta explaining the reversal.

"All of a sudden, one day, it just looked like our ads were back running again. And it was the weirdest thing in the world. And we have no idea."
— Ben Kjorlie, Capitol Bank

Customer Support Challenges

Meta provides no direct customer support channel for Business account issues of this type. Capitol Bank's experience included:

No phone support — No person to call.
Forum deflection — Meta's help system routes users to community forums with low-quality, non-actionable articles.
No violation specifics — The suspension notice named a category ("advertising standards") but provided no detail about which ad, policy, or behavior triggered it.
No reinstatement explanation — The account was restored without any notification or reason given.

Ben Kjorlie noted he went down a Reddit rabbit hole and found a suggestion to mail a physical letter to Meta's Menlo Park, California address — the most actionable advice available through community channels.

Resulting Risk Posture

The unresolved ambiguity left Capitol Bank's team afraid to make any changes to the Meta account, even routine ones like revoking agency access during offboarding. Their concern: modifying anything could "explode the whole system" and trigger another suspension with no path to recovery.

This fear is rational given:
- No explanation of what caused the original suspension
- No confirmation that the reinstatement is stable
- No support channel to consult before making changes

In practice, Asymmetric's team had already been removed from the Meta account prior to the offboarding call, which resolved the access question without requiring Capitol Bank to take action.

Key Takeaways for Client Work

1. Meta suspensions can be arbitrary and self-resolving.
Do not assume a suspension means a specific policy was violated. Reinstatement may occur without any corrective action on the client's part.

2. Verification does not guarantee reinstatement.
Completing Meta's verification flow may be necessary but is not sufficient. Clients should not be told verification will fix the issue.

3. Inaccessible support is a structural risk.
Clients should understand before launching Meta campaigns that there is effectively no escalation path for account-level enforcement issues. This should be part of onboarding risk conversations.

4. Post-suspension account fragility is real.
After an unexplained suspension and reinstatement, clients may be (reasonably) reluctant to make any account changes. Plan for this in offboarding or transition workflows — ideally removing agency access before any suspension risk materializes.

5. Document account state at transition.
When offboarding or handing off a Meta account, note any open enforcement issues in the transition documentation so the incoming team is not caught off guard.

^[1]
^[2]
^[3] (if exists)
^[4] (if exists)