Which calendars does VoiceForge book into?

Google Calendar, Calendly, Cal.com and GoHighLevel (via API). The agent checks live availability, offers only open slots, validates the write and logs outcome. Add any calendar that exposes availability + create-event — the Agent Spec stays the same.

How do you prevent double-booking?

Live availability check before offering a time, validation before write, and idempotency where the calendar allows it. VoiceForge validates tool calls, checks workspace permissions and records the booking event regardless of outcome — so a race shows as “already booked” not “two confirmations.”

Can it reschedule and handle no-shows?

Yes. Pair inbound booking with consent-aware reminder calls and SMS the client can confirm or reschedule from. Track answered, confirmed, rescheduled, no-show and opted out — the reminder guide shows the loop.

Booking that respects the calendar

The agent books only what the calendar says is free

Offering a time without checking the calendar is how double-bookings happen on speakerphone. VoiceForge checks live availability before offering a slot, then validates and logs the write.

Start building See how it works

Live availability, not guesswork

Before offering “Tuesday 2pm,” the agent queries the connected calendar — Google, Calendly, Cal.com or GHL — and offers only open slots. No hallucinated times, no “let me check and call you back.”

Validated, permissioned, idempotent

Tool calls are validated, scoped to the workspace and idempotent where the calendar allows it. Every booking, reschedule and cancellation is an audit-logged event with transcript and outcome.

Reschedule and no-show recovery

Pair booking with reminder calls and SMS. The client says “reschedule” or “confirm” and the agent moves the event without human triage. No-show reduction follows when the loop is complete.

Works with the calendar they already use

Keep the calendar the business trusts. The Agent Spec is provider-neutral — switch Calendly for Cal.com without rebuilding the agent.

Test the booking path in the browser

Run “book → double-book attempt → reschedule → no-show” in a browser test call with transcript and event stream — before telephony is attached.

Frequently asked questions

Which calendars does VoiceForge book into?: Google Calendar, Calendly, Cal.com and GoHighLevel (via API). The agent checks live availability, offers only open slots, validates the write and logs outcome. Add any calendar that exposes availability + create-event — the Agent Spec stays the same.
How do you prevent double-booking?: Live availability check before offering a time, validation before write, and idempotency where the calendar allows it. VoiceForge validates tool calls, checks workspace permissions and records the booking event regardless of outcome — so a race shows as “already booked” not “two confirmations.”
Can it reschedule and handle no-shows?: Yes. Pair inbound booking with consent-aware reminder calls and SMS the client can confirm or reschedule from. Track answered, confirmed, rescheduled, no-show and opted out — the reminder guide shows the loop.