---
id: AS-2
title: Confirmation cards
group: Working with the assistant
summary: Why the assistant always stops and asks before anything that can't be undone, and what your tap does
keywords: [confirm, confirmation, needs your tap, not yet, submit, approve, irreversible, safety]
---

Before anything that cannot be undone, the assistant stops at a confirmation card and waits for you. Submitting a sale, approving or countering an offer, closing a delivery, taking a payment: each one waits for your tap, and only your tap sends it.

## What you see

The card is marked **Needs your tap**. It names the step, such as *Submit this sale?*, and shows the real details, fetched fresh from your organization's system at that moment rather than taken from the conversation: the customer, the items, the total, what has been paid, and any balance still due, in amber.

Two buttons:

- **The action itself**, named for what it does: **Submit sale**, **Counter**, **Confirm**. Tap it and the step goes through.
- **Not yet**. Nothing is sent. The card says *Not yet — nothing was sent*, and the assistant is told you held back.

Once you tap, the card shows **Confirmed**. A card that waited too long shows **Expired**; ask again if you still want it.

## Why it always asks

The assistant can be wrong: it can misread a name, pick the wrong item or misunderstand an amount. So it prepares, and you decide. The card shows what the system will actually do, not what the conversation suggests.

No keyboard shortcut confirms a card. It is always a deliberate click or tap on the button.

## And behind the card

Your organization's systems keep their own rules, whatever happens on the device. A price below the floor, a refund over a limit, a payment on someone else's account: the system refuses them even if they are confirmed. The card is there so you see what you are agreeing to; the systems are what keep the business safe.

On this device (free), you decide which tools need a card. See Tool rules (FR-4).
