​@Jorgen Eijt  That’s very interesting, for others from the community to help it might be helpful to know more about how you’ve got this setup -- is it set to trigger based on the page visit or another factor?  Also is it a SPA (single page application)?  If so you need to add Intercom differently to SPAs as well.  

It’s possible this maay be to do with a conflict with your application and Intercom’s widget as well, I would recommend opening up the Developer Console if you can do this in the webapp version and see if any errors popup there as well. 

Hope this helps you get some more answers to your issue here. 

 

Hi ​@Nathan Sudds 
It’s indeed a Single Page App based on React. We use the IntercomProvider from the ‘react-use-intercom’ package with the following config: 

<IntercomProvider
      appId="our-app-id"
      autoBoot
      shouldInitialize={true}
      autoBootProps={{
        hideDefaultLauncher: true,
        alignment: 'right',
        languageOverride: 'en',
        email: 'johan@doe.nl',
        userId: 'abc123',
        name: 'Johan Doe',
        userHash: 'some-hash',
      }}
    />

This seems to be working fine, no errors in the console and messages appear on page load. Weird thing is that if we send messages from the ‘outbound’ section, a page reload is required to show message. If we send a message directly from the ‘contacts’ section to a specific person, it does popup instantly.

Hi ​@Nathan Sudds ,

Would be great if you could find the time to have a look at this! We are in a project where we are going to decide if we will be using Intercom or not. Thx for you help!

Have a nice weekend!

Jorgen 

​@Jorgen Eijt feel free to book a time on my calendar to connect, let's figure this out! 

We definitely don't want this to prevent you from using Intercom it's probably a quick fix once someone can see it in action.

My calendar link is in my signature here, or send me a DM and we can try to connect

thx Nathan! I will be in contact next week. Have a good weekend!

Hey ​@Jorgen Eijt Paul from Weekend Support Engineering here.

Thanks for reaching out. What you’re seeing banners or chats only showing after a page refresh usually means the Intercom Messenger isn’t staying active between page views. This is common in single-page or cloud-native apps where the page doesn’t fully reload.

Can you:

• Call Intercom('boot') once when the app loads

• Then call Intercom('update') on every route or view change

This ensures Intercom stays connected and messages appear in real time without needing a refresh.

Let me know if you're using a framework like React or Angular I can share an example specific to that setup!

Hi ​@Paul Byrne 

Please refer to my previous post in this thread to see how we set things up in our application. There are no route changes involved in our current setup. It’s a SPA where the user stays on one page. The assumption is that the provider with autoboot should be sufficient.