Greetings. I am currently engaged in an omnichannel implementation where we are attempting to seamlessly transition a customer from a Web Messaging session to a Voice Callback. We utilize an Architect Inbound Message flow. When the customer indicates they prefer a phone call, the bot prompts for their telephone number. We then execute a ‘Create Callback’ data action to place them in the voice queue. However, we consistently observe that the callback fails to route to the agent. The interaction simply remains stuck in the queue indefinitely. Is there a specific parameter format required for the callback number when transitioning from a digital channel?
Oh, I totally know what is causing this! I build these types of callback escalations all the time and they are incredibly powerful for the customer journey! The issue is absolutely the phone number formatting! When the customer types their phone number into the web chat, it comes through as a plain string like ‘5551234567’. The Genesys Cloud callback API strictly requires the number to be in E.164 format with the plus sign and the country code! Before you trigger your Data Action in the Architect flow, you must use an expression to append the country code to the string! Once you fix the E.164 formatting, the voice queue will pick it up instantly!
Yeah, the E.164 format issue catches everyone. But also make sure you are handling the caller identity properly! When an agent gets the voice callback, they see whatever you put in the ‘Caller Name’ field of the API request. If you leave it blank or just put ‘Web Chat’, the agents get super confused and often decline the interaction, which ruins their gamification scores for acceptance rates! I always recommend pulling the customer name from the Web Messaging variables and injecting it into the callback payload.
That way, the agent sees the actual name pop up on their screen and they know exactly who they are calling back.