Dentistry

One phone, one nurse, and she is chairside.

In a dental practice the call arrives at exactly the moment the nurse is holding the suction. It rings once, it rings twice, and the third call goes to the practice across the road. This page describes what a voice assistant takes off that line, and — just as precisely — what it is not allowed to touch.

The assistant answers on the first ring, asks whether this is a check-up or pain, reads the free slots from the practice calendar, books the appointment, sends the confirmation by SMS, and hands anything that sounds like an emergency straight to a person. It gives no clinical advice at all.

§01 The calls

What it takes off the reception line

Not everything on a practice phone can be automated, and the list below is short for that reason: these are the call types that end in a booking, a confirmation or a transfer — the ones where the outcome can actually be checked afterwards.

A new appointment

The patient says what hurts, or that they want a check-up, and the assistant offers the real free slots for the right dentist.

Rescheduling and cancelling

It finds the appointment by phone number, cancels or moves it, and releases the slot for somebody else.

Hours and price questions

Answered from the price list and opening hours you upload, not from what the model happens to know about dentistry in general.

Tomorrow confirmations

It dials the patients booked for tomorrow and marks who confirmed, who moved and who did not answer.

A declared emergency

Acute pain, trauma, bleeding that will not stop. Here it asks nothing further: the call goes to a person.

Out-of-hours calls

Evenings and Sundays it takes the request, writes it down and sends the summary through before morning.

§02 The flow

What happens, step by step

The flow below is made of tools that exist in the product today. Each step names the tool the assistant calls, so it is visible where the conversation stops and your own systems begin.

How an assistant is built

01 Greet, and split the two cases The assistant first line asks outright whether this is pain that started now or an ordinary appointment. It is the only branch that matters, so it goes first.
02 Find a real slot It calls the availability tool against the practice calendar, through the Google Calendar or Outlook Calendar connector, and offers two or three genuine times rather than a promise that somebody will ring back.
03 Book it It creates the calendar event with the patient name, phone number and reason, against the chosen dentist. If the slot went in the meantime, the tool returns an error and the assistant offers another.
04 Send the confirmation An SMS through the Twilio connector with date, time and address. For patients who messaged on WhatsApp in the last twenty-four hours, that channel works too.
05 Hand over emergencies For pain, the assistant transfers to the on-call number. The transfer can be blind or consultative, meaning the caller waits while the dentist is reached.
06 Close with something written down The call ends with a transcript, a recording if you switched it on, an ended reason, and the structured output you asked for.

§03 The written trail

What is left behind when the call ends

A call that leaves nothing written behind is a call you cannot check. Every row below is produced by a real tool, not by a field somebody fills in later.

What connects to CallAgent today

What is left behind when the call ends
In the calendar	The appointment event, with the patient, the phone number and the reason in the description.
By SMS	The confirmation sent to the patient, with the send time recorded against the call.
In your spreadsheet	A new row in Google Sheets or Airtable, if that is where you keep the day book, carrying the call outcome.
On the call record	The transcript, the tool-call events, the ended reason and the structured output with the fields you defined.

§04 Limits

What it does not do for a dental practice

This section is on every page of this site, and here it matters more than anywhere else, because there is a patient in pain at the other end of the line. None of what follows is on next month roadmap; these are things the product does not do.

What is finished and what is not

No clinical advice and no triage It does not say whether a pain can wait until Tuesday, does not recommend a treatment and does not read an X-ray. It can only recognise the words of an emergency and give the call to a person.
No link to your practice software There is no ready-made connector for the dental practice-management systems used in Romania. If you want the patient record inside the call, that is your own HTTP tool over your API, or an MCP server.
It takes no money No deposits, no card processing. The Stripe connector is read-only by design: it finds the customer and the invoices, it does not move funds.
It will not take your PDFs The knowledge base accepts text, Markdown, CSV, HTML, JSON, XML, DOCX and XLSX. A scanned price list has to be converted first.
No outcome figures We do not claim how far no-shows fall or how many extra bookings you catch, because we have not measured that in a real practice. The product has placed eleven real calls so far and the status page says which.

§05 Questions

What practices ask us

Will the patient realise they are talking to a machine?

Yes, if they ask, because the assistant is allowed to say so and you can make it say so in the opening line. The voice is natural, but a long and complicated conversation gives it away. Our advice is to disclose up front — not because somebody forces you to, but because a patient who works it out for themselves at minute three becomes much harder to help.

What happens if somebody calls with a real emergency?

The assistant is configured to ask nothing further and transfer to the on-call number. The transfer is blind or consultative, your choice. If nobody answers the on-call number, the call comes back to the assistant, which takes the details and passes them on.

Can it see who the patient is in my practice software?

Only if that software has an API and a tool is written for it. There is no ready-made connector for Romanian practice-management systems. What works today with no development at all is the calendar: Google Calendar, Outlook Calendar or Calendly.

What does a booking call cost?

It is billed on real talk seconds: a platform margin of 0.10 euro a minute, on top of which sit the transcription, model, voice and telephony vendors at their own price. If you bring your own keys, that part costs nothing through us. A minute and a half is a reasonable order of magnitude for a booking call.

Does it speak proper Romanian, with diacritics and patient names?

The language is pinned explicitly on the assistant. Romanian proper names remain the hardest part for any transcriber, which is why the assistant reads the name and phone number back for confirmation before it writes the booking, rather than assuming it heard correctly.

§06 Onward

Notes

1 The tools named on this page are the ones in App\Services\Integrations\ConnectorRegistry carrying implemented. Anything that is only in the catalogue, without that flag, is not named here as though it worked.
2 Calendar booking uses the check_availability and create_event capabilities of the Google Calendar connector; the text message uses send_sms from the Twilio connector. Both carry implemented in the registry.