Booking links

Booking links let you share a URL that a guest can use to schedule with you. Dispatch generates the page, queries your connected calendars for availability, and creates the resulting event on the right calendar. Booking links are how you stop the "what times work for you?" exchange.

Booking links work against Google Calendar and Outlook Calendar. You can create multiple links with different durations, buffers, and visibility windows.

What it does

• Recurring or single-use links. A recurring link is a persistent URL guests can book against repeatedly. A single-use link is for one specific meeting; once booked, the URL is spent.
• Real availability. The booking flow reads free/busy from your connected calendars when rendering the link, so booked slots disappear immediately. Availability computation runs on Dispatch's server, not as an agent tool call.
• Configurable. Duration, buffer time, minimum notice, weekly availability windows, and time zone are all set per link.
• Event creation. When a guest books, the booking flow creates the event on the configured calendar and sends invitations. Guest bookings run server-side, not through the agent's tool surface, so the permission gate is not in that path. The agent's own calendar-create tools are still gated when the agent creates an event for you directly.
• Reschedule and cancel. Guests can reschedule or cancel from the same link; Dispatch reconciles the change on your calendar through the same booking-flow mutations.

How to use it

The most common pattern is to ask Dispatch for a link.

• "Make me a booking link for 30-minute intro calls, weekdays 10am to 4pm Pacific."
• "Single-use booking link for the Acme follow-up. Pick a Tuesday or Thursday afternoon next week."
• "Send my standard 30-minute link to Sarah."

To inspect or manage existing links:

• "List my active booking links."
• "Show me what's been booked on my intro-call link this week."

Limits and behavior

• Calendar provider must be connected. A link needs a calendar to read availability from and to write events into.
• Time zone defaults to yours. Guests see times in their local time zone; the event is created in the configured calendar's time zone.
• Per-organization. Booking links belong to the organization in which they were created.

Related

• Google Calendar connection details
• Outlook Calendar connection details

For agents

• Booking links are managed by the booking-pages connector. The agent-facing tools create and update booking-page records.
• Guest-facing availability, booking, reschedule, and cancel flows run on Dispatch's server. Availability is computed there by reading free/busy from the configured calendar provider; it is not an agent tool call.
• Guest bookings execute server-side; the permission gate is not in that path. The agent's calendar-create tools remain gated when invoked by the agent directly.
• Recurring links remain active until the user deletes them; single-use links are spent on first booking.