Allow Responses/Slots to be used in "Present an answer or text response"

Hey @glamb, I’m wondering why you would want to do that? Doesn’t the user already know what they provided? Why would the Copilot need to reiterate it to the user?

@Ajay Merchia 

Essentially this would be a workaround to storing variables to then output to the user once the Path / Query is completed. Following my example above, if we wanted to ask a Question2 with the options Good, OK, Poor relating to their experience on the 3 different OS types from Question1, we’d have to build Question2 three different times on each branch.

I figured it would be easier to explain with a reference diagram (apologies for quality):

Currently we can build out the left solution with 2 questions but if we were to ask 5 questions in total, we’d end up needing many more branches to have unique written response handoffs. This may run into the 30-node limit of Paths. If the right solution were available, we could merge the branches in every question, but retain a unique output depending on what the user entered.

Sorry I think I’m still lost. Why not build the diagram on the right? Can’t your iPaaS accept “Win / macOS/ iOS” and “Good, OK, Poor” and then submit it to the necessary APIs?

Here I’m not demonstrating an API handoff. I’m using a “Present a text response” handoff which would ideally contain “{{QUESTION_TITLE}}” in the text body so that it can be replaced with the user’s choice for that question.

I can certainly use an API handoff instead, receive the HTTP in power automate, build logic to interpret the slots, then return an HTTP back to the bot, and present the user with the same information. It would just be nice to avoid API handoffs entirely if the bot could interpret {{QUESTION_TITLE}} and replace that with the user’s input for that question natively