Plugin to plugin handoff loses context

Hi ​@suyog!

Can you share a screenshot of the desired and incorrect flow? Can you confirm that your Update Address plugin has the Confirmation Policy flag enabled? This flag should ensure that verification of slots are confirmed before executing the action.

Best,

Ryan

Hi ​@suyog - Is there a reason for needing two separate plugins? This is somewhat an anti-pattern, you could have everything in one plugin and have decision policies to control the flow to see if there user wants to update or not

Hi ​@Kevin Mok ,
The requirement was to display all addresses or make an update, both being separate actions with separate triggers. The address update plugin is complex as it is because of different decision policy cases for each country (each country's requirement is different as well). The view addresses plugin also displays all addresses (primary and non-primary) whereas the update is only for a primary address. Before a user does an update, we want their primary address only to be displayed. Another requirement is that most of the time, people only want to view their address without follow-ups (following up through a decision policy every time is not the ideal experience). Hence, we distinguished the two. 

Hi ​@rgeroulo,
Here are some screenshots of what I am talking about - and yes the Confirmation Policy flag is enabled. One thing to note is View my address returns all your addresses (I only have 1 in the system as of right now). Usually people do have multiple addresses. Update my address should be showing your primary address before starting the process.
 

Thank you for the screenshots ​@suyogrithesh!

In this case, the reasoning engine will try to infer values if possible. If only a single address is returned in the view my address turn, then the assistant is not asking for a clarification since there is only 1 possible option in the update address turn.

Does this happen for users were there are multiple addresses? I would be curious if they get a different experience since the assistant will have to disambiguate.

Hi ​@rgeroulo ,
Yes I have tested through multiple users with multiple addresses and the experience is the same each time. I understand that the bot picks up on context and does not display before the update address . Is there any way we could give the bot extra instructions to always display (this is the requirement from the customer)? I was thinking of maybe using the Plugin Response Guidelines?

I still believe you should be doing this in 1 plugin.

You are already providing a CTA to the user at the end saying if you want to update your primary address then say “update my address”. You can do this in one plugin where at the end you have a slot that has a description with the same instructions and then have a decision policy if they want to update or not. If they do then go into the branch where you can update the primary address and if not just exit the plugin