---
id: KB-MA-019
url: https://app.codecontract.io/help/marta/when-an-answer-leaves-the-company
idioma: en
categoria: marta
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-MA-004, KB-MA-015, KB-MA-017]
citadoPor: [KB-MA-020]
---

# When an answer leaves the company

_Asking internally and pasting the answer into an email to a client are two very different things._

**Responde a:** 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

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.

> [!WARNING]
> 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

**En corto**

- If it is going into proceedings or a claim: that is drafted by whoever answers for it.
- If the client is waiting on a position rather than a figure.
- And if you could not yourself defend where each number comes from.

> [!NOTE]
> 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.

## Ejemplos

**A company forwards a status summary to a client without checking it.**

- Checks the figures and whether what was submitted had been reviewed

→ The client gets a status that holds up, not a confirmation of something still under review.

**An answer is copied verbatim to a client.**

- Reviews the text before sending

→ What goes out carries your judgement.

**The answer includes another client's data.**

- Checks what it contains before forwarding

→ Information does not cross between clients.

**Something is asserted to a third party unchecked.**

- Cross-checks against the original document

→ What is asserted holds up.

**The tone does not fit the relationship.**

- Adjusts the text before sending

→ The message sounds like you.

**There is no record of what was sent.**

- Records the send in the file

→ What was communicated leaves a trail.