How does Mr. AI verify the Page subscription?
In step 5 choose Check current subscription. Mr. AI checks the token’s Page identity and app, then reads this Page’s subscribed fields for that app. The check is read-only. Choose Enable required events only when you authorize adding missing fields.
- 1
Save the matching App ID, App Secret, Page ID and Page token in step 3.
- 2
Run Check current subscription. If all four fields are present, no change is needed.
- 3
If fields are missing, choose Enable required events. Mr. AI adds the required fields while keeping existing subscriptions, then checks the result.
- 4
If the status is Verified, continue to the real-message test. If confirmation is pending, test messages and run Check again later. For invalid tokens, denied access or missing fields, follow the displayed recovery steps.
- 5
If an update times out or its result is uncertain, use Check again before repeating Enable required events.
Required Meta permissions
Before verifying the Page subscription, confirm Meta granted pages_messaging, pages_manage_metadata, pages_show_list and pages_read_engagement for this setup.
How to grant them
- 1
Open Graph API Explorer and select the same Meta App used in Mr. AI.
- 2
Open User or Page and choose the intended Page. If Meta first requires approval using your user account, approve access, then return and select the Page. Mr. AI needs the Page Access Token, not a User token.
- 3
Open Permissions, click Add a Permission and add the four permissions above, especially pages_manage_metadata.
- 4
Click Generate Access Token and approve access to the intended Page in Meta. A permission name appearing in the list alone is not proof it was granted.
- 5
Return to Mr. AI and click Check current subscription in step 5. For a first connection, save the Page token and matching credentials in step 3 first.
In the image: 1 — User or Page; 2 — Permissions, then Add a Permission; 3 — Generate Access Token. Select the same app and intended Page.
You normally do not need to run /subscribed_apps requests manually in Graph API Explorer. Mr. AI checks and repairs the Page subscription. Choose Check current subscription, then Enable required events only if required fields are missing.
If access is still denied
After approving permissions, generate a fresh Page Access Token with the required permissions, update the Page token saved in Mr. AI step 3, then retry the check. Previously generated tokens are not guaranteed to acquire newly granted access automatically.
First check pages_manage_metadata for this Page/app connection. Other Page access restrictions can also cause permission_denied; the general error alone does not identify the missing permission.
When should I contact support?
If the check still fails after reviewing permissions and the Page token, note the visible error, setup step and approximate time. Send these details to support without including tokens or app secrets. You do not need to run API requests or change Meta API versions to complete this guide.
Verification errors
Permission denied?
Return to Mr. AI and click Check current subscription again. Try this check before replacing saved credentials. Still denied after approval? Generate a fresh Page Access Token with the required permissions, save it in step 3, then retry the check.
Valid credentials but no verified app subscription?
Check that the Page token was generated by the expected app and that its App ID/Secret match. Other subscribed apps do not prove this app is configured.
Does Verified mean all messages arrive?
No. It proves the Page fields observed at that check, not App Webhook fields or end-to-end delivery.
Meta Page subscription reference
Configure Messenger webhooks and all four required fields
Test Messenger and troubleshoot missing human replies
Check the result
Read the latest check result and app identity. Recheck pending evidence, then perform a real-message test.