Thanks Richard...
Correct, the queue setting is persistent, but the caller id is not.
Our use case calls for agents making outbound calls to have their caller id's display, even if they're calling on behalf of a queue.
We're unable to use full direct dial number associations to the users because we want to check the presence of the user prior to sending the call to them, so that the calling party can opt out to the team queue if that person is offline or busy, etc...
------------------------------
Dean Thames
Koch Business Solutions
------------------------------
Original Message:
Sent: 06-12-2019 14:06
From: Richard Schott
Subject: PureCloud for Chrome / Configurable Caller ID
No, we do not use the custom phone settings in the chrome client.
That setting should persist if you select "remember last selected queue" in the client settings.
If the outbound number is going to be persistent, then it really should be set as a line setting in the telephony or queue configuration, not something left up to the client.
------------------------------
Richard Schott
Genesys - Employees
Original Message:
Sent: 06-11-2019 11:10
From: Dean Thames
Subject: PureCloud for Chrome / Configurable Caller ID
Bump on this thread... Wondering if the custom properties on the phone settings is an option here? Something like this?
Anyone have any use cases for this?
------------------------------
Dean Thames
Koch Business Solutions
Original Message:
Sent: 06-10-2019 16:01
From: Dean Thames
Subject: PureCloud for Chrome / Configurable Caller ID
Hi All,
I'm liking the purecloud for chrome extension quite a bit, but there's always that one thing....
On the configurable caller id setting, is it possible to make that setting persistent? Even if it's an application file that needs to be modified.
#Telephony
------------------------------
Dean Thames
Koch Business Solutions
------------------------------