One Calendar Event or Per-Service Events?
Hi everyone,
I’m building a voice AI receptionist using Retell AI and I’d like some advice on the best architecture for appointment scheduling. For a business like a dental clinic that offers multiple services (for example: teeth whitening, tooth extraction, consultations, etc.), I’m unsure which approach is better:
Option A: Create one general calendar event and one booking function that handles all services. The service type would simply be stored as a field when the appointment is booked.
Option B: Create separate calendar events and separate booking functions for each service (e.g., one for teeth whitening, another for tooth extraction, etc.).
The same design question also applies to other functions such as:
- check_availability
-reschedule_appointment
-cancel_appointment
From a scalability and system design perspective, which approach do you recommend and why?
Thanks in advance for your insights.
3
3 comments
Emanuel Mudzanani
3
One Calendar Event or Per-Service Events?
Brendan's AI Community
skool.com/brendan
A free community for AI Voice Agents and n8n.
Join to learn, share ideas, and build real systems for the future.
Leaderboard (30-day)
Powered by