Embedded chat - how to store the position of the chat when page changes

Hi guys,

Problem: As soon as people have the chat open (to answer some questions ) and start clicking to different pages the chat closes.

Q: How to prevent the chat from closing/refreshing when an user is still browsing different pages on the website?

All the best,

Bob

Hi @VP_Bob love the username!  I added your post here where we have the answer. If you have any other questions, please let us know!

Hi Liz,

Thank you, does this mean there is no solution yet?

All the best,

Bob

Hi @VP_Bob I’m afraid this isn’t a feature we have in our chat forms, but if you have any other questions, please let us know. 

Hi Liz,

Thank you. Do you know if there is a topic in the community about a feature that stays open on multiple pages?

I think there can be a simple solution as some kind of extra layer on top of each page.

Regards,

Hi Liz

Our website displays collections of digitized artworks from Slovak galleries. 

We would like to use the Typeform chat as an interactive guide that teaches users how to create a thematic personal collection of artworks. There would be instructions like "search for a keyword and select an artwork that catches your eye", "select a color from the scale and see what artworks come up" etc. Therefore we would like the chat to remember its state while the state of the website changes (search is performed, filters are applied etc.). 

User would get to a certain "slide" of the Typeform that displays an instruction, then perform the action on the website (search, save an artwork) and return to the Typeform to continue to the next slide. Currently, the form resets to the beginning after every page load. It remembers the answers selected, but the user has to click through the form every time.

You can let me know how "development costly" would this feature be. We develop features for the website ourselves, so we understand if some feature is not worth the production time. If this is outside of your scope or focus, we will think about a different solution for the use-case.

Thank you!

Hi @Michaeka.k This isn’t a feature we currently have in production, but thank you for sharing this feedback! This is really helpful for our developers to understand another use-case behind this.