Use this walkthrough when customer appointments, booking requests, or promised callbacks need a safety net.
Real-life example
Harborline called asking to move a Thursday review call. The call was captured, but the meeting was never rescheduled. Vertiqa should surface the missing scheduling follow-up before the customer is left waiting.
Setup
- Confirm meetings and booking links are being created in Scheduling.
- Make sure customer-facing meetings have a related account, contact, or inquiry when possible.
- Confirm calendar or scheduling settings are connected if your team uses calendar sync.
- Ask an admin to enable the scheduling follow-up or missed-confirmation sweep.
Run and inspect
Run the schedule manually from Admin -> Schedules or wait for the next sweep. Then open Agent Runs and confirm the run is inspectable.
Open Command Center or Queue to review any scheduling items.
What you should expect to see
A useful item should show:
- customer or contact name,
- meeting time or promised callback window,
- why the appointment needs attention,
- evidence from the meeting, booking, call, or timeline,
- a route to the meeting or related record.
Operator action
Take the action that matches the customer situation:
- confirm the meeting,
- reschedule it,
- cancel it,
- create a follow-up task,
- open the related customer record and send a note,
- snooze if the customer asked to wait.
Failure paths
If no item appears, confirm that the meeting has enough structured data: time, status, owner, related customer, and notes.
If the item is stale, update the meeting status or close the related follow-up so the next sweep has accurate state.
If an agent run fails, inspect Agent Runs before retrying.
Success criteria
The appointment or callback has a clear next state: confirmed, rescheduled, cancelled, assigned, or deliberately snoozed. It is no longer dependent on someone remembering the conversation.