Article

Should an AI assistant send email on its own?

AI must hand a customer question to a person when the customer requests one, knowledge is missing or authority is lacking. Arrange handoff and review before sending.

By Piet Baudoin · September 2026

AI must hand a customer question to a person if the customer asks for a staff member, the answer cannot be supported, authority is lacking or a decision with consequences is needed. Have the AI agent prepare the question with the known details and the reason for handing it over to the responsible colleague. Give the customer a route to that colleague. A conversation that gets stuck must not return to the same answer.

Email adds another requirement: a reviewed answer may only be sent according to the sending agreement. A question about missing knowledge, a decision about money and approval of a message are different points where someone must be able to intervene.

When must AI hand the question over?

Hand it over when information is missing or contradictory. Think of a customer who says something has been paid while the known records do not confirm it, or a question about an agreement made only verbally. Have the AI agent identify what is missing. Do not let it finish the answer with an assumption.

Also hand it over when the question requires an exception or decision: a price change, compensation, a different delivery date, a formal complaint or permission to share data. A standard answer is not enough, even when the wording sounds familiar.

If the customer wants to speak to a staff member, assign one. If the same question keeps coming back unresolved, have someone review the conversation instead of giving the same answer again. These examples are a practical business agreement. They are not a legal list or a measured error rate.

What do you do if the customer wants to speak to a staff member?

Make the route to a staff member visible and usable. Ask only what is needed to find the right colleague. Do not make extra bot questions a condition for reaching that colleague. If no one can respond immediately, offer a callback request or a message to the responsible person. Say what the customer can expect without promising a time frame that has not been agreed. Also offer a suitable route if the customer cannot use the chat menu.

The Reddit thread discusses stuck menus, frustration and handoff with context. These are experiences and opinions, not research into an optimal waiting time. Reddit r/CustomerSuccess, read 2026-10-03.

Why is a human-sounding answer not proof?

ChatGPT is an application of AI. AI is the broader umbrella term. A pleasantly worded answer does not show that the underlying customer agreement is correct. Ask for the source and check that it applies to this customer and this question. An old agreement or an agreeable answer must not replace contradictory information in the client file.

The top results discuss incorrect answers, agreeableness and the difference between sounding human and being human. For customer contact, this leads to a practical choice: tell the customer when they are speaking with AI and how to reach a staff member. The European Commission also describes transparency about chatbot use. European Commission, read 2026-10-03. A warm tone is no basis for approving the content without review.

What data do you share for a customer question?

Provide only the data needed to handle the question, through an environment your organization permits. Do not paste passwords, login codes, complete customer lists or unnecessary client file information into a separate chat. Ask in advance who can see the data, what it is used for and what agreements your organization has about it.

The same limit applies to handoff: the responsible colleague must be able to check the relevant agreement but does not automatically need the entire client file. OWASP recommends limiting access to what the task needs. OWASP, read 2026-10-03. This is a business practice, not a claim that all AI services have the same data agreements.

Does the question, the draft or the sending need a person?

For a missing detail, the AI agent asks for an addition. The staff member checks the detail and decides which source takes precedence. The client file remains visibly open.

For a decision, the AI agent presents the facts and the open choice. The authorized staff member decides, for example, whether an exception to an agreement can be made. Only then can you draft a suitable answer.

For sending, the staff member checks that the draft matches that decision, is addressed to the right recipient and contains the right attachment. Approving an email does not replace a substantive decision that is still missing.

What must go with the question?

Give the recipient the original question, relevant client file details, earlier contact and the reason for the handoff. Clearly state what is known, which sources contradict each other and which decision or detail is needed.

A handoff such as “I do not know” makes the investigation start again. A useful handoff says, for example: “The customer asks for a different delivery date. The known agreement is with the proposal, but no new schedule has been confirmed. The responsible colleague must assess the date.” This is a workflow example, not a real customer case.

The staff member must be able to open the original source. A confidently written summary does not replace the agreement on which they base the decision.

How do you make sure someone actually takes over the question?

Assign an owner who can answer the question or is authorized to decide. Keep the open work visible until someone has picked it up. Agree on what the customer hears in the meantime and where the response is recorded.

An internal draft could be: “I am referring your question about [subject] to [responsible person]. We will get back to you once [required review] is complete.” Do not use a promised response time that no one has agreed to or can meet.

If the owner cannot be reached, the staff member must be able to assign another authorized colleague. Do not automatically return the same question to the AI agent. That does not resolve the missing decision.

Record when the customer asked for a staff member, when someone picked up the work and whether the question was resolved. Also check whether the same question later returns by email or phone. Counting fewer chats alone does not show whether the customer was helped. Moving to another channel is a reason to review the route. Do not set a general performance standard here without your own measurement.

Why is an instruction to “ask for permission first” not enough?

An agreement in the instructions helps with the desired behavior. It does not prove that an action without approval is impossible. The check must keep working when the work restarts, information changes or a received message tries to steer the AI agent in another direction.

