Options
Internal calendars
Internal calendars
Recepta.ai’s own calendars, for teams that don’t run one elsewhere. Create a calendar per crew, truck, or technician and the agent books against real capacity rather than a single shared grid.The simplest option if you’re currently scheduling on a whiteboard or in a spreadsheet.
Google Calendar
Google Calendar
Connect via OAuth from Integrations. Recepta.ai reads availability and writes bookings back, so appointments appear in the calendar your team already checks.
Apple Calendar
Apple Calendar
Connects over CalDAV using an iCloud app-specific password rather than OAuth. Generate one in your Apple ID security settings — don’t use your main Apple password.
Your field-service CRM
Your field-service CRM
Jobber and Housecall Pro carry their own scheduling. Booking through the CRM keeps jobs, customers, and dispatch in one system. Usually the right choice if you already run one. See Field-service CRM.
GoHighLevel calendars
GoHighLevel calendars
If you run GHL, its calendars can be used as the availability source. See CRM & marketing.
Choosing one
1
Already on a field-service CRM?
Book through it. Splitting scheduling between two systems creates conflicts nobody notices until a crew turns up somewhere twice.
2
Team lives in Google or Apple Calendar?
Connect that. Bookings show up where your people already look.
3
Nothing consistent today?
Use internal calendars. One per crew.
Making availability realistic
A connected calendar tells the agent when you’re free. Your appointment settings tell it what a bookable slot actually looks like — duration, travel buffers, arrival windows, capacity. Both need to be right:- Block out non-job time — lunch, admin, supplier runs. If it isn’t on the calendar, it’s bookable.
- Set travel buffers that reflect your service area, not best-case traffic.
- Keep crew count and concurrent-job capacity current when someone’s on leave.
