Skip to content

Have an AI chatbot built

We build chatbots that answer questions using your own sources, connect them to your systems and keep them up to date. We built a virtual assistant for NFZ.

The virtual assistant we built for NFZ replaces the annual pharmacy booklet with information that stays up to date

“The NFZ Virtual Assistant has significantly improved our clients’ workflow. […] it has become an indispensable part of our clients’ daily work.” Alberto Fernandez, Project Pharmacist - NFZ

Read the case study

Can a chatbot answer our questions without making things up?

Employees, customers or members keep asking the same questions about rules, contracts or procedures. A chatbot using your own documents first finds the relevant passage and answers based on it. If the answer isn’t there, it should say so.

Book a conversation

A chatbot that answers from your sources and works with your systems

Discuss your chatbot

Answers from documents

For Fokker Services Group, we built Anthony Chat, which uses a RAG model to retrieve relevant information from internal documents and present it clearly.

Connected to existing systems

Dex, the chatbot for PostNL, is connected to existing systems, so the knowledge base does not need to be maintained in multiple places.

A test set with real questions

Before launch, we test answers against questions from real situations: do they match the source, and does the chatbot say when it does not know?

Up to date after launch

With NFZ’s virtual assistant, all information stays up to date. We agree who updates the sources and monitor the quality of the answers.

We first define which questions the chatbot answers, and which it doesn’t

  1. Questions and sources

    Which questions come up most often, who asks them, and which documents or systems contain the answers?

  2. Build and test

    We build the chatbot using those sources and test it with employees on a fixed set of real questions.

  3. Go live with a designated owner

    When the chatbot goes live, it’s clear who updates the sources, who reviews the conversation logs and who manages it.

Would our own chatbot add value, or is an off-the-shelf product enough?

Talk it through with us

A good fit if

A service desk or experienced colleagues keep receiving the same questions about rules, contracts or products, and the answers are in documents or systems you can connect to.

Not a good fit if

The answer is already in one easy-to-find place, or every question still needs to be investigated by a member of staff. A better FAQ or search function would help more.

What determines the scope

The number of sources and systems, whether the chatbot is for internal use or for customers, whether conversations contain personal data, which languages it needs to support, and how much ongoing management we take on.

What if it gives a wrong answer?

That’s why it answers using your own sources and cites them, says when the information isn’t there, and refers the question to a member of staff. Logs show which questions it gets wrong.

A chat feature in your software, our assistant Joost or a custom-built chatbot?

A feature in your software

Choose this if your service desk or CRM software has a chat feature that already covers your sources, and it’s clear where conversations are stored.

Joost for internal knowledge

Choose this if employees mainly search SharePoint, Teams and manuals. In that case, our internal AI assistant Joost is easier to set up.

A custom-built chatbot

Choose this if the chatbot needs to work with your own systems or serve customers and members. Our advice: start with one clearly defined group of questions.

Our chatbots answer questions from pharmacists, PostNL employees and Fokker employees

Data Science Lab has worked with data and AI since 2016, as a Databricks Partner and Microsoft Partner. We can also manage what we build: refreshing data sources, checking answers and maintaining integrations.

Book an introductory meeting

Your most frequently asked questions and your sources shape the first conversation

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your point of contact. In the first conversation, we discuss which questions the chatbot should answer, who it is for and which sources it should use.

What questions should your chatbot be able to answer?

Describe who asks the questions, where the answers are currently stored and which systems are involved. We’ll reply by email or arrange an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

Building an AI chatbot or AI assistant involves more than switching on a language model. You decide which questions it should answer, connect the sources, test the answers, integrate it with your systems, address privacy and agree on how it will be managed.

We build this as part of generative AI. You can find all our services on the services page.

Usually through retrieval-augmented generation (RAG): for each question, the chatbot first finds the relevant passages in your documents, and the language model formulates an answer based only on those passages. That is how Anthony Chat, which we built for Fokker Services Group, works.

Read how it works technically in our blog post about internal LLMs and RAG.

With a fixed set of real questions and their correct answers, put together with the people who currently answer those questions. For each response, we check whether it matches the source, cites that source and says it does not know when the answer is unavailable.

We run the test set again whenever the sources, instructions or model change.

Yes. Dex, the chatbot we built for PostNL, connects to existing systems so the knowledge base does not need to be stored and maintained in multiple places. An integration can also retrieve information, such as the status of an application, using the user’s access rights.

Automatically categorising or routing questions falls under NLP and text analysis.

You decide this during development: which language model to use, whether to run it in a cloud environment or on your own servers, whether conversations are stored and who can see them. For NFZ, we worked with Microsoft Azure, among other things. If the chatbot processes personal data, the GDPR applies and a DPIA may be needed.

Read what this involves on our DPIA for AI page.

Yes. The transparency rules of the AI Act have applied since 2 August 2026. According to the Dutch Data Protection Authority, an AI system such as a chatbot must tell you at the start of the conversation that you are talking to AI, in writing, visually or through audio. Exceptions apply.

Your legal adviser can interpret the legal requirements. We build the notification into the chatbot.

Sources change: contracts, regulations and product information. At NFZ, the most important information used to be in an annual pharmacy booklet, which could become outdated during the year. Maintenance means updating sources, rerunning the test set, reviewing logs and maintaining integrations. Your team can do this, or we can.

If you would rather have a dedicated engineer on your team, see hire an AI engineer.

When the questions rarely come up, the answer is already available in one easy-to-find place, or every question requires a bespoke response from a member of staff. In those cases, a better FAQ, search function or form will help more.

If your main focus is internal knowledge in SharePoint and Teams, take a look at Joost, our internal AI assistant.