Anthropic warns in its own guide that content on pages or in images can conflict with the instructions. It recommends human confirmation for actions with meaningful consequences. That is a warning about the maker’s product, not a measurement of how many emails go wrong. Anthropic, read 2026-10-03.

Ask for a demonstration: have a draft prepared, reject it and see whether sending actually waits. Also check what happens after an interruption and who can change the permission.

What does the Replit incident show?

The Register describes an incident in which a Replit AI agent removed production data while the work was supposed to remain on hold under the agreement. This concerned software work, not an email agent.

The incident does not prove how often this happens. It does show why you need to check whether an agreement holds when the AI agent acts incorrectly. For your mailbox, test the same question on your own action: can a rejected draft still be sent? The Register, read 2026-10-03.

What do the security sources say about approval?

OWASP describes the risk that an AI agent can do more or gets more authority than the task requires. The organization recommends human approval before high-impact actions and a check on what someone is allowed to do.

The email example is specific: an AI agent that needs to summarize messages does not need permission to send them. An incoming message must not become a reason to send information to a stranger. A useful workflow only grants access to the work needed, lets the staff member make the sending decision and makes actions traceable afterward. OWASP, read 2026-10-03.

Who is responsible for the answer?

Have the organization assess the answer as if it were given in its own name. An incorrect commitment does not disappear because an AI agent worded it.

In the Canadian case Moffatt v. Air Canada, the tribunal held the airline responsible for misleading information from its website chatbot. This follows from the reread discussion by McCarthy Tétrault. The ruling itself could not be opened here. It is not a Dutch ruling about email or a general conclusion that every case has the same legal outcome. McCarthy Tétrault, read 2026-10-03.

The European Commission describes human oversight as part of the requirements for high-risk AI. That is not a general rule that every business AI agent must legally have an approval button for email. Make the sending and handoff agreement explicit, regardless of which legal category applies to the application. European Commission, read 2026-10-03.

What changes if the AI agent also prepares other work?

For an invoice, payment link, payroll processing or personnel decision, the question shifts from wording to authority: who may determine this, who must check it and what can still be corrected? Approving an email is not approving a payment or a change to a personnel file.

Record for each task what the AI agent may prepare and where a person decides. Test the tasks separately. A vendor showing a check for email does not prove that the same check applies to amounts or client file changes.

What do you ask a vendor?

Question What you want to see
When does a question go to a person? Specific situations and the responsible staff member
What does that staff member see? The original question, reason, sources and open decision
Can a rejected draft still go out? A demonstration in which the action actually waits
Who can change the sending agreement? The responsible person and a visible change
What happens after an interruption? Open work and earlier reviews can be found
Can the staff member stop or correct it? Rejecting, changing and pausing before an action
What is established afterward? Who decided, which version was used and what was done

Ask further when a vendor only says the AI agent has instructions to be careful. A demonstrated action is more useful than a general promise of control.

How does this work at Bombos?

Bombos does not send email itself. It is the memory layer under the AI your team already uses: one plugin for Claude, Claude Code, ChatGPT, Copilot, Grok, Codex, Cursor and your own agents. It gives that AI one shared memory with the team’s knowledge, rules it learns from your corrections and what already sits in email, documents and the software you use. That way every coworker’s AI knows which agreements apply before it writes a draft, and every draft shows what it rests on.

Whether a message waits for approval is set in the AI or agent that sends it. Discuss there in advance which work could proceed without prior approval and who will oversee it. A changed sending agreement does not make missing knowledge or an unauthorized commitment valid.

It starts with a task such as the shared inbox or following up on quotes. Bombos runs in the cloud or standalone on your own server. One person can try the plugin first for their own agents; for a team, the pilot costs €3,000 €2,000 for three months, then €1,000 per month, excluding VAT. Book your half hour.

What remains human work?

Approval takes attention. If you approve a draft without reading it, you have not checked that it is correct. Look at the recipient, the requested decision, the commitment and the underlying source. A log helps you trace what happened. It does not repair an incorrect answer that has already been sent.

The AI agent does not know an unrecorded verbal agreement. Record it before you want it considered in a later proposal. Uncertainty calls for a question to the right colleague, not a more convincingly worded guess.

AI can do the groundwork for a customer question. The division of tasks must keep showing who decides an exception, may make a commitment and takes over contact. That answers the business question of which tasks stay with people. It is not a prediction that AI can replace humans as a whole.

Further reading and sources

Also read what Claude can do on its own for a small business, responsibility for mistakes and the cost of AI for administration.

The source links appear next to the claims they support. They were read on 2026-10-03. Maker guidance, security advice, a news incident and a legal discussion are different kinds of evidence. None provides a measured error rate or time saving for Bombos here.

The first half hour · free

What does your AI forget?

  1. 01You tell us which AI you use and where it keeps starting over.
  2. 02We show what a shared memory changes there, on your own examples.
  3. 03You keep the plan, with or without Bombos.
Piet Baudoin
Piet BaudoinYou talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe
We reply the same working day.