Using Intercom in a WebView Inside a Partner App That Also Uses Intercom | Community
Skip to main content

Hi Intercom team,

I’m working on a web app that’s embedded in a partner’s mobile app via WebView. Both our web app and the partner’s mobile app use Intercom, but each with a separate workspace.

Are there any known issues or best practices when two Intercom instances (in different workspaces) are running in this setup? Specifically:

  • Could this cause conflicts with sessions or the Messenger widget?

  • Does Intercom handle isolation properly in WebViews?

  • Is there anything we should do to avoid interference between the two instances?

Or maybe to put it more simply, could having 2 separate Intercom integrations at the same time cause any issues.

Hey ​@Alan Ibarra 👋 Jacques here from Intercom Support. I hope all is well today!

Intercom does not support running two Messenger widgets (from different workspaces) at the same time in the same web page or WebView context. If both are initialized, only one will remain active—the other will be automatically unloaded. This can cause confusing or inconsistent user experiences.

If your partner’s mobile app and your embedded web app both try to load their own Intercom Messenger in the same WebView, they will conflict. There’s no built-in isolation between two Intercom instances in the same browser context.

To avoid issues, only load one Messenger per context. If both must be present, ensure they are never initialized in the same WebView or page. Alternatively, consider using Intercom’s multi-brand features within a single workspace, or use a different provider for one of the contexts. There’s no supported workaround for running two Intercom Messengers from different workspaces together in the same WebView.

If you have a specific technical setup or need more tailored advice, let me know the details and I can help further.

Reply


Terms & Conditions