# Messenger native-verification checklist

Use this after the operating plan is complete. Record the real source, observation date and owner for each check. A checkbox without a receipt does not pass.

| Stable request ID | Native check | Evidence to return | Owner |
| --- | --- | --- | --- |
| `MESSENGER-EVIDENCE-PAGE-LINKAGE` | Page linkage | Dated receipt showing the intended Facebook Page is linked to the intended business and ad account | Assign |
| `MESSENGER-EVIDENCE-DESTINATION-AVAILABILITY` | Destination availability | Dated Ads Manager receipt showing Messenger is available for the selected setup | Assign |
| `MESSENGER-EVIDENCE-PERMISSIONS` | Permissions | Dated roles or access receipt for the required people and system users | Assign |
| `MESSENGER-EVIDENCE-POLICY-APPROVAL` | Policy approval | Native review or approval receipt for the ad and message flow | Assign |
| `MESSENGER-EVIDENCE-PUBLICATION` | Publication | Publication receipt with intended identity, campaign, ad set and ad IDs | Assign |
| `MESSENGER-EVIDENCE-DELIVERY` | Delivery | Test click showing the ad opened the intended Messenger thread | Assign |
| `MESSENGER-EVIDENCE-REPLY` | Reply | Test reply showing the message reached the named owner or queue | Assign |
| `MESSENGER-EVIDENCE-CRM-ARRIVAL` | CRM arrival | Destination read-back with the expected source, answers, owner and state | Assign |

For every item, record:

- state: `Unknown`, `Requested`, `Pending`, `Observed`, `Verified` or `Denied`;
- receipt reference;
- observed date and time;
- owner;
- note describing what the receipt proves and what it does not.

Launch remains **Hold for native evidence** until all eight checks are `Verified` with a reference, date and owner. If the Meta controls differ from the plan, capture the current screen and reopen review rather than guessing.