Agata

My feedback

  1. 931 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  88 comments  ·  Feedback » New features  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Agata commented  · 

    I don't think you got the point.

    When an operator uses tawk.to chat and for ANY REASONS forgets to put the status to invisible OR forgets to completely logoff when he/she is away for a wee or just because the shift is over, incoming chats will still be forwarded to the "not present" operator who will not be able to answer. This is not exactly what you expect from a valid live help chat system.

    Many other chats have this very important feature so I think you should as well.
    You don't have to invent anything new. Just copy.
    Thanks

    An error occurred while saving the comment
    Agata commented  · 

    Yes, please I badly need the autoaway, I'm fed up of missing chats.
    Thanks

    Agata supported this idea  · 
  2. 25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Feedback  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Agata commented  · 

    I don't think that visitors should see what is the name that the operator gives him at backend.
    This applies to visitors starting to chat through trigger so they are not asked to put their name and email (another problem).

    Agata supported this idea  · 
  3. 52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Feedback  ·  Flag idea as inappropriate…  ·  Admin →
    Agata shared this idea  · 

Feedback and Knowledge Base