Separate a suggestion from a change.
“That looks good” can mean many things in a conversation. It is a weak foundation for changing a booking or placing an order. A clear confirmation gives a person a chance to review the result before it affects their account.
Show the action where the discussion happens, with language that names the outcome: add the plan, save the basket, or confirm the booking.
Put the important details beside the button.
A confirmation should carry the information someone needs to decide. For a food order, that might mean the items, destination, delivery window, and final total. The exact details depend on the action.
Do not make the person reconstruct those details from six earlier messages. Bring the proposed result together, and give them a way to change it.
Show where the result went.
After confirmation, the conversation should make the outcome clear. The saved plan belongs in the normal plan screen; an order belongs in the normal order history.
A useful action joins the product’s existing experience. The confirmation is the connection between understanding a request and doing something with it.
Thoughts on building personal agents into the products people already use.
More about why we’re building shardr