Dialogflow CX: the intents do not appear as an output in Architect

[Hafid_Bourich]

Hello,

I am unable to see the outcome paths for the handover in the architect. With the ES integration you did this by setting an intent as the end of the conversation, then you could choose this in your architect flow. With CX you can put a transition to the end of the session, but that doesn't seem to have the same effect.
Do you know how to do this?

Regards,
Hafid

[Hafid_Bourich]

Can anyone help out with this?

[brad.wehmeier]

Hello Hafid,

Dialogflow CX no longer uses intents as the end of the virtual agent's session. As you observed, it uses the transition to the end of the session. In order to control how the conversation proceeds in Architect, the CX Agent will need to pass that data back to Architect. Then the Call Dialogflow CX action will capture that data into a variable, then branch based on the value of that variable.

First the Dialogflow CX Agent will need to be configured to output some data. This can either be by setting a Session Variable in CX or by adding a Live Agent Handoff Metadata fulfillment.

Within Architect, the Call Dialogflow CX Bot action provides the configuration to map the values from Output Session Variable or a Live Agent Handoff Metadata into an Architect flow variable.

Once the value is part of an Architect variable, then the other Architect actions like the Switch action can be used to branch the flow.

I hope that helps.

Thanks,
Brad

[Hafid_Bourich]

Thanks a lot Brad!

One more question. Is there a difference between using the session out variables or the Live Agent Handoff Metadata output?

Regards,
Hafid