Marta
When an answer leaves the company
Asking internally and pasting the answer into an email to a client are two very different things.
You ask how many of a client's files are still open, a flawless summary appears, and the natural move is to copy it and send it. At that moment something worth keeping in mind happens: the answer stops being an internal query and becomes a statement of yours.
What changes when it crosses the door
| Inside | Outside |
|---|---|
| It helps you get your bearings | It reads as a commitment |
| An error is fixed and forgotten | An error has to be corrected in front of the client |
| It is a summary of what is stored | It looks like a company statement |
| Nobody checks the figures twice | Whoever receives it keeps the figure |
Important
The part that cannot be delegated: **what you send is yours from the moment you hit send, and it carries no mark of how it was drafted**. Nobody on the other side knows — or needs to know — whether a person wrote it or it came from a query. So a figure about to leave the company gets checked against its record first: not because the answer usually fails, but because you answer for it, and a misquoted number does not cost the same outside as it does inside.
What to check before sending
- 1
Figures and dates, in their place
They are what the other side keeps, and will quote later.
- 2
That nothing from another client slipped in
A summary can draw on several places at once.
- 3
That it does not promise what you do not want to promise
A friendly text can commit to dates on its own.
- 4
And the tone, which reads differently outside
What sounds direct internally can sound curt outside.
Watch out
One case slips through easily and is not obvious: **a summary does not always separate what is confirmed from what was pending**. If a file holds a document that was submitted but not reviewed, a summary may treat it as good without the caveat — and that caveat is exactly what matters when the reader is a client awaiting confirmation. Before sending a status, check whether what you call «there» is what is settled or merely what arrived.
When not to forward anything
Worth knowing
This is not distrust of the tool: it is the same rule you would apply to a draft handed to you by a colleague. The draft is welcome, and you sign it after reading it.
›Can I say the AI drafted it?
You can, and it does not change who answers for what it says.
›What about an internal summary?
No ceremony needed there: that is exactly what it is for.
›Is it worth asking for sources?
Yes, and checking two: that is what makes reviewing quick.
A real case
The situation
A company forwards a status summary to a client without checking it.
What you do
- Checks the figures and whether what was submitted had been reviewed
What you get
The client gets a status that holds up, not a confirmation of something still under review.
The situation
An answer is copied verbatim to a client.
What you do
- Reviews the text before sending
What you get
What goes out carries your judgement.
The situation
The answer includes another client's data.
What you do
- Checks what it contains before forwarding
What you get
Information does not cross between clients.
The situation
Something is asserted to a third party unchecked.
What you do
- Cross-checks against the original document
What you get
What is asserted holds up.
The situation
The tone does not fit the relationship.
What you do
- Adjusts the text before sending
What you get
The message sounds like you.
The situation
There is no record of what was sent.
What you do
- Records the send in the file
What you get
What was communicated leaves a trail.
This article answers
- can I send a client what the AI answers
- using an assistant answer in a report
- who is liable for what the AI writes
- quoting figures the assistant gave me