Feature Request: Adjust Chat Timeout Period
AnsweredHello Support,
I am aware that currently the chat timeout period for idle visitors chatting through desktop is 20 minutes, and 5 minutes via mobile. The fact that neither are customisable has been a concern to our team for quite some time now.
Are there any plans to make the timeout adjustable? if not, what are your suggestions to avoid these early timeouts, mostly speaking of chats via mobile SDK.
Thanks in advance,
Alex
-
Hi Alex,
Thanks for sharing your feedback regarding the session timeout behaviour. Currently, we have no plans to make this customisable per account but we are getting more requests for it on the mobile SDK due to network connections being less stable on mobile devices.
For your case specifically, are your sessions expiring because of a wait time that is longer than 5min? We are looking at improving the persistent nature of the mobile SDK conversations next year and it may include things like push notification support. Once we have something to share that is more concrete, we will let you know.
-Ramin
-
+1
-
We should be able to customize this... And/or force end the chat...
-
Hey guys,
I would like to bring up this topic again. We would like to change the timeout time to a longer peroid. It would help us a lot, if you could think about this feature once again.
We use your chat tool for a live stream as a support for the viewers. Beside that we use it to communicate with the technical guys who set up and manage the stream. So it is important for us, that the technical guys will not disapear after 20 Minutes.
Thank you very much,
Niko
-
...and for us we would like the time out to be shorter unless you give us the ability to end the chat as the agent.
-
Our organization would like to have more control over closing chat. Please make this into a feature going forward.
-
Please add the ability to customize the chat session timeouts and allow agents to close chats. Adding it as a option to enable/disable agent access to this feature from the admin UI might be a good solution.
We use Routed Chats and when a customer forgets to close their window/widget they repeatedly come back into the queue, passing from one user to the next each time. Not only is this a distraction for agents but it also causes real chats to be unfairly distributed. In our scenario an actual chat discussion can last 20 - 60 min. One of these stale sessions lasts only a couple minutes as the agent checks to see if the user is actually returning for further support or not. It's an embarrassing scenario, as we're practically pleading with them to close the widget.
Zendesk Chat works well but lack of this basic feature is significant shortcoming. Please consider adding this feature so we can recommend Zendesk chat to others in the support community. -
Following - We also need this option asap!
-
Waiting for this feature launch !
-
Would love this feature as well.
-
Agree with all the above comments.
In our case, visitors are returning to the chat long after the agent has left the chat, the chat duration does not take into account the fact that the chat has ended once before. The chat duration then continues to count the 'new' conversation between the same customer and a different agent. This is harming our reports as we see abnormal long durations and the last agent to handle the chat with the customer ends with a very long resolution time.
- Ability to force close/end a chat
- Ability to edit chat timeout period
- If the agent left the chat, the customer should be made aware that the chat is closed, and would have to specifically choose a) my request is not done b) new chat
Please sign in to leave a comment.
11 Comments