Hi team
Looking at this resource centre article:
https://help.mypurecloud.com/articles/use-the-prioritized-caller-selection-feature-to-configure-caller-id-information/
if this is set in order for:
- Call Source
- Trunk
When a call is made outbound on behalf of queue that has no outbound caller ID set for it, what would you expect the behaviour to be in the following scenarios?
- User making the call has a DID in their profile
- User making the call does NOT have a DID in their profile
In both scenarios, the trunk itself has an outbound caller ID set.
In running through a few scenarios this is what is happening if the user has a DDI...:
- Create a queue with no caller ID set - in the caller ID for the queue that field value remains NULL
- Edit the queue to add a caller ID to it, but then delete that caller ID - the field doesn't revert to NULL but now becomes +undefined
In the case of #1, the user's DDI presents, in the case of #2 the next item in the prioritisation list presents.
Before I go and reopen my case, how do you all interpret the resource centre article around this?
There's still some discrepancy in how Genesys' tech writers on the resource centre and the Care team interpret this behaviour.
#Routing(ACD/IVR)
#Telephony
------------------------------
Vaun McCarthy
------------------------------