Skip to main content
Question

Need human help: Instagram connected to old Manychat account, owner unreachable

  • September 23, 2026
  • 1 comment
  • 5 views
Chauxfit

Hi! I own the Instagram account Chaux Maria | Fitness | Entrenamiento y Nutrición ​@Chauxfit . It's connected to a Manychat account called "Maria chaux", created by a former admin who no longer responds. I sent an access request with no answer. The AI assistant confirmed I need a manual review with proof of ownership, but it can't create a ticket and I have no requests in my Help Center account. Could a moderator or the support team please help me disconnect my Instagram so I can connect it to my own account? I can provide proof of ownership. Thank you!

    1 reply

    SumGenius
    Forum|alt.badge.img
    • SumGenius
    • Smooth talker
    • September 24, 2026

    Most of this you can fix yourself, and it isn't a ManyChat problem.

    The old workspace reaches your Instagram through a token the former admin granted using their own
    Facebook profile. As long as that person still has a role on your Page or sits in your Business Portfolio, that token keeps working. Remove them and it dies.

    Go to Meta Business Settings, People, and remove the former admin. Then check your Page roles under Page settings and Page access, and remove them there too. Then open your own Facebook profile, Settings and Privacy, Settings, Business Integrations, and remove ManyChat if it's listed.

    That kills the old workspace's access to your account immediately. You don't need the ex-admin and you don't need a ticket for it.

    The one piece that does need support is if you want that same Instagram inside a new ManyChat workspace. They hold an internal record of which account owns the channel and there's no self-serve way to release it from someone else's workspace. Keep pushing on the ticket for that part, with your proof of ownership.

    One last thing to check either way: Page settings, Instagram, Conversation Routing. If a default app is set there, everything else goes silent with no error. Worth a look once you've cleaned up the permissions.

    Community Terms & ConditionsAccessibility statement