Hi Ragheb
-
We implemented a very similar use case in the past, although using Salesforce Open CTI instead of Service Cloud Voice.
Our approach was:
- The inbound call arrives in Genesys Cloud.
- We use a Data Action to call a Salesforce API, passing the caller's phone number.
- If a matching customer is found, the API returns the customer information, including the assigned Account Owner (or the corresponding agent).
- Based on the API response, we use the Preferred Agent routing method in Genesys Cloud to route the interaction directly to the assigned agent whenever they are available. If the preferred agent is unavailable, the interaction follows the normal routing strategy.
-
This architecture worked very well because the routing decision was made entirely within Genesys Cloud based on Salesforce data retrieved in real time.
I haven't implemented this specifically with Service Cloud Voice, so I'm not sure whether the same approach is officially supported in that integration, but from a Genesys Cloud perspective, using a Data Action together with Preferred Agent routing is definitely a viable solution.
------------------------------
Kaio Oliveira
GCP - GCQM - GCS - GCA - GCD - GCO - GPE & GPR - GCWM
PS.: I apologize if there are any mistakes in my English; my primary language is Portuguese-Br.
------------------------------