Genesys Cloud - Main

I will post here and Developer Forum.

When I use Developer to chat it routes the interaction through the Widget that then follows the Chat flow that I have built out to do schedule evaluations, and other fun stuff. When the customer uses the code from Developer it seems to be bypassing the Chat flow and going directly to the queue. My question is, "targetType" and "targetAddress" below, if they change this to Flow, and Flow Name, respectively, will that force it to the Chat flow that is associated with the Widget? 

<script> window._genesys = { "widgets": { "webchat": { "transport": { "type": "purecloud-v2-sockets", "dataURL": "https://api.mypurecloud.com", "deploymentKey": "", "orgGuid": "", "interactionData": { "routing": { "targetType": "QUEUE", "targetAddress": "Avtex Test Queue", "priority": 2 } }

#Routing(ACD/IVR)

------------------------------
Angelia Harper
Avtex Solutions, LLC
------------------------------

Hi Angelia,

A few questions:

Where did you generate the code snippet?
What widget version are you using?
Do the versions match between your org and the customers?
Are you using a deployment? That is where I configure the flow.

Thanks,

------------------------------
Daniel McLeod
Qsect LLC
------------------------------

Original Message:
Sent: 05-01-2020 10:45
From: Angelia Harper
Subject: Chat Flow Routing

I will post here and Developer Forum.

When I use Developer to chat it routes the interaction through the Widget that then follows the Chat flow that I have built out to do schedule evaluations, and other fun stuff. When the customer uses the code from Developer it seems to be bypassing the Chat flow and going directly to the queue. My question is, "targetType" and "targetAddress" below, if they change this to Flow, and Flow Name, respectively, will that force it to the Chat flow that is associated with the Widget?

<script> window._genesys = { "widgets": { "webchat": { "transport": { "type": "purecloud-v2-sockets", "dataURL": "https://api.mypurecloud.com", "deploymentKey": "", "orgGuid": "", "interactionData": { "routing": { "targetType": "QUEUE", "targetAddress": "Avtex Test Queue", "priority": 2 } }

#Routing(ACD/IVR)

------------------------------
Angelia Harper
Avtex Solutions, LLC
------------------------------

Yeah, me not doing this piece before is hard. So, I set up the V2 Widget, assigned the call flow there. Went to the Developer Chat, selected the development, and the queue. Copied that code, gave them the Key and the script/code. They then do their addition to their website and this is where we see it is bypassing the flow.

------------------------------
Angelia Harper
Avtex Solutions, LLC
------------------------------

Original Message:
Sent: 05-01-2020 11:46
From: Daniel McLeod
Subject: Chat Flow Routing

Hi Angelia,

A few questions:

Where did you generate the code snippet?
What widget version are you using?
Do the versions match between your org and the customers?
Are you using a deployment? That is where I configure the flow.

Thanks,

------------------------------
Daniel McLeod
Qsect LLC

Original Message:
Sent: 05-01-2020 10:45
From: Angelia Harper
Subject: Chat Flow Routing

I will post here and Developer Forum.

When I use Developer to chat it routes the interaction through the Widget that then follows the Chat flow that I have built out to do schedule evaluations, and other fun stuff. When the customer uses the code from Developer it seems to be bypassing the Chat flow and going directly to the queue. My question is, "targetType" and "targetAddress" below, if they change this to Flow, and Flow Name, respectively, will that force it to the Chat flow that is associated with the Widget?

<script> window._genesys = { "widgets": { "webchat": { "transport": { "type": "purecloud-v2-sockets", "dataURL": "https://api.mypurecloud.com", "deploymentKey": "", "orgGuid": "", "interactionData": { "routing": { "targetType": "QUEUE", "targetAddress": "Avtex Test Queue", "priority": 2 } }

#Routing(ACD/IVR)

------------------------------
Angelia Harper
Avtex Solutions, LLC
------------------------------

Hi Angelia,

I sent you a private message to gather more details you may not want public.

If you cannot share the information I requested, the next step I recommend would be testing the code you sent them on a basic test site and see if you get a different result.


Thanks,

------------------------------
Daniel McLeod
Qsect LLC
------------------------------

Original Message:
Sent: 05-01-2020 11:55
From: Angelia Harper
Subject: Chat Flow Routing

Yeah, me not doing this piece before is hard. So, I set up the V2 Widget, assigned the call flow there. Went to the Developer Chat, selected the development, and the queue. Copied that code, gave them the Key and the script/code. They then do their addition to their website and this is where we see it is bypassing the flow.

------------------------------
Angelia Harper
Avtex Solutions, LLC

Original Message:
Sent: 05-01-2020 11:46
From: Daniel McLeod
Subject: Chat Flow Routing

Hi Angelia,

A few questions:

Where did you generate the code snippet?
What widget version are you using?
Do the versions match between your org and the customers?
Are you using a deployment? That is where I configure the flow.

Thanks,

------------------------------
Daniel McLeod
Qsect LLC

Original Message:
Sent: 05-01-2020 10:45
From: Angelia Harper
Subject: Chat Flow Routing

I will post here and Developer Forum.

When I use Developer to chat it routes the interaction through the Widget that then follows the Chat flow that I have built out to do schedule evaluations, and other fun stuff. When the customer uses the code from Developer it seems to be bypassing the Chat flow and going directly to the queue. My question is, "targetType" and "targetAddress" below, if they change this to Flow, and Flow Name, respectively, will that force it to the Chat flow that is associated with the Widget?

<script> window._genesys = { "widgets": { "webchat": { "transport": { "type": "purecloud-v2-sockets", "dataURL": "https://api.mypurecloud.com", "deploymentKey": "", "orgGuid": "", "interactionData": { "routing": { "targetType": "QUEUE", "targetAddress": "Avtex Test Queue", "priority": 2 } }

#Routing(ACD/IVR)

------------------------------
Angelia Harper
Avtex Solutions, LLC
------------------------------

So, you set up the Widget with a flow, like:



------------------------------
George Ganahl GCP (Genesys Cloud), ICCE
Principal Technology Consultant
Genesys
------------------------------

Original Message:
Sent: 05-01-2020 11:55
From: Angelia Harper
Subject: Chat Flow Routing

Yeah, me not doing this piece before is hard. So, I set up the V2 Widget, assigned the call flow there. Went to the Developer Chat, selected the development, and the queue. Copied that code, gave them the Key and the script/code. They then do their addition to their website and this is where we see it is bypassing the flow.

------------------------------
Angelia Harper
Avtex Solutions, LLC

Original Message:
Sent: 05-01-2020 11:46
From: Daniel McLeod
Subject: Chat Flow Routing

Hi Angelia,

A few questions:

Where did you generate the code snippet?
What widget version are you using?
Do the versions match between your org and the customers?
Are you using a deployment? That is where I configure the flow.

Thanks,

------------------------------
Daniel McLeod
Qsect LLC

Original Message:
Sent: 05-01-2020 10:45
From: Angelia Harper
Subject: Chat Flow Routing

I will post here and Developer Forum.

When I use Developer to chat it routes the interaction through the Widget that then follows the Chat flow that I have built out to do schedule evaluations, and other fun stuff. When the customer uses the code from Developer it seems to be bypassing the Chat flow and going directly to the queue. My question is, "targetType" and "targetAddress" below, if they change this to Flow, and Flow Name, respectively, will that force it to the Chat flow that is associated with the Widget?

<script> window._genesys = { "widgets": { "webchat": { "transport": { "type": "purecloud-v2-sockets", "dataURL": "https://api.mypurecloud.com", "deploymentKey": "", "orgGuid": "", "interactionData": { "routing": { "targetType": "QUEUE", "targetAddress": "Avtex Test Queue", "priority": 2 } }

#Routing(ACD/IVR)

------------------------------
Angelia Harper
Avtex Solutions, LLC
------------------------------

Yes, we figured it out! Customer was using the old version of the chat code. All corrected now.

------------------------------
Angelia Harper
Avtex Solutions, LLC
------------------------------

Original Message:
Sent: 05-04-2020 12:07
From: George Ganahl
Subject: Chat Flow Routing

So, you set up the Widget with a flow, like:

Correct?

------------------------------
George Ganahl GCP (Genesys Cloud), ICCE
Principal Technology Consultant
Genesys

Original Message:
Sent: 05-01-2020 11:55
From: Angelia Harper
Subject: Chat Flow Routing

Yeah, me not doing this piece before is hard. So, I set up the V2 Widget, assigned the call flow there. Went to the Developer Chat, selected the development, and the queue. Copied that code, gave them the Key and the script/code. They then do their addition to their website and this is where we see it is bypassing the flow.

------------------------------
Angelia Harper
Avtex Solutions, LLC

Original Message:
Sent: 05-01-2020 11:46
From: Daniel McLeod
Subject: Chat Flow Routing

Hi Angelia,

A few questions:

Where did you generate the code snippet?
What widget version are you using?
Do the versions match between your org and the customers?
Are you using a deployment? That is where I configure the flow.

Thanks,

------------------------------
Daniel McLeod
Qsect LLC

Original Message:
Sent: 05-01-2020 10:45
From: Angelia Harper
Subject: Chat Flow Routing

I will post here and Developer Forum.

When I use Developer to chat it routes the interaction through the Widget that then follows the Chat flow that I have built out to do schedule evaluations, and other fun stuff. When the customer uses the code from Developer it seems to be bypassing the Chat flow and going directly to the queue. My question is, "targetType" and "targetAddress" below, if they change this to Flow, and Flow Name, respectively, will that force it to the Chat flow that is associated with the Widget?

<script> window._genesys = { "widgets": { "webchat": { "transport": { "type": "purecloud-v2-sockets", "dataURL": "https://api.mypurecloud.com", "deploymentKey": "", "orgGuid": "", "interactionData": { "routing": { "targetType": "QUEUE", "targetAddress": "Avtex Test Queue", "priority": 2 } }

#Routing(ACD/IVR)

------------------------------
Angelia Harper
Avtex Solutions, LLC
------------------------------

Glad to hear it! I was just getting time to look at it again :-)

------------------------------
George Ganahl GCP (Genesys Cloud), ICCE
Principal Technology Consultant
Genesys
------------------------------

Original Message:
Sent: 05-04-2020 12:09
From: Angelia Harper
Subject: Chat Flow Routing

Yes, we figured it out! Customer was using the old version of the chat code. All corrected now.

------------------------------
Angelia Harper
Avtex Solutions, LLC

Original Message:
Sent: 05-04-2020 12:07
From: George Ganahl
Subject: Chat Flow Routing

So, you set up the Widget with a flow, like:

Correct?

------------------------------
George Ganahl GCP (Genesys Cloud), ICCE
Principal Technology Consultant
Genesys

Original Message:
Sent: 05-01-2020 11:55
From: Angelia Harper
Subject: Chat Flow Routing

Yeah, me not doing this piece before is hard. So, I set up the V2 Widget, assigned the call flow there. Went to the Developer Chat, selected the development, and the queue. Copied that code, gave them the Key and the script/code. They then do their addition to their website and this is where we see it is bypassing the flow.

------------------------------
Angelia Harper
Avtex Solutions, LLC

Original Message:
Sent: 05-01-2020 11:46
From: Daniel McLeod
Subject: Chat Flow Routing

Hi Angelia,

A few questions:

Where did you generate the code snippet?
What widget version are you using?
Do the versions match between your org and the customers?
Are you using a deployment? That is where I configure the flow.

Thanks,

------------------------------
Daniel McLeod
Qsect LLC

Original Message:
Sent: 05-01-2020 10:45
From: Angelia Harper
Subject: Chat Flow Routing

I will post here and Developer Forum.

When I use Developer to chat it routes the interaction through the Widget that then follows the Chat flow that I have built out to do schedule evaluations, and other fun stuff. When the customer uses the code from Developer it seems to be bypassing the Chat flow and going directly to the queue. My question is, "targetType" and "targetAddress" below, if they change this to Flow, and Flow Name, respectively, will that force it to the Chat flow that is associated with the Widget?

<script> window._genesys = { "widgets": { "webchat": { "transport": { "type": "purecloud-v2-sockets", "dataURL": "https://api.mypurecloud.com", "deploymentKey": "", "orgGuid": "", "interactionData": { "routing": { "targetType": "QUEUE", "targetAddress": "Avtex Test Queue", "priority": 2 } }

#Routing(ACD/IVR)

------------------------------
Angelia Harper
Avtex Solutions, LLC
------------------------------