NewDesk team10 min read
Why this is the scary one
Answering a question badly costs a follow-up. Refunding the wrong invoice costs money and trust, twice. So the powers that touch Stripe, refunding an invoice and cancelling a subscription, are the ones we designed most carefully, and the ones we are asked about most.
Connected by you, bounded by you
A desk connects its own Stripe account under Integrations. From then on a ticket shows what Stripe knows about the customer on it: their plan and the invoices a refund conversation is about. The powers act on that account only, within the limits the desk’s owner set.
The customer agrees first
A refund is not something the assistant does to a customer; it is something the customer asks for. Before a refund or a cancellation runs, the assistant states exactly what it is about to do and waits for the customer to agree in their own words. No agreement, no run. A widget with the confirmation card shows it as a card; one without it is held to the same rule mechanically.
The model cannot invent the inputs
A power whose inputs the model cannot obtain from the conversation is an invitation to make them up. So a refund takes the invoice the desk found under the customer’s email, not an amount the model typed, and the reason is a short line kept for the record. The assistant proposes; the desk checks.
Written on the ticket
Every run is recorded on the ticket: what was asked, what was confirmed, what happened, and the reference from Stripe. Your team reads it in the morning the way they would read a teammate’s note, and the same tools are there for your own assistant over MCP, with the same confirmation before either runs.