Why don't I see any Pages after connecting?

If your Pages don't appear in Reply200 after linking your Facebook profile, it's usually due to one of the following reasons:

• Your profile doesn't have the necessary permissions for those Pages on Facebook.
• You didn't select the required Business Managers or Pages during the Facebook authorization flow.

How to fix it

1. Assign your Facebook profile to a Page

1. Go to business.facebook.com, then Settings
2. In the left sidebar: Accounts, then Pages
3. Select the target Page from the list
4. Click the "Assign people" button (top of the right panel)
5. In the "Add people and set permissions" dialog:
   • Select the person from the list (or search by name/ID/email)
   • Choose a permission level on the right side:
     • Partial access — Content, Messages, Community activity, Ads, Insights
     • Full control — Everything (toggle "Everything" on)
6. Click Assign

Important: If you granted these permissions after you already linked your profile to Reply200, you need to go through the linking process again.

2. Select the needed Business Managers and Pages during Facebook authorization

During the connection flow in Reply200, make sure you select:

• The correct Business Managers
• All Pages you want to manage with Reply200

If some Pages were skipped during authorization, simply reconnect your profile and select all relevant assets.

3. "This profile is already connected to another account"

This means that some or all of the Pages you're trying to add are already linked to a different Reply200 account. Before adding them to your new account, go to the other account and unlink those Pages first.

4. Adding more Pages to an existing connection

You don't need to create a new account. Use the + button in your dashboard to add more BMs or Pages. If the Pages belong to a different Facebook profile, make sure you're logged into that profile before clicking the button.

5. Connection issues on Safari

If the connection flow fails or doesn't complete, try using Chrome instead. Safari can sometimes interfere with the OAuth redirect.

If none of the above resolves it, reach out to us — we're happy to help.