2. RE: Retrieve the skills variable in another Call Flow ?

I assume you mean flow A is using the Set Participant Data action. The most likely cause of flow B not finding the value using the Get Participant Data action is a name mismatch. Make sure the Attribute Name in both actions is exactly the same--it is case-sensitive, with no spaces at the beginning or end.

One small note: you could use the Transfer to Flow action instead of Transfer to Number to get from flow A to flow B. This is not causing your problem, it's just a little easier than having to remember what phone number matches to flow B.

3. RE: Retrieve the skills variable in another Call Flow ?

Thank you Melissa for your reply, when I add action "Get Participant data" on the second call flow, I can retrieve the variable set on the first call flow, however I cannot add it as skill with Transfer to ACD, I put expression like "Flow.Skill" on ACD Skill 1, but I got this error:

I assume you mean flow A is using the Set Participant Data action. The most likely cause of flow B not finding the value using the Get Participant Data action is a name mismatch. Make sure the Attribute Name in both actions is exactly the same--it is case-sensitive, with no spaces at the beginning or end.

One small note: you could use the Transfer to Flow action instead of Transfer to Number to get from flow A to flow B. This is not causing your problem, it's just a little easier than having to remember what phone number matches to flow B.

Thank you Melissa for your reply, when I add action "Get Participant data" on the second call flow, I can retrieve the variable set on the first call flow, however I cannot add it as skill with Transfer to ACD, I put expression like "Flow.Skill" on ACD Skill 1, but I got this error:

I assume you mean flow A is using the Set Participant Data action. The most likely cause of flow B not finding the value using the Get Participant Data action is a name mismatch. Make sure the Attribute Name in both actions is exactly the same--it is case-sensitive, with no spaces at the beginning or end.

One small note: you could use the Transfer to Flow action instead of Transfer to Number to get from flow A to flow B. This is not causing your problem, it's just a little easier than having to remember what phone number matches to flow B.

Thank you Melissa for your reply, when I add action "Get Participant data" on the second call flow, I can retrieve the variable set on the first call flow, however I cannot add it as skill with Transfer to ACD, I put expression like "Flow.Skill" on ACD Skill 1, but I got this error:

I assume you mean flow A is using the Set Participant Data action. The most likely cause of flow B not finding the value using the Get Participant Data action is a name mismatch. Make sure the Attribute Name in both actions is exactly the same--it is case-sensitive, with no spaces at the beginning or end.

One small note: you could use the Transfer to Flow action instead of Transfer to Number to get from flow A to flow B. This is not causing your problem, it's just a little easier than having to remember what phone number matches to flow B.

Thank you Melissa for your reply, when I add action "Get Participant data" on the second call flow, I can retrieve the variable set on the first call flow, however I cannot add it as skill with Transfer to ACD, I put expression like "Flow.Skill" on ACD Skill 1, but I got this error:

I assume you mean flow A is using the Set Participant Data action. The most likely cause of flow B not finding the value using the Get Participant Data action is a name mismatch. Make sure the Attribute Name in both actions is exactly the same--it is case-sensitive, with no spaces at the beginning or end.

One small note: you could use the Transfer to Flow action instead of Transfer to Number to get from flow A to flow B. This is not causing your problem, it's just a little easier than having to remember what phone number matches to flow B.

Thank you Melissa for your reply, when I add action "Get Participant data" on the second call flow, I can retrieve the variable set on the first call flow, however I cannot add it as skill with Transfer to ACD, I put expression like "Flow.Skill" on ACD Skill 1, but I got this error:

I assume you mean flow A is using the Set Participant Data action. The most likely cause of flow B not finding the value using the Get Participant Data action is a name mismatch. Make sure the Attribute Name in both actions is exactly the same--it is case-sensitive, with no spaces at the beginning or end.

One small note: you could use the Transfer to Flow action instead of Transfer to Number to get from flow A to flow B. This is not causing your problem, it's just a little easier than having to remember what phone number matches to flow B.

