Secure Client Confirmation & Confirmed Action
Secure Client Confirmation & Confirmed Actions
Ask Clio supports Secure Client Confirmation for tools that take action on behalf of a client.
When Client Confirmation is enabled, Ask Clio prepares the proposed action, shows the client a confirmation modal with the inputs that will be sent, and only executes the API call after the client confirms.
This allows firms to safely support action-oriented workflows while keeping the final approval step with the client.
Common use cases
Secure Client Confirmation can be used for workflows such as:
Deposits and withdrawals
Trading actions
Account profile or address changes
Operational account updates
KYC or onboarding document collection
Banking workflows that require client-provided documentation
Other firm-defined actions that should require explicit client approval
How it works
The firm creates or edits a tool from the Integrations tab.
The firm enables Require client confirmation before executing.
When the tool is triggered in chat, Ask Clio creates a draft of the action.
The client sees a confirmation modal in the SDK.
The client reviews the inputs that will be submitted.
After the client confirms, Ask Clio sends the request directly to the configured API.
Why this matters
For sensitive workflows, the model should not directly execute an action without client approval. Client Confirmation creates a secure handoff between the conversational experience and the API execution step.
The model can help collect the required information, but the API call is only executed after the client confirms the final payload.
File uploads and Client Confirmation
Tools that use the file Data Input type must have Client Confirmation enabled.
When a client uploads a file in the confirmation modal, the uploaded file is passed directly into the tool execution flow rather than being sent through the model.
Last updated