Is popup the only way to allow website navigation and chat at the same time?

[shivanuo]

Im asking this because if i disable the popup setting, the chat get reset as soon as the person click on another page, the page reload, so the chat, and everything is deleted and it shows as the webvisitor has left.

The popup is the only way to chat and allow people to browse the website, what is kinda wierd having to do that.

Is this right or i did setup something wrong?

 

[Constantinos Constantinou]

Hello @shivanuo ,

You are not doing something wrong. Popout indeed is to cater to the cases that you would like to support the continuity of the chat session to your website.
Chat initially built for single page applications, and the popout was our intermediate solution, for the cases that they would like to avoid termination of the chat session.
We know that this is not the perfect solution, but it is an intermediate solution.

You know very well that this is a work in progress, and more features will come in the near future.

Thank you for your support.

 

[shivanuo]

Ok, but take this as a feedback, i tried as i was already using 3CX, but we got a ton of complains because of this and i had to go back to the older chat system, the popout will only work on Desktop not for mobiles, so is a huge issue, some way to keep the chat session open while browing whiout popout needs to be added.

Just a random suggestion, do not inmidiately close the session when the chat is closed, add something like 2-5 minutes timeout on the 3CX side, then use a randomly generated ID when chat is initiated, store that on a cookie on client side and on 3CX as well, if the chat is re-open have the chat check that with 3CX side stored IDs that are still valid, if exist, re-join chat, if not start new.

Is not perfect but a LOT better than what it is now, at least as a option, and its simple.

 

[Constantinos Constantinou]

Hello @shivanuo,

Thank you for your feedback.
Can you please clarify what do you mean by "will only work on Desktop not for mobiles". This was a known issue, that was fixed on or current release. Is this the case.

Thank you also for your suggestion about the session lifespan.