Direct answer
"Sent," it says. Here is how you prove it, and what it said.
Somewhere there is a client who never got the quote, a supplier who never got the change of terms, and an agent reporting that both emails were sent. The agent's word settles nothing. The record of the send step does: what ran, who it went to, the exact contents, and the result the mail service handed back, all saved at the moment of sending.
Updated October 17, 2026.
Three different claims hide inside "I sent it"
Drafted. The message exists somewhere: in a chat, a drafts folder, a plan the agent described. Nothing has left the building. Sent. A send call actually ran, a mail or messaging service accepted the message, and it handed back a result. Read. The recipient opened it. Agents blur all three into one confident sentence, and the sentence is worth nothing until you separate them. This page is about the middle claim, the one that can actually be proven: sent, with the contents fixed.
What settles it: the send step has its own record
When a send runs through a recording connection, the call is written down as it happens, the same as any other step. The record of a send step carries the fields a reviewer needs: the tool that ran, the recipient it was addressed to, the subject and the body as sent, the result the service returned (for email, that includes the provider message id), and the time the step was saved. Anyone can re-verify that record later, which means the contents can be checked character by character against what was saved at send time. If the agent later paraphrases its own email differently, the saved body wins, because the saved body is the one that cannot be quietly rewritten.
Compare the weaker sources. A sent folder shows a message left the account, which is real evidence, but it lives where the account holder can edit or delete it, and it says nothing about the steps around the send. The agent's chat claim shows nothing at all: it is the claim, not the evidence.
The worked shape of the proof
The public handover records on this hub show the mechanism on ordinary client work: a job gathered into one page, every step listed with the time it was saved, each step tied to its receipt. Read one of those step lists and find any step: that is exactly the shape of a send step in a longer job. The record for the job at zambo.dev/handover/45434a17 was checked step by step by its client and accepted, four of four. A send recorded the same way carries its recipient and its returned message id in the same list, checkable by the same recompute.
What the record cannot prove: the reading
A send record proves the call ran and fixes what was sent: the recipient, the contents, and the result the service returned, unchanged since the moment it was saved. It does not prove the recipient opened the message, read it, or acted on it, and it does not prove who produced the words. Be suspicious of any tool that sells read proof for ordinary email. Sent is a fact a record can carry. Attention is not.
Put a gate before the next send
Proof after the fact is half the fix. The other half is a gate before it: high-stakes sends wait for a person's approval, and that approval is recorded against the job the same way the send is. Then the pair answers both questions a dispute ever asks: what exactly went out, and who said it could go. The sign-off page in the Related list works through the gate in detail.
Frequently asked questions
How do I prove my agent actually sent that email, and what it said?
Look for the record of the send step, not the agent's summary of it. When a send runs through Zambo, the call writes a verifiable receipt as it runs, and that record holds the recipient, the subject, the body as sent, the result the service returned (including the provider message id for email), and the time the step was saved. Re-verifying the receipt recomputes it against the record as saved, so the contents you check are the contents that went out. A sent folder entry supports the claim; the agent's sentence in chat does not.
My AI sent an email for me. How do I keep proof of what was sent?
Keep the send step's receipt, not a screenshot of the chat. The fields that matter are the tool that ran, the recipient, the subject and body as sent, the saved result with the provider message id, and the time it was saved. Keep them where the record stays checkable: the receipt can be re-verified later, by you or by anyone you hand it to. And for sends that matter, put an approval gate in front of them, so the proof set includes who approved the send before it ran.
Can the record prove the recipient read my email?
No, and that limit is deliberate. The record proves the send: the call ran, the service accepted the message, and the contents are fixed as saved. It cannot show the inside of the recipient's attention. An unopened email is still a sent email, and the record keeps those two facts separate, which is exactly what you want when the other side claims nothing ever arrived.
My agent says it sent the email, but there is nothing in my sent folder. What now?
Treat the claim as unproven and work the boring causes first: a different sending account, a connected app sending under its own identity, a draft saved instead of sent, or a send that failed after the claim was written. If the send ran through a recording connection, pull the job's step list: a real send is a step with a saved result, and a failed or missing step shows there too. If there is no record and no sent copy anywhere, the honest conclusion is that you cannot prove the send happened, and the fix is recording and a sign-off gate on the next one.
How do I keep an agent from sending mail I never approved?
Put the send behind a gate: the agent prepares the message, a person approves that specific message, and only then does the send run, with the approval recorded against the job. The record then proves both halves, what went out and who allowed it. For $0.99 the Day Pass covers 24 hours of recorded, gated work, no subscription; ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders.
Your AI said "done." For $0.99, prove it: https://zambo.dev/day-pass/