What these systems normally control
Requirements for assessment; confirm supported actions before relying on this workflow.
Bookable time, resource availability, appointment types, reminder emails, and, in some products, shift schedules.
Calendars and Scheduling
Keep scheduling changes connected to the people doing the work.
Provider options and connection limits
Providers to assess for calendars and scheduling
Google CalendarConnect your own account
Microsoft Outlook CalendarConnect your own account
CalendlyNeeds assessment
Acuity SchedulingNeeds assessment
Check the actual connection before changing your process.
On Pro, the QuickBooks Online connection imports customers and invoices from your own company and does not write back. It still needs checking with your company. Other provider names and the information flows below describe requirements to assess, not ready-to-use connections. Confirm the provider, plan, permissions, direction and any setup cost before work begins.
Why the specialized system usually stays
Requirements for assessment; confirm supported actions before relying on this workflow.
Team calendars carry personal availability, holidays, and PTO. Some scheduling products own SMS reminders customers already trust. The Forge connects to them so an appointment booked anywhere still starts your workflow.
Information to review for import
Requirements for assessment; confirm supported actions before relying on this workflow.
- Scheduled appointments and updates
- Rescheduled and cancelled events
- Attendee details and appointment type
- Resource assignment (staff member, room, chair)
Information to review for export
Requirements for assessment; confirm supported actions before relying on this workflow.
- Appointment slots based on operational rules (crew availability, licensing, region)
- Reminder and confirmation communications from an operational context
- Assignment changes when operations reassigns work
- No-show and completion status back to the calendar
Events to consider during setup
Requirements for assessment; confirm supported actions before relying on this workflow.
- Appointment booked
- Appointment cancelled or moved
- Appointment marked complete
- No-show recorded
Manual work the proposed connection may reduce
Requirements for assessment; confirm supported actions before relying on this workflow.
- Copying appointments into a job list
- Emailing crews their day
- Manually reminding customers of an upcoming visit
- Reassigning appointments by voice when a resource drops out
Whose work improves
Requirements for assessment; confirm supported actions before relying on this workflow.
- Office administrator
- Operations manager
- Field employee, technician, or provider
- Owner / executive
Reports that become possible
Requirements for assessment; confirm supported actions before relying on this workflow.
- Booking source attribution
- No-show rate by service or channel
- Utilization by resource or crew
- Time from booking to service delivery
Access and permission notes
Requirements for assessment; confirm supported actions before relying on this workflow.
- Uses provider OAuth against the specific calendar granted.
- Personal calendars are not read unless the user explicitly connects them.
- Sensitive event bodies can be excluded from sync.
Common category-wide limitations
Requirements for assessment; confirm supported actions before relying on this workflow.
- Two-way sync depth varies widely across providers.
- Some booking pages don't emit rescheduled events at all — only new bookings.
What might be replaced after review
Requirements for assessment; confirm supported actions before relying on this workflow.
Lightweight booking pages are typically absorbed by The Forge once operations is stable. Staff-calendar and PTO management usually remain in the workplace calendar.