Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

IntentConfirmationSetting

import type { IntentConfirmationSetting } from "https://aws-api.deno.dev/v0.4/services/lexmodelsv2.ts?docs=full";

Provides a prompt for making sure that the user is ready for the intent to be fulfilled.

interface IntentConfirmationSetting {
active?: boolean | null;
confirmationConditional?: ConditionalSpecification | null;
confirmationNextStep?: DialogState | null;
confirmationResponse?: ResponseSpecification | null;
declinationConditional?: ConditionalSpecification | null;
declinationNextStep?: DialogState | null;
declinationResponse?: ResponseSpecification | null;
elicitationCodeHook?: ElicitationCodeHookInvocationSetting | null;
failureConditional?: ConditionalSpecification | null;
failureNextStep?: DialogState | null;
failureResponse?: ResponseSpecification | null;
promptSpecification: PromptSpecification;
}

§Properties

§
active?: boolean | null
[src]

Specifies whether the intent's confirmation is sent to the user. When this field is false, confirmation and declination responses aren't sent. If the active field isn't specified, the default is true.

§

The DialogCodeHookInvocationSetting object associated with intent's confirmation step. The dialog code hook is triggered based on these invocation settings when the confirmation next step or declination next step or failure next step is InvokeDialogCodeHook.

§
confirmationConditional?: ConditionalSpecification | null
[src]

A list of conditional branches to evaluate after the intent is closed.

§
confirmationNextStep?: DialogState | null
[src]

Specifies the next step that the bot executes when the customer confirms the intent.

§
confirmationResponse?: ResponseSpecification | null
[src]
§
declinationConditional?: ConditionalSpecification | null
[src]

A list of conditional branches to evaluate after the intent is declined.

§
declinationNextStep?: DialogState | null
[src]

Specifies the next step that the bot executes when the customer declines the intent.

§
declinationResponse?: ResponseSpecification | null
[src]

When the user answers "no" to the question defined in promptSpecification, Amazon Lex responds with this response to acknowledge that the intent was canceled.

§
elicitationCodeHook?: ElicitationCodeHookInvocationSetting | null
[src]

The DialogCodeHookInvocationSetting used when the code hook is invoked during confirmation prompt retries.

§
failureConditional?: ConditionalSpecification | null
[src]
§
failureNextStep?: DialogState | null
[src]

The next step to take in the conversation if the confirmation step fails.

§
failureResponse?: ResponseSpecification | null
[src]
§
promptSpecification: PromptSpecification
[src]

Prompts the user to confirm the intent. This question should have a yes or no answer.

Amazon Lex uses this prompt to ensure that the user acknowledges that the intent is ready for fulfillment. For example, with the OrderPizza intent, you might want to confirm that the order is correct before placing it. For other intents, such as intents that simply respond to user questions, you might not need to ask the user for confirmation before providing the information.