Messenger error 200: pages_messaging_phone_number not reviewed

Code 200 with subcode 2018027 is the App Review wall for a narrower capability than ordinary messaging: pages_messaging_phone_number, the permission behind Messenger's customer-matching feature, which lets a business open a conversation by supplying a phone number instead of a Page-scoped ID. Like its sibling 200/2018028, it works for app admins, developers and testers before review and fails for everyone else, and the message says so verbatim.

Customer matching was always a restricted, US-oriented feature with additional strings attached: Meta's error table also documents subcode 2018021, "requires phone matching access fee to be paid by this page," reflecting that access historically involved a fee and explicit approval beyond ordinary review. If your integration merely replies to people who message the Page, you do not need this permission at all, seeing 2018027 usually means a recipient object was built with phone_number where an id (PSID) belongs.

The pragmatic question is therefore not "how do I pass review" but "should this code path exist." Messaging by phone number without prior interaction is exactly the cold-outreach pattern the platform has been closing down; the durable architectures start conversations through entry points the person initiates, m.me links (see the link generator), chat plugins and ads, then message the resulting PSID.

{
  "error": {
    "message": "(#200) Cannot message users who are not admins, developers or testers of the app until pages_messaging_phone_number permission is reviewed and the app is live.",
    "type": "OAuthException",
    "code": 200,
    "error_subcode": 2018027,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Design conversation starts around user-initiated entry points and PSIDs; keep phone numbers as CRM metadata, not addressing keys. If a business case truly needs phone matching, treat the permission, fee and review as a project with lead time, and isolate the capability behind a feature flag so its absence cannot break ordinary replies. The review-wall family is compared on the code 200 page and in the troubleshooting guide.