AI chatbots for business that answer from your own data

We build on large language models that retrieve from your sources, not on decision trees. Where a fixed menu serves users better, for example to choose a language or a department, we keep it.

• Customer service chatbots that answer questions about orders, products and policies, and hand over to your support team
• Internal help desk assistants for IT, HR or operations questions, answering from your own documentation
• Sales and pre-sales assistants that find product details, availability and terms
• Assistants inside your product, so your customers get help where they work
• Voice assistants for phone lines, where the speed of each response matters

Many help desk and CRM products now include an AI chatbot. If your answers live in one knowledge base and the chatbot only has to answer, such a product is often the faster choice, and we will tell you so in the first call.

A custom chatbot is worth building when answers depend on several systems, when the chatbot has to act and not only answer, when data must stay in your environment, or when you need to test and control its behaviour in detail.

The main risk of a business chatbot is a confident wrong answer. We reduce it in three ways: every answer cites its source, the chatbot declines when its sources don't cover a question, and a test set of real questions, including ones it should refuse, runs before every change. No chatbot is right every time; the test set shows how often yours is right on your questions.

Permissions apply to every answer. A customer sees only their own orders, and an employee gets answers only from documents their role may open.

A chatbot that can't hand over frustrates customers. We agree with your support team which topics, customers and situations go to a person, and the chatbot passes the conversation with its context so nobody has to ask again. Your team also sees which questions the chatbot could not answer, which shows where the documentation needs work.

An online retailer's support team answers the same questions about delivery times, returns and order status every day. The chatbot answers policy questions from the returns and shipping pages, looks up order status in the shop system for logged-in customers, and starts a return only after the customer confirms it. Complaints, damaged goods and any refund above an agreed amount go straight to a person.

The team tracks the share of conversations resolved without handover, the reasons for handovers and customer ratings, next to the cost per conversation.

Every chatbot we launch comes with what your team needs to keep it right after we leave:

• A test set built from past tickets or chat logs, with expected answers and sources
• A limited launch on one channel or customer group first
• Monitoring of answer quality, handovers and cost per conversation
• A runbook for adding sources, changing what the chatbot may do and investigating a wrong answer