The reply, drafted with the real number in it.

/How the turn went

The figure is looked up, the draft is held, and the scope is wider than the habit.

1. 01

   The number comes from billing, not from memory

   The customer is found by the address on the mail thread, and the invoice is read from the billing connection. A figure recalled rather than fetched is the one thing a reply like this cannot afford to get wrong, and the status line shows where this one came from.

2. 02

   It reads what the split would actually mean

   One issued invoice cannot be edited into two, so the draft says credit note and reissue rather than promising an edit. The reply is only as useful as the thing it is willing to be specific about.

3. 03

   A draft is still a write

   Creating the draft is held at a card that shows the text in full. Nothing lands in the asker’s mailbox until they press it, and nothing leaves the mailbox at all.

4. 04

   The scope Google does not offer

   Gmail has no draft-only permission: the scope that lets anything write a draft is the same scope that lets it send. So the consent screen a person sees when they connect their account says “send mail as you”, and the checkbox in the console says so too, rather than quietly claiming a narrower grant. The bot only ever drafts — but that is a property of the product, which the console’s audit trail lets you check, not of the permission.