Agents get kicked off FOP while changing Status/Presence
Hello,
I have a strange problem with my Agents.
Everytime they put themselves as "out for lunch" or "meeting" they get kicked out of FOP2. And the presence is not changed.
If I am doing this for their account or for mine, it works like a charm.
The users are all assigned to a template and have the plugin 'Change Presence Menu' and 'Presence Box DND Integration' enabled in their account.
What is the reason that this does not work properly? Do I need to give them some special permission?
I am thankful for any help,
cheers!
I have a strange problem with my Agents.
Everytime they put themselves as "out for lunch" or "meeting" they get kicked out of FOP2. And the presence is not changed.
If I am doing this for their account or for mine, it works like a charm.
The users are all assigned to a template and have the plugin 'Change Presence Menu' and 'Presence Box DND Integration' enabled in their account.
What is the reason that this does not work properly? Do I need to give them some special permission?
I am thankful for any help,
cheers!
Comments
Running latest FOP2 Version (just made an upgrade yesterday) and still have the problems.
Running latest Chrome Version, too.
FOP2: Version 2.30.03
Chrome: 47.xxx
Also it needs to be said that after getting kicked out the agents are unable to login again! They need to complete reload the website/open up the website again to login again.
Updates are all up-to-date as far as I can tell
I have activated the following:
Change Presence Menu
Presence Box DND Integration
Both running latest version.
My agents use this to change status (see screenshot).
Activated Debug in FOP2 Admin, here is the log:
You should see that there is no "update" on any button... So should be all up to date
I just tried calling through Support line for US but could't get through. How can I reach live help besides via phone?
Thanks.
After a quick review, the problem was caused by having users with no password set. Changing presence asked for a password again, disconnecting them from the original session. Although FOP2 should handle empty passwords more gracefully, it is not a good idea to leave users with empty passwords.
So, setting up passwords to FOP2 users fixed the issue.