Title: 2 issues found
Last modified: January 19, 2017

---

# 2 issues found

 *  [mekuf](https://wordpress.org/support/users/mekuf/)
 * (@mekuf)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/2-issues-found/)
 * Hello, i have 2 issues with latest version of live chat.
 * 1st. when operator is online and user after filling forms starts chat it connects
   very slow, maybe 3-5 seconds. is there way to make it superfast like different
   chat plugins?
 * (!!!) 2nd. When user in chat writes us, we answer user = all good. we can speak.
 * But!
    when operator was, for example, a little bit slow with answer (maybe talk
   to another user) and user closes chat window… when we answer, user chat windows
   starts loading…loading…loading. and no result. it infinitely loads with no window
   opening with new answer.
 * how to solve ?
    thank you.

Viewing 1 replies (of 1 total)

 *  Thread Starter [mekuf](https://wordpress.org/support/users/mekuf/)
 * (@mekuf)
 * [9 years, 4 months ago](https://wordpress.org/support/topic/2-issues-found/#post-8673667)
 * about 2nd issue with “reopening chat window” after operator answer;
 * i checked this scenario at yith plugin demo, running admin console and frontend
   at the same time. i found this issue happens even at your demo.

Viewing 1 replies (of 1 total)

The topic ‘2 issues found’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/yith-live-chat_c6e6f3.svg)
 * [YITH Live Chat](https://wordpress.org/plugins/yith-live-chat/)
 * [Support Threads](https://wordpress.org/support/plugin/yith-live-chat/)
 * [Active Topics](https://wordpress.org/support/plugin/yith-live-chat/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/yith-live-chat/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/yith-live-chat/reviews/)

 * 1 reply
 * 1 participant
 * Last reply from: [mekuf](https://wordpress.org/support/users/mekuf/)
 * Last activity: [9 years, 4 months ago](https://wordpress.org/support/topic/2-issues-found/#post-8673667)
 * Status: not resolved