Offer availability
Read only the selected business’s authorized free/busy calendar data. Offer a small set of openings tied to this call. The assistant must not invent a time from an empty or unavailable calendar.
The Solution Workshop guide
Follow one new request from the phone to a clear next action. An answered call is the beginning, not proof of a booking or a delivered message.
Capability review: September 17, 2026. Status applies to the specific action described.
The voice pilots handle new intake and message-taking. A dedicated business route can identify its intended business; a shared entry route needs to establish which business the caller means. The receiving number and trusted routing configuration determine where work belongs.
A personal voicemail route has a different job: take a discreet message, allow a callback preference and let the caller finish. It should not turn a friend, recruiter or investor into a plumbing customer.
In these pilots, the assistant does not retrieve the caller’s old address, invoices or appointment history. Recognizing a number is not permission to open an account.
Fictional example · target workflow
Caller: “There’s a leak under the kitchen sink. Can someone come tomorrow?”
The useful result today is a bounded intake test. The target result is an explicit, verifiable handoff. Both should preserve what the caller asked for without making promises about arrival time or price.
A dedicated Texas demo has voice booking tools, but its live selection flow is under repair and is not demo-ready. Their intended contract has two parts:
Read only the selected business’s authorized free/busy calendar data. Offer a small set of openings tied to this call. The assistant must not invent a time from an empty or unavailable calendar.
The caller explicitly selects an offered opening. The server checks it again, creates the event and retains the calendar provider’s booking reference. A retry must not create a second event.
A conflict, inaccessible calendar or declined offer leaves the call at CALL REQUIRED — NOT BOOKED. This label means further work is needed; it does not prove a callback request was delivered to a professional.
How calendar authorization should work| Result | What it establishes | What still needs proof |
|---|---|---|
| Request received | The request was saved. | Follow-up, appointment and delivery. |
| CALL REQUIRED — NOT BOOKED | No confirmed appointment. | Who will review it and whether a callback was sent. |
| BOOKED | For provider calendar booking, a selected slot was rechecked and the event has a retained reference. | Invitations, customer texts and crew notifications. |
| Prepared / simulated | A draft or demonstration exists. | Any real external action. |
| Queued / posted | A provider accepted the named message action. | Delivery where available, and whether the recipient read it. |
A downloaded calendar file and a local scheduling record are useful, but neither proves that Google or Outlook was updated. Look for the provider-sync status as well as the appointment state.
The internal personal-voicemail pilot has a configured private owner Slack DM destination. A fresh end-to-end call-to-DM check remains part of acceptance. There is no verified personal SMS delivery route.
Business customer SMS and professional notifications need their own sender, consent, receiving destination and delivery evidence. They do not become available simply because voice works. A private transcript should never be placed on a public board or an open link.
A number supplied during the current call can be recorded as a contact preference. That does not authorize access to records associated with either number, and it does not mean a message has been sent.
The honest outcome is unbooked with a clear need for human review. It must not invent a transfer, dispatch, delivery receipt or callback deadline. Controlled tests should include interruptions, uncertainty, unavailable services and callers who decline text.