What this demonstrates
This project shows two clinic scheduling paths that stay in sync with Google Calendar:
- A native Google Appointment Scheduling handoff where the agent sends the patient a direct booking link.
- A custom scheduler where the backend owns availability, booking, rescheduling, cancellation, and notifications.
The goal is to make the voice agent useful without pretending the prompt alone can perform operational work. The agent gathers intent and structured details, then calls backend tools that validate and execute the request.
System shape
The workflow connects a phone agent, custom actions, Cloud Run services, Google Calendar APIs, and SMS delivery through Twilio.
The important design choice is that booking logic belongs in backend services, not in the conversational prompt. That keeps validation, error handling, calendar writes, and notification logic testable.
Compliance posture
The system is designed for HIPAA-aware deployment: access can be controlled, activity can be audited, data can be encrypted, and retention policies can be applied.
Full HIPAA compliance still depends on signed Business Associate Agreements with the relevant vendors and correctly configured production accounts.