PRODUCT GUIDE
Arrange the next conversation
Create a governed booking with durable provider readback.
Product guide · Based on the September 18, 2026 product documentation. Connected proof is reported for specific operations; this guide is not a new live certification. Private work and provider authorization take place in Agent.
What this is for
Create a governed booking with durable provider readback.
Runs booking availability, provider create/readback, cancellation/reschedule and L3 eligibility for provider-specific proven scopes.
Before you start
Prerequisites
- booking authority
- provider readiness
- available slot
Operating modes and access
Documented modes: ASSIST and AGENT. Modes do not grant access or execution authority.
Relevant roles: PUBLIC TOKEN HOLDER, OWNER, ADMIN, OPERATOR. A listed role does not imply that every action on the screen is permitted.
Check mode and role boundariesWhat is checked
- signed token or workspace authority
- provider identity
- idempotency
Evidence and limits
Documented connected scope. The supplied documentation reports bounded connected evidence. It does not establish every configuration, provider, user or operation.
Documented provider scope
- Cal.com exact path
- Google Calendar exact async path
Important limits
- Microsoft positive Booking-to-L3 remains blocked by Teams capability; provider parity is not claimed.
Apply it to your service
Start with the service you deliver. Industry examples are hypotheses to review, not proof of demand or results.
Choose the next step
Explore the public sample, or open Agent to review the relevant setup and permissions for an existing Workspace.
YOUR NEXT MOVE
Start with a clearer
next move.
Explore a Blueprint before deciding how much work to delegate.
Preview available. Paid checkout is not open.