There's not a wait to resolve this natively with Intercom I'm afraid. There two solutions you could take:
- Change the ID of the button when the modal is open, thus preventing the tour from starting
- Use Javascript API to invoke the tour at just the right time.
The tours product is not currently able to make assessments based on the state of your app, so this is something you have to bear in mind when creating your tours. 😃
Thank you for the details. I am using the Intercom Tour feature so I can keep my engineering team focused on other issues. If I need to involve engineering I might as well have my engineers create the whole tour and reduce my spend on Intercom.
Hello @denna 👋,
I'm suggesting to delay the product tour launching or add some time (3-4 sec) until that button will be active for users.
Delaying the product tour allows you to launch them in the fully loaded application (Just for 2-3 Sec's). How to do that?
Now about second workaround, which I think more helpful in your case: You can make certain buttons non clickable for certain kind of time. Like until page is fully loaded or until the product tour will be started (For 3-4 Seconds). Intercom using this workaround, like if you go to Outbound -> Chats or Posts - You can see that New button is not clickable for certain kind of time (3-4 Sec).
You can check following video to better understand the use case:
https://youtu.be/KO3okd5RICs
If you can look at the following video, you can find that New button is not clickable for some time. I think following solution will be so helpful in your case and it's requires less development.
Let me know if you have any question about this topic, Always happy to help.
It's not really possible without tweaking it at the engineering level- as Roy has pointed out.
Thank you for including the video!
I run into a similar issue when a modal on our page is obscuring the element focused by the Product Tour.
I just wanted to let you know that the workaround “Change the ID of the button when the modal is open, thus preventing the tour from starting” does not work. When there is no element matching the selector, Intercom displays the tour anyway. It just does not highlight any element. 😔
The “Time on current page” workaround also does not work reliably in our situation. It makes it even worse because user has more time to open the modal.
Opening the tour using JavaScript API is a no-go for us too. We have a dedicated person that creates the tours. She creates multiple tours per day and we do not have the capacity to release new JavaScript triggers (duplicating the logic she would otherwise specify in the configuration of the tour) every time a new tour is added just to prevent displaying them when modal is open.
Making elements not clickable for certain time is also a no-go in this situation. The modal is opened when user wants to browse a gallery of photos on the page. We do not want prevent users from browsing the gallery in first few seconds after the page loads just because there could be a Product Tour targeted on them.
It would be great if there was one of the following settings in the Intercom Product Tour:
- Do not display the tour step until element matching the selector is present on page.
- We could then specify the selector as: `body:not[class*=”Modal--open”] .element-triggering-tour`
- Do not display the tour step while element matching the selector is obscured by another element.
- This would fix the problem universally even for apps that do not have special CSS class on body element when modal is open.
