Find the answer.
Keep support moving.
Bring the KajoAI Company Knowledge Assistant to your support team. Find answers in approved manuals, product guides, and troubleshooting instructions. See the supporting sources, check the product version, and spend less time searching or interrupting a specialist.
Free 60-minute workshop. Bring a recurring support question and the documents that should answer it.
A support agent searches manuals, help pages, and old tickets before finding the relevant instruction.
Routine questions interrupt the same experienced people, even when the answer is documented.
An older guide looks useful, but its instructions do not apply to the customer's product.
For teams supporting complex products.
A practical starting point for software companies, equipment suppliers, and technical service teams whose agents regularly search substantial documentation.
A good fit
You have recurring questions, maintained product documentation, and a named support expert who can judge whether answers are correct. Start with one product family and one team.
Check the foundations first
If your help desk's existing search or AI features meet the need, use them. If the answers live only in people's heads, capture that knowledge before building an assistant.
Ask a question.
Inspect the evidence.
The assistant searches the approved material for the selected product and version. If the information is missing or inconsistent, it asks for clarification or directs the question to a person.
Useful context with each answer
Your agent gets an answer with references to the supporting passages, so they can open the original material and check it before advising a customer.
Your knowledge owner identifies the product and applicable versions for each source and agrees which guidance takes precedence. The assistant asks for a missing version and flags unresolved conflicts instead of silently choosing an instruction.
Illustrative example using fictional product documentation.
“The application stopped syncing after an update. What should I check first?”
For Example App 4.2, the troubleshooting guide says to check the connection status in Settings → Sync and record any error code. Confirm the installed version before using these steps.
- Source
- Example App troubleshooting · §2
- Applies to
- Version 4.2
- Ask the customer
- Installed version and error code
- Next step
- Check the source, then advise
In the delivered assistant, source references open the approved material. This preview shows the answer format.
Built on a real support knowledge project.
For Visual Components, the first phase brought together more than 1,400 documents and online help content. A working intranet assistant was made available to a tester group, with source references and feedback collection.
The published example covers the first implementation and testing phase. Read the project summary on KajoAI’s homepage.
Start with the questions your team answers every week.
Agree the sources, audience, supported topics, and acceptance criteria before the build. Your support expert judges the results using real questions.
- Review the material
Check document quality, product versions, permissions, and whether your existing tools already solve the problem.
- Agree the test set
Select real questions and known answers. Include missing product versions, obsolete instructions, conflicting sources, and questions the material cannot answer.
- Build and evaluate
Connect approved documents, configure access, and test answers and source references against agreed criteria.
- Review and hand over
Review the results against the agreed criteria and decide whether to expand. Receive editable workflows, documentation, and clear maintenance responsibilities.
You provide
A knowledge owner, an IT contact, approved source material, product/version labels, and support experts with time to review the test answers.
You receive
The agreed source connection, searchable index, assistant interface, evaluation results, access configuration, and handover documentation.
Validate the answers.
Build daily use from there.
Choose the outcome your team needs. After reviewing your documents and access requirements, we confirm the scope, fixed price, and delivery plan in writing.
PACKAGE 1
Pilot
€4,900
Implementation + €150/month retainer · Excluding VAT
One document set · One team · Estimated 3–4 weeks
- Connect one agreed document set: manuals, process instructions, or reviewed support-ticket material.
- Get answers with supporting references and product-version context.
- Test real support questions, missing answers, and conflicting guidance with your experts.
- Receive the findings, editable workflows, and a recommendation on whether to expand.
Outcome: evidence for your rollout decision
FOR DAILY SUPPORT WORK
In production
€9,500
Implementation + €250/month retainer · Excluding VAT
Agreed document base + your workspace · Estimated 5–7 weeks
Includes answer validation, plus:
- Connect your agreed document base and keep it current as sources change, on an agreed refresh schedule.
- Use the assistant in one agreed interface: your intranet, Teams, or a web widget behind your login.
- Monitor source refreshes and notify a named owner when they fail.
- Define behavior rules with your team, test them before launch, and train the person who owns the assistant.
Outcome: a maintained assistant for daily use
FOR A WIDER ROLLOUT
Many languages, many teams
€16,000
Implementation + €450/month retainer · Excluding VAT
Agreed teams, access groups, and languages · Estimated 7–10 weeks
Includes daily support capabilities, plus:
- Give each team access to its approved source collections.
- Test that answers, references, and saved conversations respect those access boundaries.
- Build and evaluate each agreed language version using material in that language and customer-approved reviewers.
- Report recurring questions and knowledge gaps, and review answer quality after the first 30 days.
Outcome: a controlled rollout beyond one team
Prices are indicative totals for the selected implementation, not cumulative stage fees. A pilot upgrade is quoted separately, accounting for reusable work. Delivery estimates begin when access and usable source material are available.
The same product, focused on support
These are the Company Knowledge Assistant packages applied to technical support. The pilot covers one document set and one team. Production connects the agreed document base to one workplace interface. The third package adds agreed languages, access levels, and knowledge-gap reporting.
Agree the boundaries before building
Your proposal defines source connections, document formats and volume, users, product versions, languages, refresh frequency, and acceptance criteria. We confirm access and integration feasibility before quoting. Scanned-document conversion, source rewriting, extra interfaces, and custom integrations are separately scoped.
Your monthly retainer
The package retainer covers the agreed hosting service, document maintenance, and support. Qdrant and language-model provider charges are additional. Your quote defines the refresh schedule, monitoring, support hours, response targets, and service start date. Additional development is quoted separately.
Database and AI usage costs
Qdrant database and language-model costs are paid by you in addition to the retainer. Allow an estimated €150–€500 per month combined, depending on usage volume and the model chosen. These are variable provider charges, not a fixed fee or a spending cap.
Estimated combined monthly budget: €300–€650 for Pilot, €400–€750 for In production, or €600–€950 for Many languages, many teams. These estimates combine the package retainer with the €150–€500 database and model allowance; any separately quoted additional hosting, software licenses, and applicable taxes are excluded.
Before work starts, agree provider billing arrangements, usage monitoring, the pilot period, refreshes, and the retainer start date. Your quote identifies the hosting included in the retainer, any additional hosting or license costs, and continuation, cancellation, and handover terms.
Measure useful answers, not the number of chats.
Record a baseline and agree numerical acceptance thresholds before building. Your reviewers assess the assistant on representative support questions.
Answer quality
Check correctness, whether the cited passage supports the answer, and whether the right product version is used. Track unsupported answers and appropriate escalation.
Search effort
Compare time to find a usable answer on equivalent questions, including time spent opening and checking the source.
Knowledge gaps
Track unanswered recurring questions and requests for specialist help. Assign gaps to a named knowledge owner.
Citations and testing reduce risk; they do not guarantee a correct answer every time. Agree release thresholds before building and retest after material changes.
Prepare the reply.
Keep the agent in control.
Once knowledge retrieval meets the agreed criteria, add a response draft based on the customer’s question and approved sources. The support agent checks, edits, and sends it.
Reply drafting
Connect one agreed support queue, include the relevant ticket context, and prepare a draft with internal source references. Measure draft acceptance and the amount of editing required. Not included in the packages above.
Escalation with context
If the sources do not resolve the question, prepare an escalation summary with missing details and the sources already checked. Assignment and reminders can be scoped through Request Handling.
Clear boundaries.
Fewer surprises.
Choose the setup around your support process, source quality, and access requirements.
Yes. AI can misread or combine information incorrectly. The assistant is configured to use approved sources, expose supporting references, and flag insufficient evidence. Your team tests these behaviors before launch and checks answers before using them with customers.
The first two packages use one access group whose members may read the entire approved collection. The cross-team package separates agreed collections by group. Access controls cover retrieval, references, and saved conversations. Before launch, agree how user removal and source restrictions affect indexed content, conversation history, and cached answers. Source-system permissions are mapped and tested as part of the agreed setup; automatic synchronization of individual file permissions requires explicit scoping.
The quote defines pilot refreshes; production packages keep sources current on an agreed schedule. Changed and removed sources are updated in the index, and failures are reported to the owner. Urgent removal and access changes follow a separate agreed procedure rather than waiting for the next scheduled refresh.
Yes, when approved ticket material is part of your agreed document set. Tickets can contain outdated workarounds, customer information, and advice that applies only to one installation. Agree filtering, access, and retention before including tickets. Live ticket-system connections are confirmed in the proposal.
First check the capabilities included in your existing support or workplace tools. A custom build may be useful when you need specific document processing, product-version handling, evaluation, hosting, or workflow integration. The workshop compares those needs with what you already have.
No. These packages provide an internal knowledge assistant. Reply drafting is a separately scoped extension, and your support agent reviews and sends each reply. Automatic external responses would require a separate scope, approval rules, and evaluation.
Before access is granted, agree hosting, model providers, data processing locations, retention, and access with your IT contact. You receive the editable workflows, index, and handover documentation, subject to the licenses for underlying services. Hosting and ongoing maintenance responsibilities are documented in the quote.
Show us where your support team gets stuck.
Bring a question, the documents that should answer it, and the person who knows what a good answer looks like.
What you leave with
A view of source readiness, a proposed pilot boundary, and the questions to test first. If improving your existing search or documentation is the better next step, we will say so.
Free 60-minute workshop · No obligation to proceed
Explore the full Company Knowledge Assistant offer. Need to assign incoming work and chase decisions? Explore Request Handling. This assistant focuses on finding and checking support knowledge.