Let your homepage answer from your own content
Visitors type what they came for. An AGO agent answers from your pages, articles and offers, checks your systems for live information, acts when you allow it and hands the visitor to your sales team when they are ready. Your team updates the site by asking an agent, not by editing pages one at a time.

Visitors get the answer and the page that goes with it
Menus make visitors guess where you filed the answer. The agent looks it up for them, in your content.
Your definition
A visitor types a term you use. The agent gives your definition of it, the one your pages use.
Its sources
Each answer cites the pages it comes from, so the visitor can check it and read further.
Your articles and offers
The answer links to what you wrote on the subject and to the offer that matches it.
A lead your sales team can call
When the visitor is ready, the agent collects what sales needs and passes the lead on with the conversation attached.
A rule for what you do not cover
You decide what the agent says when your content has no answer: say so, and offer to put the visitor in touch with your team.
The agent reads your systems and acts, not only your pages
Your content answers the general question. The next one is often about now: a price, a slot, a stock level.
It opens the right page
When the visitor wants to see it, the agent takes them to the page, on the site they are already on.
It fetches live information
During the conversation it calls your systems for what changes by the hour: prices, availability, stock, delivery dates, an order status.
It acts
It books the demo in your sales team’s calendar, registers the visitor for an event, prepares a quote or opens a trial account.
You decide what it may do alone
For each type of action you choose: the agent alone, the agent with approval, or a person.
One agent between your site and your systems, and the harness that keeps it right
The page sends the question and its context. AGO searches your knowledge, calls the tools the question needs, applies your decision rules and hands over when it should.
pageContextthe page the visitor is onnavigate()opens the page that answersfunctionsactions inside the pagewebmcpthe same tools for browser agents
- Unanswered question
- Text proposed by AGO
- Reviewed by your team
- Published in your CMS
- Synced back
- visitor
“Is the X200 in stock, and can it reach Lyon before Friday?” - context
pageContext/products, en - knowledge
search("X200")3 sources: product sheet, delivery guide, offer - tool
get_stock(sku: "X200")14 units - tool
estimate_delivery(sku: "X200", city: "Lyon")Thursday - answer
“Yes, 14 in stock, delivered Thursday.” [1] [2] - navigate
navigate("/products/x200")page opened - action
create_quote(sku: "X200", qty: 3)rule: approval, waits for sales - handoff
leadto the CRM, conversation attached
The knowledge base comes before the conversation
Without one, an agent answers with what its model read on the web. With one, it answers with what you published.

Any CMS, and your other sources
Connect any CMS (WordPress, Webflow, Contentful, Strapi or your own), along with Notion, Confluence and your documentation. Your team keeps writing where it writes today, and AGO keeps the knowledge base in sync.
One definition for every answer
A term is defined once. Two visitors asking the same thing get the same answer, whichever words they use.
Gaps your team can see
AGO lists the questions your content does not answer and proposes the missing text. Your team accepts it, edits it or rejects it.
What visitors come for
Topics show what visitors ask, in their own words, which a page view count does not tell you.
Your team updates the site by asking an agent
A page change becomes a request in plain words. Your current site can also stay where it is.

Ask for the change
Your team asks Claude or Codex for it. AGO builds the change and publishes it in about a minute.
Check it before it goes live
A change can wait as a private preview, opened only with its link, until someone publishes it.
Put back an earlier version
AGO keeps recent versions, so a page that went wrong can be put back as it was.
Found by search engines and AI assistants
The sitemap, robots.txt and llms.txt are generated with every change, and each build lists the pages missing a title or a description.
Or keep the site you have
The conversation fits into any site, inside your own design. Moving your pages to AGO is a separate decision.
Start with the knowledge, then open the conversation
The redesign can wait. The quality of the answers depends on the content behind them.
Connect your CMS and your systems
We connect your CMS, your other sources and the systems the agent will read or act in, and agree with you which sources are authoritative.
Test the questions that matter
Your team lists what visitors ask. AGO checks that the knowledge answers it before anyone outside sees the agent.
Open the conversation on your homepage
On your current site, in your design, with the handoff to sales you choose.
Read what visitors ask
Unanswered questions become content to write, and the answers improve as the knowledge does.
Move the pages when it is worth it
Once the knowledge holds, your pages can move to AGO Sites and be edited by asking.
We run useago.com this way
What we offer you, we tried on our own site first.
A question field on the first screen
Visitors ask the AGO agent from the homepage. It answers from what AGO has published and opens the page that goes with the answer.
A contact request inside the conversation
When a visitor wants to talk to us, the agent takes the request in the conversation. Nobody has to look for a form.
Questions from AI agents too
Other AI agents can question AGO through a public API, without opening the site.
Pages changed by asking
Our pages are written and changed by asking a coding agent, then reviewed before they go live.
Temana Import does it with its customers
Its agent answers on its website and on Messenger, in French, Tahitian and English, and routes qualified leads to its sales team.
Read the case studyThe homepage conversation is only the first moment
The visitor who asked a question on your site becomes a customer. AGO takes care of them from that first question to the renewal, with the same customer context at every step. That is a customer harness.
- 1Before buying
The question on your homepage
Your content, live information from your systems and a qualified lead for sales.
See this moment - 2Getting started
The first steps in your product
The agent lives inside your product and takes each new customer to their first result.
See this moment - 3Day to day
Every request, through to resolution
It reads the account, queries your systems, answers and acts, and hands over with the context.
See this moment - 4Over time
The obstacles before the renewal
It spots an obstacle in the conversations and prepares the action that helps remove it.
See this moment
Questions about a conversational homepage
What changes for your visitors, your content and your site.
Does the conversation replace our pages?+
No. The pages stay, for search engines and for visitors who prefer to browse. The conversation sits on top of them and links back to them.
Will the agent answer things that are not in our content?+
You set the rule. The usual one: answer only from your knowledge base, say so when it does not cover the question, and offer to put the visitor in touch with your team.
Do we have to move our site to AGO?+
No. The conversation works on the site you already have. AGO Sites is an option for teams who want to edit their pages by asking an agent.
Which CMS can we connect?+
Any: WordPress, Webflow, Contentful, Strapi or a CMS built in house. The knowledge base stays in sync with what you publish.
Can the agent give live prices or availability?+
Yes. It calls your systems during the conversation, so the answer reflects what they say at that moment. You choose which systems it may read and which actions it may take.
Who keeps the knowledge base up to date?+
Your content stays where your team writes it and AGO keeps it in sync. The questions the agent could not answer come back to your team as proposed additions.
Can we see what visitors ask?+
Yes. Conversations, topics and unanswered questions are in AGO, and leads reach your sales team with the conversation attached.
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 Apps and Sites
Internal tools and public sites your team builds by asking Claude or Codex.
- Temana Import
An agent that answers from the catalogue and passes qualified leads to sales.
- Customer harness
Everything around the model that talks to your customers, and who decides what.
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.
