Skip to main content
Audact
See the offer

Integration · CGM Z1

Write the booking back into the practice system.

Integration · CGM Z1: No delivery date committed

Inbound appointment intake and recall outreach for dental practices, with the result written back into the practice system instead of retyped. The system is CGM Z1 — CompuGroup Medical's dental information system, sold alongside CGM Z1.PRO and CGM XDENT. This page used to name a product called CGM Dentinet; CGM has no product by that name, and the address still carries the old one. Audact governs the conversation: the Article 50 disclosure, the professional scope, the detection of checksum-validated identifiers (BSN, IBAN, card). The practice system keeps being the record. This is a system we write back to and not a partnership.

What the agent produces per call

{
  "event": "call.completed",
  "outcome": "appointment_requested",
  "outcome_source": "conversation",
  "confirmed_by": null,
  "receipt_id": "rcpt_01HX7K9M3P4Q5R6S7T8U9V",
  "article_50": { "disclosed": true, "clause": "1", "at_turn": 1 },
  "scope": { "pack": "dental_de", "locale": "de-DE", "out_of_scope_turns": 0 },
  "write_back": {
    "system": "cgm_z1",
    "patient_ref": "sha256:e3b0c44...",
    "starts_at": "2026-09-03T09:30:00+02:00",
    "provider": "dr_meier",
    "note": "Kontrolle, Recall 6 Monate"
  }
}

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

outcome is what was requested in the call; confirmed_by stays null until the system of record confirms it.

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, and the duty of confidentiality applies to whoever processes it.
Regulation (EU) 2016/679 (GDPR), Art. 9

What Audact governs in the call

Article 50 disclosure spoken at the top of the call and recorded.
In controlled testing
Professional scope: out-of-scope clinical advice is checked per sentence segment before it is sent to speech.
In controlled testing
Checksum-validated identifiers (BSN, IBAN, card) are detected; other patient data is not in the tested scope.
In controlled testing
Write-back of appointments, recalls and contact notes into CGM Z1.
Planned

Sector

Dental practices, where the phone is the front door.

A dental practice answers the same four questions all day and loses the fifth caller to voicemail. The value is not that a machine answers; it is that what the machine says stays inside what a practice is allowed to say, and that the booking lands in the system the front desk actually uses.

Professional scope is the part that makes this a different product from a generic voice agent. A caller asking about pain is asking a clinical question, and the answer belongs to a person — the agent books, it does not diagnose.

Setup

Four steps, once the integration ships.

  1. Agree how Audact reaches your CGM Z1 installation, and who holds the credentials.
  2. Map agent personas to practice locations and providers.
  3. Configure the professional scope rules and the disclosure wording.
  4. Run in shadow mode (appointments mirror without committing), then switch to active.

Questions

Is CGM a partner?
No. CGM Z1 is a practice-management system we write back to, and this page says so rather than implying an endorsement that does not exist.
When does the write-back ship?
There is no committed date. There is no signed agreement with CGM and no pilot in a practice. Dental is also not in our first launch: a dental call touches health data, a special category under Article 9 GDPR that pulls in the impact assessment of Article 35, and that assessment is a condition of onboarding here. The governance inside the call is in controlled testing; the write-back is what is waiting.

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