Why a medical AI agent needs SOPs

What an intake SOP needs to cover

For an intake agent, an SOP is not a clinical manual. It describes the administrative work the team already does: how to qualify a request, what practical information to give, how to present an approved price or treatment, which situations are urgent, when to hand off, and what data must stay out of the system's reach.

Why a generic script fails

Two dental practices do not share the same hours, treatments, or tone. A generic agent can answer fast and still be wrong. It can also ask too many questions, miss an urgency the practice itself has defined, or give out information the team does not stand behind. Speed does not help if the next step is not the one the practice would have chosen.

At a large dental clinic in Casablanca, the work started with the procedures the operations manager provided, not with installing a bot. The volumes observed, more than 100 WhatsApp conversations a day, later fewer than nine needing human intervention, belong to that clinic and that period. They do not repeat automatically elsewhere. The method does repeat: audit the SOPs, define the boundaries, qualification, languages, escalations, testing, then deployment.

What the agent can do, what stays human

A clear SOP lets the agent handle appointments, approved pricing, validated explanations, and practical information. It bars diagnosis, prescriptions, and any decision that requires a healthcare professional. Requests for medical or insurance documents, urgencies defined by the practice, and unusual cases get handed to the team, with the context already gathered.

How we work when an SOP is incomplete

Many practices run on habits, not a document. In that case, we start with an inventory: messages received, usual answers, the information the front desk already gives out, and situations it refuses to handle alone. If the team agrees to validate these rules, an agent can be tested against those scenarios until they consider it compliant. If nobody wants to formalize the scope, we decline a generic deployment rather than promise a result nobody could actually control.

The SOP does not replace an official connection

Procedures protect the content. The connection protects the infrastructure. A practice can have excellent intake rules and still expose its number if it automates WhatsApp through an unofficial session. The reverse is also true: an official API does not make an agent reliable if nobody has defined what it is allowed to say. Both layers are necessary.

What this means for a practice in Morocco

A practice in Casablanca, Rabat, or elsewhere can reuse the method. It cannot reuse another clinic's volumes as local proof. Forteuno Web works remotely: the city pages describe service areas, not offices. The agent follows the language actually used, French, Arabic, or Darija, rather than the phone prefix alone. French serves as the fallback when the preference is unknown.