Our agent phones have two lines. The first line is the contact centre agent number and the second line is the agent's personal DDI.
I am trying to work out the best approach to deal with calls coming in on the DDI line as I would like these to be part of the contact centre too and be able to report on call activity here. My initial thoughts are that a call will come into the DDI and if the agent is not available then it will be transfered to the CSQ for that agent.
Would it be better for the DDI line to have a "call foward all" set to the CSQ trigger and then use some enterprise parameter to see the original called number, do a lookup and send this call to the agent whose DDI it is? I'm just wondering how this is achieved programatically? Or would a better approach be for all of the agent DDI numbers to be triggers for the UCCX application? This leads to the question how many triggers can an application have?
This is always a sticky topic. Both of your ideas are possible and there isn't really a "best" option IMO.
If you create a trigger and have agents CFA their lines to it, then it is only a single trigger in CCX to configure. Agents can turn this off by disabling CFA. This could be good or bad though. CCX would need to handle redirecting the call to VM if reaching the agent fails. You remove the ability for the agent to even see the call (call waiting) since the busy trigger is set to one on their ICD line. Their only indication someone called would be if they leave a voicemail.
There is no documented limit of triggers per application. Agents cannot turn this on/off. Everything else would be the same as option one.
You can do this either with a Call Consult Transfer step or attempt an agent-based routing with the Select Resource step. For reporting reasons you would want to use Select Resource though. This also means the agent cannot answer calls at all unless they are logged in to CAD though.
Also, you could choose to route to a CSQ instead of the agent's voicemail in any of these scenarios if you wanted. CCX cannot queue callers to a specific agent and CSQs don't scale well enough to have one per agent. This somewhat depends on who is calling though. A menu option with choices works well: Press one for voicemail or two to speak with another representative."
Lastly, another scenario might be to create an IVR with a "dial by extension" concept where the customers know the extension of who they are reaching and not the direct line number. CCX could do agent-based routing as discussed above there. The advantage is that their direct line would remain untouched. This only works if they would refrain from giving that number out though.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...