Hi all.

What a wonderfull tool we have here.  I'm enjoying using the help center live tool!

I have a doubt.  I thought it would be possible to track visitors steps on the page; that when a visitor enters the site an operator would be warned; and that way we could initiate contact with visitors.

I still think this must be possible but I'm too much newbie to understand how to do it!

Can you help me?

Thanks!

hi ,
Please note that in your config.  php file this optionis set to true
 // Monitor visitor activity as well as chats in the request monitor
 $conf['monitor_traffic'] = true;

Next :
Please note that after an operator logs in , he has to click on 'Live help' tab
a pop up window will comeup ,

if you have already requested a chat as a client using diff browser, than the one used for operator login , you will see the information on your operator liveHelp popupwindow , begining with word Status : Browsing . 
Below this table the end lines are two links . 
MoreInfo | Initiate

Moreinfo will give details another window with useful tracking links like Footprints , again on loast line of this table click on link View history  -  to track the user movement on website . 

Initiate.   This link will help operator to proactively initiate the chat .   Currently this mode will made the client name as guest . 

Thanks Vinit for your reply and support.

I have everything configured like you explained but I think things are not working properly. 

If you have another solution let me know.

seems to be some operator initiation problem .  try the livechat with icon prepared for cobrowse . 
Also try booting all the operator and relogin as operator . 

Else send me a dummy admin username and pass .  will check and try fix the error

Hi,

I have a problem that operators can see visitors in the monitor from every departement, even the ones that are not assigned to them.   Am I something missing here? Could this be a bug?

Version: 2. 1. 7

Thanks. 

This should not happen.  Thanks for pointing it out.  I'll look into the matter further and report back here with the bug fix.

Thanks for replying, I'm on 2. 1. 7.
Can you confirm this behavior?