Thank you Melissa for your reply, when I add action "Get Participant data" on the second call flow, I can retrieve the variable set on the first call flow, however I cannot add it as skill with Transfer to ACD, I put expression like "Flow.Skill" on ACD Skill 1, but I got this error:

I assume you mean flow A is using the Set Participant Data action. The most likely cause of flow B not finding the value using the Get Participant Data action is a name mismatch. Make sure the Attribute Name in both actions is exactly the same--it is case-sensitive, with no spaces at the beginning or end.

One small note: you could use the Transfer to Flow action instead of Transfer to Number to get from flow A to flow B. This is not causing your problem, it's just a little easier than having to remember what phone number matches to flow B.

Thank you Melissa for your reply, when I add action "Get Participant data" on the second call flow, I can retrieve the variable set on the first call flow, however I cannot add it as skill with Transfer to ACD, I put expression like "Flow.Skill" on ACD Skill 1, but I got this error:

I assume you mean flow A is using the Set Participant Data action. The most likely cause of flow B not finding the value using the Get Participant Data action is a name mismatch. Make sure the Attribute Name in both actions is exactly the same--it is case-sensitive, with no spaces at the beginning or end.

One small note: you could use the Transfer to Flow action instead of Transfer to Number to get from flow A to flow B. This is not causing your problem, it's just a little easier than having to remember what phone number matches to flow B.

where Task.SkillNames is the string collection variable of skill namesFlow.Skill is the string variable of the skill name you retrieved from the Get Participant Data actionTask.Skills is the skill collection variableTask.DefaultSkill is the default skill variable to use if Flow.Skill is not found in Task.SkillNames

Thank you Melissa for your reply, when I add action "Get Participant data" on the second call flow, I can retrieve the variable set on the first call flow, however I cannot add it as skill with Transfer to ACD, I put expression like "Flow.Skill" on ACD Skill 1, but I got this error:

I assume you mean flow A is using the Set Participant Data action. The most likely cause of flow B not finding the value using the Get Participant Data action is a name mismatch. Make sure the Attribute Name in both actions is exactly the same--it is case-sensitive, with no spaces at the beginning or end.

One small note: you could use the Transfer to Flow action instead of Transfer to Number to get from flow A to flow B. This is not causing your problem, it's just a little easier than having to remember what phone number matches to flow B.

where Task.SkillNames is the string collection variable of skill namesFlow.Skill is the string variable of the skill name you retrieved from the Get Participant Data actionTask.Skills is the skill collection variableTask.DefaultSkill is the default skill variable to use if Flow.Skill is not found in Task.SkillNames

Thank you Melissa for your reply, when I add action "Get Participant data" on the second call flow, I can retrieve the variable set on the first call flow, however I cannot add it as skill with Transfer to ACD, I put expression like "Flow.Skill" on ACD Skill 1, but I got this error:

I assume you mean flow A is using the Set Participant Data action. The most likely cause of flow B not finding the value using the Get Participant Data action is a name mismatch. Make sure the Attribute Name in both actions is exactly the same--it is case-sensitive, with no spaces at the beginning or end.

One small note: you could use the Transfer to Flow action instead of Transfer to Number to get from flow A to flow B. This is not causing your problem, it's just a little easier than having to remember what phone number matches to flow B.

New Best Answer

About Genesys

Genesys® powers 25 billion of the world’s best customer experiences each year. Our success comes from connecting employee and customer conversations on any channel, every day. Over 10,000 companies in 100+ countries trust our #1 customer experience platform to drive great business outcomes and create lasting relationships. Combining the best of technology and human ingenuity, we build solutions that mirror natural communication and work the way you think. Our industry-leading solutions foster true omnichannel engagement, performing equally well across all channels, on-premise and in the cloud. Experience communication as it should be: fluid, instinctive and profoundly empowering.