Skip to main content
FATOU HEALTH

Scheduling

Live scheduling with explicit confirmation.

Fatou Health connects a supported scheduling system to one approved workflow. The model can discuss the appointment, but server-side rules control which tenant, appointment type, calendar, and action are actually authorized.

Scope before automationAuthority stays explicitUncertainty stays visible

How Fatou Health works

Scheduling built to fail safely

The goal is not simply to call a calendar API. The goal is to make the booking path correct, reviewable, and hard to execute twice.

Approved appointment mapping

The workflow is bound to the configured practice, appointment type, calendar, and timezone. It does not choose an arbitrary service because a model suggested one.

Real availability only

The receptionist offers times returned by the live scheduling integration. If availability cannot be verified, it does not invent a slot.

Exact proposal first

The visitor sees the specific service, date, time, and booking identity before the consequential action is allowed to run.

Explicit confirmation

A current server-side proposal must be explicitly confirmed. A vague or stale 'yes' is not enough to authorize a different booking.

Duplicate protection

Booking attempts use a deterministic identity and server-side execution controls so a retry or repeated confirmation does not blindly create another appointment.

Uncertain outcomes fail closed

If the scheduling provider returns an uncertain result, Fatou Health does not automatically retry and risk a duplicate. The outcome is recorded for reconciliation or human review.

For technical review

Verify the integration boundary before you connect a calendar.

The public docs explain what a connection grants, what it does not grant, how booking requests are authorized, and which API contracts are intended for integration work.