A scope edge for first contact and calendar handoff
This page defines where Appointment Copilot’s responsibility ends and where your organization’s responsibility remains.
It is written to support internal review and operational clarity.
Appointment Copilot handles first contact. It acknowledges inbound inquiries, captures information within configured fields, routes appropriately, and documents the interaction.
The clean handoff ends at calendar confirmation. After calendar confirmation, internal handling begins.
These lists describe scope, not outcomes.
Scope note: Appointment Copilot does not evaluate inquiries, decide outcomes, or assume responsibility for professional decisions. It is a first-contact handling layer with explicit termination at calendar confirmation (when scheduling is enabled).
Scheduling is treated as a boundary event. If scheduling is enabled for a workflow, the system can confirm a calendar event as the terminal state for first contact.
After that point, responsibility transitions to your internal team. Appointment Copilot does not continue downstream interaction unless explicitly configured for additional first-contact handling scenarios.
Interactions are documented to support internal review. This allows your team to verify what information was captured, what routing occurred, and what the system communicated.
Your organization determines how documentation is reviewed, retained, and incorporated into internal processes.