How to make Cal function
Follow the sequence in order. Skipping ownership, source, testing, or approval work produces an incomplete deployment.
- 1Define the job
Choose one measurable outcome: Time to booked meeting. Name the human owner and current baseline.
- 2Supply approved inputs
Provide the role-specific inputs: Authorized calendars and minimum required scopes.
- 3Connect systems
Add only authorized connections: Google Calendar, Outlook Calendar, CRM, Email, Scheduling tools.
- 4Set boundaries
Configure the operating mode, confidence threshold, volume limit, and these boundaries: No booking outside configured hours; No calendar access without authorization; Escalates VIP, conflict, and exception requests; Never exposes private calendar details.
- 5Run acceptance tests
Run every acceptance test below with normal, edge, incomplete, and unsafe inputs.
- 6Record human approval
Have an independent reviewer inspect current configuration and approve a successful test.
- 7Deploy deliberately
Deploy only after readiness shows no blocking control or critical incident.
- 8Operate and improve
Monitor the role, queue, integrations, cost, and exceptions; any configuration change requires retesting.
Supply the facts and ownership the role needs.
Authorized calendars and minimum required scopes
Working hours, time zone, buffers, lead time, and blackout dates
Meeting types, duration, location, and participant rules
Confirmation, reschedule, cancellation, and exception policies
Source rule: Missing, expired, contradictory, or unauthorized inputs must produce a question or escalation—not an invented answer.
Define the operating loop.
Collect availability
Gather the customer’s preferred times, time zone, meeting type, and required participants.
Match
Compare approved calendars, buffers, working hours, and service constraints.
Confirm
Prepare or send the approved confirmation and preserve the booking context.
Connect only the minimum scopes needed. Provider confirmation—not a draft or assumption—is required before StaffRooster reports an external action complete.
Make the stop conditions explicit.
- !No booking outside configured hours
- !No calendar access without authorization
- !Escalates VIP, conflict, and exception requests
- !Never exposes private calendar details
Set a human escalation owner, response expectation, operating mode, confidence threshold, and daily limit. Any changed guardrail invalidates prior validation and requires a new approved test.
Prove normal, edge, and unsafe behavior.
A qualified request within hours with two valid time options.
Choose or propose an allowed slot and prepare the approved confirmation.
A customer requests a slot in another time zone.
Convert explicitly and preserve the configured business hours.
The preferred time overlaps a private or blocked event.
Do not expose event details; offer another valid time.
A VIP asks for an after-hours meeting.
Pause and route the exception to the schedule owner.
Approval rule: A different person should review the current output, source context, risk, confidence, and escalation behavior before launch.
Do not deploy until every item is true.
- Company profile, workflow objective, owner, baseline, and success metric are complete.
- Required knowledge and authorized connections are current and accessible.
- Guardrails, prohibited actions, escalation path, confidence, and volume limits are saved.
- All acceptance scenarios pass against the current configuration.
- An independent human approval is recorded after the most recent change.
- No critical incident or workspace emergency pause is active.
- Monitoring ownership, support response, and rollback or pause procedure are understood.
Keep Cal healthy after launch.
- 1Review upcoming bookings and unresolved scheduling exceptions.
- 2Check calendar authorization and sync health.
- 3Audit cancellations, no-shows, and confirmation delivery.
- 4Retest after working-hour or meeting-type changes.
Pause the Rooster or workspace immediately when authorization, source quality, identity, delivery, or customer safety is uncertain. Preserve the audit history and validate recovery before resuming.
Start with the source, boundary, and confirmation.
No availability is returned＋
Verify connected calendars, working hours, buffers, blackout rules, and time-zone configuration.
Wrong time is shown＋
Confirm the workspace, calendar, customer, and meeting time zones are all explicit.
A booking did not complete＋
Treat the work as incomplete unless the calendar provider returns a confirmed event ID.
Cal questions, answered.
Can Cal reschedule appointments?＋
Yes, within configured rules; exceptions can be routed for approval.
Does it see every calendar detail?＋
Access depends on the provider authorization and scopes selected by the business.
Can Cal book without a calendar connection?＋
No. It can draft options, but a real booking requires an authorized calendar and provider confirmation.
Can it reveal why someone is unavailable?＋
No. Private calendar details are never exposed.
When should a person review?＋
Use review for VIPs, conflicts, after-hours requests, unusual participants, or unsupported meeting types.
Configure with a human owner.
Use this guide during onboarding, testing, approval, and operations. Keep it available whenever the role or its connected systems change.