Would like to get some additional details on the differences between the following 2 wrap-up codes
ININ-OUTBOUND-TRANSFERRED-TO-QUEUE
ININ-OUTBOUND-TRANSFERRED-TO-FLOW
My understanding is that for #1, this refers to a wrap-up that appears when call gets assigned to queue but did not reach agent. Would like to clarify what exactly does #2 mean for getting transferred to a flow? What does this 'flow' refer to?
Hi Declan, I have taken a look, but im still unsure of what this 'flow' exactly represents in Genesys' terms
Can help to elaborate a little more on what the 'flow' in 'transferred to flow' means?
Hello Declan, If I could be very specific:
From the context of an outbound call dialing, in what situations will the wrap-up code return ININ-OUTBOUND-TRANSFERRED-TO-FLOW?
From my interaction timeline, it seems like such calls are assigned to agent where agents are 'alerted' but did not pick-up phone. Can i understand it as a wrap-up code to tag such scenarios where calls is assigned to agents but not picked-up in time before it is dropped by user?
ININ-OUTBOUND-TRANSFERRED-TO-QUEUE: Indicates that the outbound call was transferred to a queue where an Agent will pick up the conversation.
ININ-OUTBOUND-TRANSFERRED-FLOW: The call is transferred to a Genesys Cloud Architect flow. An Architect flow is the entry point in Genesys Cloud for the different communication channels (e.g. voice, messaging, email). A flow is an executable decision tree where you can build logic to determine how you want to route the cucstomner or do additional work before the customer is routed to the destination.