Pass values to the in-queue call flow

[Dana_SF]

hi all, I'm having a hard time passing values from my IVR flow to the hold queue I've tried various combinations of set and get participant data (set in the IVR get in the in-queue flow) and update data with no luck. I've read the docs on the methods and tried a dozen different combinations but nothing I do will let me pass string values from the IVR to the in-queue call flow, can anyone link me a specific example of how this is done? I'm still searching docs and the developer forum, I'll post if i find the solution

[MelissaBailey]

The variables used in the update data action only exist for the currently executing flow. To get data from one flow to another, use the set participant data in the 1st flow and the get participant data in the 2nd flow. The Attribute Name must be exactly the same for the value to be retrieved. It is case-sensitive, and a space at the beginning or end will not match.

[Dana_SF]

Thanks for the quick response Melissa. I'll create a test flow to isolate just the set and get and post here if I can't get it to work.

my problem is the participant variable name I set in the main IVR flow is not available to me in the Get participant data statement in the in-queue flow, it refuses to let me type the name of the variable I know exists (the participant variable I set in the other flow) and it doesn't show in the in-queue flow list of available variables to access. Very confusing. I've triple checked capitalization, etc... Good to know I'm on the right path, must be something simple i'm doing wrong

[MelissaBailey]

Attribute name can be a variable but it's normally easier to use literal mode. In the Get Participant Data action, match the attribute name to the one set in the Set Participant Data action, and set Variable to Assign as a new variable to contain the value found.

In this example, Task.myValueVar will be "hello".

[anon28066628]

Hi Dana,

"it refuses to let me type the name of the variable I know exists (the participant variable I set in the other flow) and it doesn't show in the in-queue flow list of available variables to access."

Participant Data doesn't autocomplete; they're not like flow or task variables that are known to the flow and have flow variable types (user, skill, datetime, etc.). Participant Data are simply key/value pairs added to the conversation, typically strings. The name key is an arbitrary string, and the string must match precisely when set in one flow and retrieved in the other ("myValue", from Melissa's example).