Information boundaries
One check looked for internal information that should not appear in a customer reply.
Case study · Google
I led the development of an AI support agent at Google. It investigated technical issues and wrote replies for support specialists to review and send.
01 · The problem
Technical inquiries arrived as email conversations. For each one, a support specialist read the thread, checked the relevant product systems and backing data, consulted technical documentation, and wrote a reply.
As the number of inquiries grew, so did the backlog. Much of the team’s time went into gathering the same kinds of evidence again and again.
02 · The system
The agent gathered the evidence and wrote a response. A support specialist reviewed it before anything went to the customer.
The agent read the full email thread to understand the customer’s issue and its context.
Google ADK routed the inquiry through the workflow and selected the evidence it needed.
Tools looked up the current system status and backing data. The agent did not have to rely on model recall.
The agent used relevant internal and external documentation to write the draft.
The system saved the response for a specialist to review, edit if needed, and send.
03 · The safeguards
Each draft went through a set of validation checks before it reached the support team.
One check looked for internal information that should not appear in a customer reply.
An LLM judge checked the draft again for quality and consistency.
A support specialist made the final decision about what to send.
04 · The result
For more than 70% of technical inquiries, the workflow handled the investigation and produced a reply ready for review. The team cleared its growing backlog and brought customer response time down to one day.
The pilot led to a decision to integrate the agent into Merchant Center Assistant, the AI chat assistant available to Merchant Center users.
A similar problem?
I can help you map the workflow, work out where an agent is useful, and keep the right decisions with your team.
Book an architecture call →