Calendar Booking

What Calendar Booking covers

OrcaPulse already supports a meaningful scheduling and reminder layer, even though the current project does not yet expose a standalone calendar-provider integration like a full Calendly or Google Calendar connector.

The strongest current implementation is around appointment-style workflows: booking confirmations, timed reminder sequences, AI reminder calls, recall scheduling, and template support for appointment-related variables.

Appointment-style workflows

The sample workflow system already includes a healthcare appointment flow that shows how OrcaPulse treats booking-oriented journeys in practice. That flow sends a booking confirmation, waits until the right reminder windows, sends a 24-hour reminder, runs a same-day AI reminder call, and follows with post-appointment messaging.

This is useful because it shows the current booking model is workflow-first rather than calendar-widget-first.

• Confirmation pattern: booking-style flows can start with an email or message that confirms the appointment.
• Reminder pattern: waits, SMS, email, and AI call steps can be chained around the event timing.
• Operational outcome: the system already supports reducing no-shows and handling attendance confirmation as a workflow problem.

Scheduled reminders and wait logic

Calendar-style behavior in the current project is powered by the scheduling engine. Wait steps pause execution, store the next-step position, and let the scheduler resume work at the right time. Leads also carry scheduled execution times and execution states that make timed sequences observable.

This is the foundation that lets reminder and booking-adjacent workflows unfold over hours or days instead of firing every action immediately.

• Wait support: workflows can delay until the next reminder window instead of running everything at once.
• Scheduled execution: leads keep explicit execution times that the scheduler uses to resume work.
• Timeline visibility: follow-up scheduling can be reflected in timeline events such as `Follow-up Scheduled`.

Rescheduling and recall handling

OrcaPulse already has real reschedule behavior, even though it is centered on lead follow-up and appointment confirmation flows rather than a direct calendar booking connector. Leads can be manually rescheduled, and recall logic can react to outcomes like busy, voicemail, or a reschedule request by pushing the next attempt into the future.

This makes the scheduling layer flexible enough for booking-style operations that need confirmation, delay, and rescheduling logic.

• Manual reschedule: the lead controller can move both recall time and scheduled execution time to a new moment.
• Outcome-based recall: reschedule or busy-style call outcomes can schedule the next attempt automatically.
• No-show style flows: the same timing system can support reminder and re-confirmation sequences before a meeting or appointment.

Template and runtime variables

The runtime already supports template variables that fit booking-oriented communication, including placeholders such as {{date}}, {{time}}, and {{appointmentTime}}. Sample workflows and reminder content also show booking-specific copy like confirmation messages, reminder notices, and reschedule instructions.

This means the communication layer is already prepared for appointment-style flows even where the calendar system itself is not yet a first-class connector.

• Runtime placeholders: scheduling-aware variables can be resolved inside generated messages and voice prompts.
• Reminder copy support: existing templates already cover confirmation, reminder, and reschedule-style language.
• Booking-oriented prompting: AI call prompts can push toward meeting confirmation, demo scheduling, or specialist handoff.

Current project boundary

The important boundary to document clearly is that OrcaPulse does not yet expose a dedicated calendar provider integration in the current codebase. There is no clear standalone route group for booking systems, slot lookup, or two-way calendar synchronization.

So today, calendar booking is best understood as a workflow and scheduling capability rather than a fully separate booking connector. The product can coordinate appointment-oriented operations, but the external calendar-provider layer is still a future expansion area.

Next steps

After Calendar Booking, the next useful docs area is usually Operations, starting with Analytics or Templates / Workflow Library, depending on whether you want to document visibility or reusable assets next.