A place to ask questions, connect with others, and stay in the know
A lot of this depends on how you're gathering your custom attributes. Are they something from the call that generated the callback (assuming this isn't a web or process generated callback) or data gathered once a callback enters queue?If you're transferring values from the call to the callback, I'd recommend creating the callback in a handler so you have access to both interactions and then you can easily get attributes from the call and assign them to the callback then replace the call with the callback or perform whatever other business logic you require to get the callback dealt with.Where you should do this specifically relies a lot on where you are creating your callback today: is the call already in queue? Is this callback generated by a pre-queue check? Is this a web callback?Then it's just a question of creating queue columns associated with the attributes in IA then assigning permissions to appropriate users to see the queue columns.
Every year, Genesys® orchestrates more than 70 billion remarkable customer experiences for organizations in more than 100 countries. Through the power of our cloud, digital and AI technologies, organizations can realize Experience as a Service℠, our vision for empathetic customer experiences at scale. With Genesys, organizations have the power to deliver proactive, predictive, and hyper personalized experiences to deepen their customer connection across every marketing, sales, and service moment on any channel, while also improving employee productivity and engagement. By transforming back-office technology to a modern revenue velocity engine Genesys enables true intimacy at scale to foster customer trust and loyalty.