Suggested by Gal Baruch – Accepted – 1 Commentsare there any APIs that could be used for adding users on an automated daily basis?
we are going through system migration changes and need to configure all the agents in the administration portal and also users in the Davici Creators Studio,
after we create the Agents in UCCE servers.
until now we needed to create an agent user id in the AMC IA Configuration Manager,
importing could work for bulk users, at the start, not for day to day changes.
we have created an automated process that gets the Users info from A.D. configures phone extensions in the CUCM, creates Agents in the UCCE servers, each one according to his/hers designated call center, all automated using different API's.
releasing API's we could use (in combination with the OKTA automated login) would be very much helpfull for agent managment.
THANKS and best regards
Suggested by Kris Soekiatno – Accepted – 1 CommentsWhen customer ends the call just before agents, they will get this Release AMCAdapter error message. In this very case only, can we silent the error message and do not popup any error or message and let the solution release or clear the call session/handle when user click on Release button in CTI Toolbar.
However, we have seen the same Release AMCAdapter error message on several cases. ie, when call was made and disconnect immediately, when call reached to VM and disconnect; when the call got into busy signal and disconnect, when the call was invalid and disconnect. Those cases were producing the same error messages and we do not want to silent the popup error.
Ability to overtake extension in CTI login process.
Currently when an extension is “used” by CTI and a user didn’t log out properly (or when used CTI in incognito window which got closed), then there is a conflict in logins when another user (or the same user after closing incognito window) tries to log into CTI with the same extension. It returns an error and blocks the login. This requires to use Agent Logout Tool. But the logout tool is given to supervisors (at least at Home Depot), so it adds logistics to ask supervisors to log users out. A much cleaner experience would be if the function of Agent Logout Tool was integrated into login process, so that when a user is logging in, say, with agent ID 12345 and extension 34567 but this extension is already “used” by CTI, then CTI UI asks the user if he wants to overtake the extension in CTI. Similar like Avaya phones have a function to take over an extension if you are logging in with an extension which is already logged in for another phone. This can be achieved by running agent logout tool algorithm on the background upon conflicted login, because you already have all the inputs when agent is trying to log in: you know the system he is using, his login, Agent ID, extension, password (if applicable) because the agent entered them in the login window. Such “extension overtake” ability would make it a clean experience rather than login frustration currently experienced by our associates daily. Imagine trying to log in your gmail mailbox and getting a blocking error that you already logged in from another computer, so call our 1-800 support number to log you out of that other computer so you could log in here. Adoption rate wouldn’t be there.
Make agent ID non-mandatory for logout via Agent Logout Tool
Suggested by Raymond Garcia – Accepted – 0 CommentsIt would be nice to have some settings in the admin portal that allow for quick edits to the salesforce toolbar's css. For instance, the ability to change the font size in critical places could save time and make slight, yet valuable customizations very clear and easy to edit by a less technical user.
Suggested by Michal Raz – Accepted – 1 Comments
We would like to disable the screen popup when the call is from an internal extension.
Our internal extensions have only 3 digits. When an agent receives an internal call – there is no need to open a new session in the WebUI.
We would like AMC to check whether it is possible to define that if the call is identified by AMC as an internal call (i.e. under 5 digits) – the ANI details of this call should not be communicated to SAP.
Scope Metals Group
After our agents finish calls they have ACW (After Call Work) status automatically turned on for 30 seconds. But when they need more time to do the work after the call, they press on ACW button on Avaya within those 30 seconds and it makes ACW status stay 'on' idefinitely, until it's manually switched to another one. However, in DaVinci ACW button is greyed out and isn't clickable when already in ACW status. Agents can't wait for 30 sec for it to expire and quickly click it because it's inconvenient and also always leaves the risk of another call coming in at that moment.
Can we please make ACW button active and in black font, so that users can click it and don't need to go back to avaya phones for that?