Skip to main content
AGO
CUSTOMER HARNESS

Own your customer harness without building its infrastructure

A customer harness is everything around the AI model that talks to your customers: what it knows about each account, what it is allowed to do, where it answers, when it hands over to your team and how you check it. With AGO, your team decides all of it and the platform runs it.

WHAT IT IS

A customer harness turns a model into an agent your customers can rely on

The term comes from coding agents, where the harness is the software around the model. Facing customers, it has seven parts.

Customer context

The agent reads this customer’s account through your APIs and MCP servers, not only your documentation.

Actions

What it may do in your systems and inside your product: update a record, open the right screen, pass a lead to sales.

Knowledge

Your help center, documentation and files, kept in sync with what you publish.

Channels

Your product, your website, email, WhatsApp, Messenger and voice, in one tone of voice.

Decision rules

For each type of decision: the agent alone, the agent with approval, or a person.

Handoff

The person who takes over receives the conversation and its context, in AGO Helpdesk or in yours.

Tests and quality

Your scenarios replayed and attacks simulated before release, then a quality score on conversations.

WHY AGO

Why build it with AGO

Built alone, the harness becomes infrastructure your engineers maintain. Inside a helpdesk, it stops where the vendor’s connectors stop.

You keep the experience, AGO runs the infrastructure

Your team decides what the agent says, what it does and where it appears. Connectors, knowledge sync, channels, tests and analytics are AGO’s to build and maintain.

Any system your team runs

Agents read and act through your APIs and MCP servers: billing, back office, internal tools. When a connector is missing, our engineers build it with you.

Inside your own product

The agent knows the page your customer is on, opens the right screen and prepares the change. It runs in production for onboarding inside the Brevo interface.

Keep your helpdesk or use AGO’s

The harness does not depend on where your tickets live. Escalations reach Zendesk, Intercom, Help Scout or AGO Helpdesk with the context attached.

AI agents are our core business

AGO has built AI agents since its first day. The whole team works on what makes an agent good in production: a quality score on conversations, replays of your scenarios and simulated attacks before release.

Built with an AI Engineer, then run by your team

An AGO engineer builds the first agent with you. Your business and technical teams then run and extend it on their own.

WHO DOES WHAT

Your team writes the rules, AGO runs what they run on

What makes the agent yours stays with your team. What only has to work is AGO’s job.

PartYour team decidesAGO provides
Customer contextWhich data the agent may read, for which customerAPI and MCP connections, and engineers to build a missing connector
ActionsWhich actions the agent may takeTools in your systems and SDK functions inside your product
KnowledgeWhich sources are authoritativeImport, sync and checks that the knowledge covers your reference questions
ChannelsWhere your customers meet the agentProduct SDK, website, email, WhatsApp, Messenger and voice
Decision rulesWho takes each type of decisionThe agent acting alone, waiting for approval or handing over, as you set it
HandoffWhen a person takes over, and whoRouting to your helpdesk or AGO Helpdesk, with the conversation attached
QualityThe scenarios that matter and the bar for releaseReplays, simulated attacks, quality scores and analytics
CUSTOMER RESULT / SILAE

Silae replaced its helpdesk bot with an AGO agent and nearly doubled its deflection

Silae
75 to 85%of conversations deflected by AGOUp from around 40% with the previous Zendesk bot
“Some of my favorite parts are things we never even asked for. The CX evaluation system scores the quality of every conversation, the dashboards keep getting sharper, and the MCP server and APIs let us connect the agent to the wider Silae ecosystem.”
Xavier Kerouanton, VP Partner Experience, Silae
HOW IT IS BUILT

Five meetings to a harness in production

Built with your team, then reviewed on real conversations until the agreed goal is reached.

1

Scoping workshop

Two hours to set the priority use cases, the response standards and the automation goal.

2

Your systems

With your technical contact, we go through your APIs and arrange the access the agent needs.

3

Your knowledge

We identify the content that matters and who keeps it up to date as your product changes.

4

Everyone involved

One meeting to explain how the agent works, who decides what and how handoff happens.

5

The first weeks

Regular reviews of conversations and improvements until the agreed goal is reached.

FAQ

Questions about customer harnesses

What the term means and what building one with AGO involves.

What is a customer harness?+

The software around an AI model that lets it work with your customers: their account data, the actions it may take, the knowledge it answers from, the channels it answers on, the rules on who decides, the handoff to your team and the tests that check it.

How is it different from an agent harness?+

An agent harness is the general runtime around a model: tools, memory, guardrails. A customer harness adds what talking to customers requires: knowing who the customer is, reading their account, answering on their channel and handing over to a person with the context.

Where does the term come from?+

From coding agents, where the harness is everything around the model. In October 2026 Microsoft announced a customer conversation harness in Copilot Studio, and in November 2026 HubSpot described its next chapter as building a customer relationship harness.

Why not build our own harness?+

You can. Connecting a model to your documentation is quick. Keeping it right through months of product changes takes connectors, knowledge sync, tests, analytics and a handoff to your team, and that is the work AGO takes off your engineers. Your own interface can still sit on top: the SDK lets you build your own chat in React.

Do we have to change helpdesk?+

No. Escalations can go to the helpdesk you already use, such as Zendesk, Intercom or Help Scout, or to AGO Helpdesk.

Which decisions can the agent take on its own?+

The ones you give it. For each type of decision you choose: the agent alone, the agent with approval, or a person.

What does AGO cost?+

The standard rate is €0.50 per conversation with a €500 monthly minimum, with unlimited seats and AI agents. Billing does not depend on resolution. Enterprise pricing is quoted separately.

Plan your implementation

  • AGO Agents

    Agents that answer and act inside your product and on your channels.

  • The SDK

    Routes, page state and the functions your agent may call in your app.

  • Pricing

    Conversation pricing, monthly minimum and illustrative calculations.

GET STARTED

Start with support, extend to the whole customer journey

In a first 30 minute conversation, we scope your priority requests, what needs connecting and how the result will be measured.