Skip to main content
FATOU HEALTH

Exploring workflow · not in standard pilot

Voice can be added when the workflow earns it.

Voice and phone handling are an exploration direction, not part of Fatou Health’s standard commercial pilot today. Any future production use would require separate channel, escalation, recording, privacy, reliability, and verification work.

Scope before automationAuthority stays explicitUncertainty stays visible

How Fatou Health works

What a voice workflow would require

Fatou Health does not treat a phone number as a checkbox. The call path has to be mapped and tested like any other consequential workflow.

Call-path mapping

Define which calls the agent may handle, which it must transfer or escalate, and what should happen when nobody is available.

Approved knowledge

Responses come from the same practice-specific Customer Brain and approved boundaries used by the receptionist workflow.

Scheduling controls

If voice scheduling is enabled, it should use the same live availability, exact proposal, confirmation, and duplicate-protection controls as the approved booking workflow.

Human escalation

Clinical, urgent, ambiguous, complaint, or unsupported requests need an explicit human path rather than an improvised AI answer.

Observable outcomes

Calls and consequential actions need reviewable outcomes so the practice can understand what happened and correct failures.

Managed rollout

Fatou Health would test the voice workflow privately before launch and monitor it after approval. It is not included automatically in the website receptionist pilot.