About the platform flow itself and disconnect

I'm new here, so I don't know if the category that I'm posting is the correct one, please forgive me.

Is possible to disconect a customer (guest) from the platform? I know we can disconnect calling the action (closeSession) from websocket. But is there anyway to close the session from the platform?

Maybe using conversation disconnect? (I didn't find the messager configuration to change the default value for this feature)

Welcome @Katekko - yes we are releasing new Conversation Disconnect feature for Web Messaging: it is now in Beta (which explains why you don't see it yet), but will become Generally Available most likely next Wednesday.
See Idea https://genesyscloud.ideas.aha.io/ideas/DXWMM-I-26 for tracking.

1 Like

Thanks for the answer! Is the same email to login this ideas website?

About the question:
So to the session getting away today, we need to wait the timer (72) over or call the disconnect action, right?

About the business:

It's seems confusing to me how the web messagin need to work. Talking about the token that I need to generate and send to the platform, every token it's a different session, every user need a different token, but the same user need to mantain the token forever? Or he can generate another token and use another session?
But if he use another session, how can he retrieve the old history of the old session? Need I keep all the tokens that the user X generated in my backend?

It's seems hard to me answer this questions. In my company, we are going to join a meeting with some consultant to help clarify some. But I will appreciate if you answer this questions that I made.

Thank for your time!

At the moment, each browser would have a distinct token that identifies the user on that browser.
If you want to resume sessions across different browser, we currently support Authenticated Web Messaging: this relies on your IDP service to support OpenID Connect. As soon as End-User signs-in to your brand, the "authenticated" messaging session can be resumed, on any browser or device. Basically the conversation would follow to End-Users wherever they log-in to the brand. For future we are contemplating other ways to resume session, that don't necessarily require End-User to authenticate with the brand.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.