The short answer
Create a Business app at developers.facebook.com owned by your Business Portfolio, add the WhatsApp, Messenger and Instagram products, point their webhooks at your inbox, then create an admin System User in Business Settings, assign it your WhatsApp accounts, Pages and Instagram accounts, and generate a token for your app with expiration set to never. WhatsApp works on your own assets right away. Messenger and Instagram DMs from the public need Advanced Access through App Review.
Before you start
- A Meta Business Portfolio (formerly Business Manager) that you administer and that owns your WhatsApp Business Account(s), Facebook Page(s) and Instagram professional account(s).
- Each Instagram account linked to a Facebook Page. Instagram DMs are handled through the Page.
- A public HTTPS URL for your inbox, for example
https://inbox.yourcompany.com. Meta only delivers webhooks over HTTPS. - A privacy policy URL for your company. Meta requires one before the app can go Live.
- For App Review: Business Verification of your portfolio (Business Settings → Security Center).
Step 1: Create the app
- Go to developers.facebook.com → My Apps → Create app.
- Choose the Business app type and select your Business Portfolio as the owner. Ownership matters: the System User token in step 4 only works for apps owned by the same portfolio.
- Add the products you need: WhatsApp, Messenger, and Instagram (through the Messenger API).
Step 2: Configure webhooks
For each product, set a callback URL on your inbox and a verify token, a random string you also give your inbox (openssl rand -hex 24 works). On UnoInbox the callbacks are /webhooks/whatsapp, /webhooks/messenger and /webhooks/instagram on your install's domain.
Subscribe to these fields:
- WhatsApp:
messages,account_update,message_template_status_update,phone_number_quality_update. - Messenger and Instagram:
messages.
Your webhook must answer fast. Meta retries deliveries that time out, so acknowledge with 200 immediately and do the work in the background. UnoInbox acknowledges in under 200 ms and processes every message from a job queue.
Step 3: Complete the app settings and go Live
- App settings → Basic: add your privacy policy URL, a data deletion callback (or instructions URL), an app icon (1024×1024) and the category Messaging.
- Switch the app to Live. In development mode, Meta only delivers messages from people who have a role on the app.
Step 4: Create a System User and a non-expiring token
A System User belongs to the business, not to a person. Its token keeps working when employees leave or change their Facebook password, which is why it is the right credential for an inbox.
- Business Settings → Users → System users → Add, with the Admin role.
- Assign it your WhatsApp account(s), Page(s) and Instagram account(s) with full control.
- Generate a token for your app with expiration Never and these permissions:
whatsapp_business_messaging
whatsapp_business_management
business_management
pages_messaging
pages_manage_metadata
pages_show_list
pages_read_engagement
instagram_basic
instagram_manage_messagesTreat this token like a password. Store it encrypted and never in a URL or a log. UnoInbox seals it with 256-bit AES-GCM using a key kept apart from the database, and never shows it again after you paste it.
Step 5: Connect and verify
Give the token to your inbox. In UnoInbox, the owner pastes it once in Settings → Meta connection. The app checks it with Meta, lists every WhatsApp account, Page and Instagram account it can reach, and you assign each one to a brand. Send a test message to your WhatsApp number: it should appear in the inbox within seconds.
Step 6: App Review for Messenger and Instagram
WhatsApp needs no App Review when your app and your WhatsApp accounts belong to the same portfolio. Standard Access covers your own assets.
Messenger and Instagram are different. With Standard Access, Meta only delivers DMs from people who have a role on your app. To receive messages from real customers, request Advanced Access for pages_messaging, pages_manage_metadata, pages_show_list, pages_read_engagement, instagram_basic and instagram_manage_messages, plus the Business Asset User Profile Access feature (customer names and pictures) and, if agents need to reply after 24 hours, the Human Agent feature (replies up to 7 days after the customer's last message).
Each request needs a short use-case description and a screencast of the flow. Since October 2026, Meta classifies an app that requests Advanced Access as a Tech Provider, which adds its Platform Terms, a yearly Data Use Checkup and a data-handling questionnaire. That review covers only your own Page and Instagram account, and no other company's review status can affect yours.
Common mistakes
- App owned by a personal account or another portfolio. The System User cannot generate a token for it.
- Token generated with an expiry. It stops working after 60 days. Choose "Never".
- Instagram account not linked to a Page. It will not appear in the assets list.
- App left in development mode. Real customers' messages never arrive.
- Doing heavy work inside the webhook handler. Slow acknowledgements trigger retries and duplicate messages.
Do you need a BSP at all?
Not for access. Since Meta opened the WhatsApp Cloud API, any business can connect its own app directly. A Business Solution Provider adds an interface, support and sometimes a markup on message fees. If you want the interface without the intermediary, that is what a single-tenant inbox gives you: see single-tenant explained and how UnoInbox compares.
Meta's own references: WhatsApp Cloud API, Messenger Platform, Instagram Messaging. Meta changes its dashboards often; the names above are current as of the review date.