Jump to content


Chat BOT transfering to human operator


5 replies to this topic

#1 fabiobr

    Advanced Member

  • Members
  • PipPipPip
  • 136 posts

Posted 08 June 2017 - 09:09 PM

Hi, it's me again... sorry :)

Recentely I enabled the chat BOT and configured it to always start the chat, allowing visitors to talk to human operator if needed. But many visitors (most of them) are leaving the chat even without finding an answer, and my guess is because when they click to "talk to human operator" the chat is finished and back to the "insert your information" page. Would be better if when visitors click in the "talk to human operator" link, they are redirected automatically to an avaliable operator or to the waiting queue. Well, this is my suggestion. Thanks!

Best regards,

Fabio

#2 Patrick Keil

    Administrator

  • Administrators
  • 3242 posts
  • LocationSingen, Germany

Posted 09 June 2017 - 06:23 AM

Hi Fabio,

Thanks for your thoughts.

Did you configure some required input fields? If you did, this is something we shouldn't ignore, don't you think?

Cheers.

#3 fabiobr

    Advanced Member

  • Members
  • PipPipPip
  • 136 posts

Posted 09 June 2017 - 01:02 PM

Hi Patrick,

Yes, there are some required input fields, but visitors already filled them before entering in the chat (Chat BOT)... Maybe I am missing something...


Thanks!

#4 Patrick Keil

    Administrator

  • Administrators
  • 3242 posts
  • LocationSingen, Germany

Posted 12 June 2017 - 12:03 PM

Hi,

I can't reproduce this. I only see the details form when I haven't entered my details. If I did this before, I go straight to the operator.

#5 Oleh Vasylyev

    Advanced Member

  • Members
  • PipPipPip
  • 44 posts

Posted 12 June 2017 - 02:22 PM

Hello

We have same issue.

Attached Image: chat-bot-input.gif
(gif-animation of this issue)

Patrick, you have access to our test-server - you can quick check there.

#6 Patrick Keil

    Administrator

  • Administrators
  • 3242 posts
  • LocationSingen, Germany

Posted 13 June 2017 - 06:42 AM

Thank you, we fixed this for 7.0.5.0.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users