A support assistant that answers from your own information
A first-answer assistant replies using your own documents, policies and past conversations, not the internet and not guesses about your product. It answers the repeat questions and shows where each answer came from, checks that it is sure before replying, and passes everything else to a person with the details already gathered.
What problem this solves
“Sixty per cent of our tickets are the same eight questions, and our team answers them one at a time all day.”
Sixty per cent of customer questions tend to be the same eight, answered one at a time, all day, by people you hired for the other forty per cent. The repetition is not only costly. It is what makes support jobs hard to keep filled.
The trap is that everybody knows this now, and the market is full of bots that answer the easy questions badly. The value was never in having a bot. It is in how many questions get closed without a person, and how smoothly the rest are handed over. A setup that ignores the second number is a demo the client cancels in month three.
That is why we plan this around measuring from the start: how many questions it closes and how well it hands over, reported monthly, so it either proves itself with numbers or gets changed.
Typically 30–60% of repeat questions answered without a person, and the rest reaching your team with the details already collected.
Market contextFreelance chatbot work grew 71% in a year on Upwork. What matters now is not having a bot. It is how many questions get closed and how smoothly a person takes over. Without that, it is a demo the client cancels in month three.Source: Upwork, In-Demand Skills 2026
What happens, step by step
- 01Question arrives
- 02Look it up in your documents
- 03Answer, showing where it came from
- 04Check it is sure
- 05Hand over to a person
Who this is for
Online stores, software companies and service businesses with a support inbox that has an obvious repeating tail, and enough written information for an assistant to answer from. If the knowledge lives only in your team's heads, writing it down is the first project, not this one.
It suits a few dozen questions a week upward. The threshold is less about volume than about repetition: two hundred varied questions are answered less often than eighty near-identical ones.
It is not a replacement for a support team and we will not sell it as one. It stops your team spending its day on the eight questions your documents already answer.
- Sectors
- E-commerce · SaaS · Services
- Strongest fit
- United StatesEuropeLatAm
What it costs
| Size | Build | Monthly |
|---|---|---|
| Micro | Build$600–$1,200 | Monthly$150–$300/mo |
| Small business | Build$1,500–$3,000 | Monthly$400–$800/mo |
| Mid-market | Build$3,500–$7,000 | Monthly$900–$1,800/mo |
All prices are in US dollars. Work outside the agreed scope is $35–$60/hour. The cost of AI services is passed on at cost plus 20%, or you can use your own account with the AI provider.
Frequently asked questions
- What share of questions will it close?
- Typically thirty to sixty per cent of repeat questions, with the rest reaching your team with the details already collected. The range is wide because it depends almost entirely on how repetitive your questions are and how good your documents are. We can look at both during the first call instead of guessing.
- How do we stop it making things up?
- It answers from passages of your own documents and shows which ones. When it finds nothing relevant, it does not make up an answer. It hands over. That behavior is the whole point. An assistant left to fill gaps on its own is exactly what gets a support bot switched off.
- What happens to questions it cannot handle?
- They reach a person with the conversation, the customer's details and what the assistant already found out, so whoever picks it up is not starting from scratch. Customers notice the handover more than anything else, and it is what the monthly report tracks.
- Does it sit on our website or in our support inbox?
- Either, and usually both. It connects to the common support inboxes, and a chat box on your site covers the pre-sale questions that never become a support request. Both use the same set of documents, so there is one thing to keep current instead of two.
- Who keeps the information up to date?
- You do. It is your documentation, and keeping it current is work you should be doing anyway. What the care plan covers is the quality of the answers: spotting the questions that get answered badly and fixing the gap, which is hard to see from the inside.
We do not sell a bot that says hello. We sell fewer questions reaching your team, and we measure it every month.
The numbers on this page come from public industry studies. They are not results from Amagenon clients. On the audit call we check them against your own numbers.
Find out what your process is actually costing you
A 30-minute call and a one-page report on the three automations that would help your business most. Free while we build our first case studies.