Skip to main content
Audact
See the offer

Integration · Doctolib

Patient booking across three markets, one duty.

Planned · no date set

Doctolib is the booking layer for medical practices across France, Germany and Italy. The planned integration lets an agent check availability, book and reschedule, while the disclosure, the professional boundary and the handling of health data run inside the call rather than in the practice's policy folder.

What the agent produces per call

{
  "event": "call.completed",
  "outcome": "reschedule_requested",
  "outcome_source": "conversation",
  "confirmed_by": null,
  "receipt_id": "rcpt_01HX7K9M3P4Q5R6S7T8U9V",
  "article_50": { "disclosed": true, "clause": "1", "at_turn": 1, "locale": "de-DE" },
  "scope": { "pack": "medical_de", "escalated_to_human": false },
  "write_back": {
    "system": "doctolib",
    "patient_ref": "sha256:e3b0c44...",
    "from": "2026-09-03T08:20:00+02:00",
    "to": "2026-09-10T11:00:00+02:00"
  }
}

Worked example. Acme GmbH and Nova Industries are fictional; no customer data appears here.

The locale on the disclosure is not cosmetic: the wording is per jurisdiction because the national layer on top of Article 50 differs.

What applies to the call

The patient must be told they are speaking to an AI system, at the latest at the first interaction.
Regulation (EU) 2024/1689, Art. 50(1) and 50(5)
Health data may only be processed on one of the narrow grounds.
Regulation (EU) 2016/679 (GDPR), Art. 9
The data subject may request erasure, and the controller must be able to carry it out.
Regulation (EU) 2016/679 (GDPR), Art. 17

What Audact governs in the call

Article 50 disclosure per jurisdiction, spoken and recorded.
In controlled testing · Germany: national policy layer active. Netherlands: in development. Belgium and Austria: planned.
Professional scope: clinical questions route to a person.
In controlled testing
Checksum-validated identifiers (BSN, IBAN, card) are detected; other patient data is not in the tested scope.
In controlled testing
Availability lookup, booking and rescheduling through Doctolib.
Planned

Sector

Three countries, three wordings, one obligation.

A multi-site operator running France, Germany and Italy does not get to write one disclosure script. The obligation is the same across the union; the wording, the national layer and the professional rules are not, and a single script is how a group of practices ends up non-compliant in two of three markets at once.

Policy packs are per jurisdiction for that reason. The agent speaks the wording the country requires, and the receipt records which one it spoke.

Setup

Four steps, once the integration ships.

  1. Connect Audact to your Doctolib account.
  2. Select the practices and appointment types the agent may book against.
  3. Enable the policy pack per country and review the disclosure wording.
  4. Run in shadow mode, then switch to active.

Questions

Does the agent handle results or prescriptions?
It can take the request and route it. Anything that is a clinical judgement goes to a person, and the receipt records the turn where the conversation turned.
Which countries are covered on day one?
The German policy pack is active, checked by a person against the national text, and the Dutch one is in progress.

Do not wait for the integration

Every integration will be built on the same six endpoints. They run inside the managed platform; no public API is served on api.audact.ai yet, apart from the published Merkle roots. Where a sector system exposes an API, the shorter route is to call it from your side and let Audact govern the conversation.

See the API

Related