
I built this booking agent for a healthcare provider with five locations and one overloaded phone line. Receptionists answered calls between check-ins, patients waited on hold, and missed calls left slots empty. The provider processed 200+ bookings per week, so every lost call cost real revenue.
I shipped two surfaces. Patients meet a chat widget on the clinic website. It answers questions about doctors, hours, and visit preparation, offers open slots from the scheduling API, and confirms bookings by SMS. Staff open a dashboard. It shows the day schedule per location, flags double bookings, and lists callbacks with phone numbers and reasons.
Compliance shaped the build before a single booking flowed through it. Every tool call lands in an audit table with session id and approval reference. Phone numbers pass through a redaction pass before they reach logs. Each row carries a thirty-day retention stamp with nightly deletion. The provider passed its data review before launch with zero rework.
Eight weeks after launch, phone load at reception dropped by half and slot fill rose from 78 to 94 percent. The provider now runs the agent across all five locations, and staff onboard new hires with the dashboard in one sitting.