Why not just use an off-the-shelf chatbot from a vendor?
For general information bots, a SaaS product works perfectly well. An AI intake is different: it has to match the schema of your underlying system exactly, the protocols of your sector and the tone of your organisation. You also want to keep the prompts, evaluation cases and RAG sources under your own control, because they directly affect the data that ends up in your EHR, HRIS or CRM. With a closed vendor, you never get full visibility into those. A custom intake also produces a far better audit trail — relevant as soon as the AI Act or the regulator comes knocking.
Which LLM do you use?
That depends on the use case, data category, languages and privacy requirements. For most healthcare, government and financial clients, we land on Azure OpenAI in Western Europe or Claude via AWS Bedrock in Frankfurt. For clients who, as a matter of policy, don't want a US cloud provider, we run Mistral or Llama in your own environment. We work vendor-independently: you own the prompts, the schema and the evaluation set, and we can swap the model if price or performance gives us reason to.
How do you prevent the model from hallucinating during an intake?
Three layers. First, we use structured outputs / function calling, so the model must shape its output according to a predefined JSON schema. Second, we use RAG on the organisation's official knowledge, so that answers and follow-up questions are grounded in approved sources rather than the model's training data. Third, an evaluation pipeline with realistic cases validates every model or prompt change. For high-risk applications, a human review always sits in between before the intake outcome affects any decision-making.
Can an AI intake process patient or client data?
In principle, yes, provided the right compliance layer is in place: a DPIA, a suitable data processing agreement, sub-processors in line with your GDPR policy, and LLM inference within the EU. For some healthcare organisations we opt for on-premise or dedicated cloud for broader reasons — for example, with particularly vulnerable groups. We advise on what fits for each project and work with your data protection officer, using NEN 7510 controls as a framework. Something similar applies to law firms, given professional secrecy.
How does an AI intake handle people who would rather talk to a person?
Every AI intake we build has a visible "I'd rather talk to a person" route. At any moment, users can step out of the flow and reach a human member of staff — by phone, a callback request or a handover to live chat. It isn't an option but a design requirement: some groups don't suit an AI flow, and forcing them into one is a bad idea. The handover route is also an AI Act transparency requirement for high-risk applications.
Can you integrate the intake with our EHR, HRIS or CRM?
Yes. We have experience with HiX, Epic, ChipSoft, CGM and Cura on the EHR side; AFAS, Workday, BambooHR and Personio on the HRIS side; and Salesforce, HubSpot and Dynamics on the CRM side. The integration typically runs via HL7 FHIR for healthcare, a REST API for modern systems, or a SOAP layer for older ones. If your system is built in-house, we integrate against a custom API. See also our page on
case management system development.
How do you measure the quality of an AI intake?
We build an evaluation pipeline with realistic cases, often based on real, anonymised historical intakes from your existing form. Every prompt or schema change automatically runs against that set and produces a score per cohort: how often the classification is correct, how often the structured fields are filled in correctly, how often the AI escalates to a human and how often that is justified. Alongside these quantitative measurements, we look qualitatively at failures, cases where the AI silently fills in the wrong field, because those cause the most harm.
How do you handle the AI Act for our intake?
We start with an AI Act classification: low risk, limited transparency obligations, or high risk (intake as input for medical triage, legal decisions, credit refusals, HR assessments). For high-risk applications we take care of the mandatory risk management documentation, the data governance requirements, the transparency layer, the human oversight mechanism, the logging the regulator is entitled to inspect, and post-market monitoring after go-live. We align with an existing ISMS.
Who owns the code, prompts and data?
You do. We hand over the complete source code, prompts, JSON schemas, evaluation cases and build pipelines. The RAG sources and intake records live in your cloud or with a hosting partner of your choice. No lock-in on the technology or on the choice of LLM: we earn our money from good work that lasts, not from clients who are stuck with us.
What are the typical pitfalls of an AI intake project?
Three patterns. One: the schema isn't properly thought through, so the AI has to produce data that the back end doesn't know what to do with. Two: there is no evaluation pipeline, and the first prompt change silently breaks an edge case that nobody notices until a user complains. Three: the human side of the workflow isn't taken into account. The AI now delivers neat intake records, but the team that has to pick them up still works to the old rhythm. Our sprint approach addresses all three structurally.