Forward / Delegate from Connections.Response to IntentRequest

Question

question

NewUser-bf5caa60-070a-4423-8e05-09c46aa6d386 asked · Jan 09, 2019 at 11:25 PM

Forward / Delegate from Connections.Response to IntentRequest

I don't know why it's not possible to switch between intents easily.

I want to integrate Amazon Pay in my Alexa Skill with the ASK SDK v2

So I have this check for the final setup of finished connection setup.
request.type === 'Connections.Response' && request.name === 'Setup'

But how to get back to my original intent?
So imagine I have a intent where the user want to buy something. "OrderIntent".
I return the payment setup "Connections.SendRequest" directive.
Then I get back the "Connections.Response" but how to go back to my "OrderIntent"?

I mean the request is closed and the session is done. So I can't work with SessionAttributes and must use PersistentAttributes. - ok thats not a problem.

But now I stuck on how to get back to my intent. Without that the user says again "Yes please order now".

Any ideas?

In the examples https://developer.amazon.com/de/docs/custom-skills/dialog-interface-reference.html#confirmslot they wrote:

Note that you cannot change intents when returning a Dialog directive, so the intent name and set of slots must match the intent sent to your skill.

So this is another topic. Why I can send an updated intent with different name as (Dialog) directive when I'm not allowed to change the intent name!?

Thanks in Advance for answers. I am desperate.

how-to intents session dialog directive redirect

1 · Show 1

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

NewUser-0c4117b2-b119-40b4-b4e3-99710289e52d · Jan 10, 2019 at 05:11 PM

The fact that the skill can't redirect intents makes real conversation practically impossible. The examples that the documentation provides about how to do this rely on really contrived responses from the user. Alexa: "Do you want a large dog or a small dog?" User: "How big is a large dog?" (new intent) Alexa: "Large is more than 50 pounds". The user can now only get back into the original intent by saying "I want a medium dog", rather than just "medium". Not to put too fine a point on it, but that's just stupid. This needs to be fixed. A skill should be able to switch intents itself.

0 · Share ·

Answer 1 · 2019-01-15T18:14:44Z

barry@amazon answered · Jan 15, 2019 at 06:14 PM

Hello and thank you for your message.

One way to do what you are describing is to instead of relying on intents, you create functions that take the handlerInput as argument. Then the function can filter from which intent it was called and get executed based on that.

Regards,
Barry

0 · Share

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Forward / Delegate from Connections.Response to IntentRequest

question details

Related Questions