Company reportedLive since Mar 2026Added Oct 2026

Doctolib

Doctolib ships an AI agent that lets clinicians build their own note templates by chatting

Doctolib built an AI agent, the Consultation Template Manager, that helps doctors create custom templates for the notes its AI scribe writes. It went from internal hackathon to external beta in about three weeks. Of users who started it, 78% saved a customized template.

Key figures

Copied exactly from the sources. Copy any figure with its citation.

78%

Share of users who started using the agent and ended up saving a customized consultation template1

About nine times out of ten

Share of saved templates that needed only small edits or none before saving1

About half

Share of practitioners testing the agent whose own template is used in a real consultation summary, usually within a few days1

About three weeks

Time from internal hackathon to production with external beta practitioners1

What it took

CostNot disclosed
TeamTwo full-time engineers (software, machine learning) plus part-time product, design and product marketing staff1
TimelineAbout three weeks from hackathon (early March 2026) to production beta1

The problem

Doctolib offers an AI scribe, the Consultation Assistant, that listens to a patient visit and drafts the clinical note. The time saving depends on the note reading as that doctor would have written it. Two cardiologists will not write alike, so every mismatch sends the doctor back to rewrite. Doctolib's product let doctors add instructions to note templates, but writing a good template took time and technical skill most practitioners did not have.

What they built

The Consultation Template Manager swaps a settings screen for a chat. A clinician says what kind of note template is needed, with its specialty and structure. The agent asks multiple-choice questions, drafts a template, and refines it as the clinician reacts, for example "add an allergies section". It can also restructure an old free-form template in one pass. Behind it, a small group of cooperating AI agents is coordinated by one that routes each request to an interviewer, a builder or a converter.

How they did it

The idea came from an internal hackathon at the start of March 2026. About three weeks later, the agent was live in production with external beta practitioners. The team stayed small: two full-time engineers (one software, one machine learning) with part-time help from product management, design and product marketing colleagues.

The speed came from an existing AI platform. It supplies an agent framework built on Google's Agent Development Kit, a gateway that lets Doctolib switch language model providers without changing application code, automated deployment, and built-in monitoring and testing. Doctolib's Medical Excellence committee reviewed the product before release, and staff tested an alpha in week one.

Before release, the team ran automated tests where a model played doctors with different specialties and goals, and other models scored whether the agent repeated questions, adapted to the specialty and produced a coherent template.

Results

Doctolib reports figures from the roughly 6,000 practitioners with access. Among users who began using the agent, 78% finish by saving a customized template. Doctolib says that about nine times out of ten the saved template carries minor edits or none. Roughly half of those who try the agent go on to use their own template in a real consultation summary, usually within a few days. The agent runs in France and Germany.

These are adoption measures from an early rollout. The post does not report time saved per note.

What to copy

Pick the step that stops people from using a feature well, and let a conversational agent do it for them. Reuse a shared platform for deployment and evaluation so the first release takes weeks, and track whether people keep what the agent produces.

Lessons for your project

  1. Fix the real blocker. Doctolib's scribe saved time only if notes matched each doctor's style, and writing a good template was too hard, so the agent targeted that step.

  2. Build the platform first. The team says three weeks was possible because model access, deployment, monitoring and testing already existed for earlier AI products.

  3. Test with simulated users before release. Doctolib built clinician personas and a simulator to run full conversations through the agent and score them.

  4. Release in stages. Internal staff used an alpha in the first week, then external beta users, then a gradual rollout, with a medical safety committee review before release.

  5. Measure whether people keep what the AI makes. Saved templates and use in real consultations were the signals Doctolib tracked.

Caveats

  • Doctolib's own engineering blog is the only source. No independent outlet confirms the figures.
  • The figures measure adoption of the agent's output, not time saved. The post does not say how many users started the agent or how long the measurement period was.
  • The post does not name the language model. It names Google's Agent Development Kit as the framework and says the model can be switched through a gateway.
  • The date comes from the blog's feed entry (18 September 2026), because Medium blocked the article page itself. The March 2026 release date is the post's own wording.
  • The post says rollout was gradual and that A/B testing would come later, so the results are from an early stage.

Sources

  1. From hackathon to production in 3 weeks: inside Doctolib's AI factory

    Doctolib engineering blog (Medium) · 2026-09-18 · Company blog · medium.com

Summarized in our own words from the sources above. Spotted an error? See corrections.