Alaska Road Trip books its Concierge planning calls on AgentDraft.

A concierge trip is not a passive booking link. The customer has just paid for judgment: routes, trade-offs, pacing, and the things a form cannot capture. The next screen has to do one concrete job well: show real open times on the founder's calendar and let the traveler reserve one without waiting for manual coordination.

That is where AgentDraft fits. The product page promises the call is booked from Yoni's live calendar after checkout. The scheduling surface can use the same availability, hold, and commit path as the rest of AgentDraft, so the paid customer is never racing a stale list of times.

The flow is deliberately boring from the customer's point of view: pay for the Concierge tier, pick a time, join the call. The useful machinery is behind the screen:

traveler buys Concierge
  │
  ├─▶ checkout completes            → booking screen opens
  │
  ├─▶ GET  /v1/availability         → Yoni's live open planning slots
  │
  ├─▶ POST /v1/bookings mode=hold   → protect the chosen time during confirmation
  │
  └─▶ POST /v1/bookings mode=commit → create the call on the winning path

The important part is the hold. A travel customer should not lose a slot because another writer touched the calendar while they were confirming details. AgentDraft gives the checkout handoff a temporary claim, then commits only if that claim still wins.

This is first-party, and the page should say so plainly. It still matters because it is a real paid workflow, with a customer-visible failure mode if scheduling gets sloppy. “Book your call after checkout” only works if availability is current, the selected slot can be held, and the final commit is deterministic.

• The public proof page publishes the offer. The Concierge page shows the $497 tier and explains that the planning call is selected from Yoni's live calendar after checkout.
• The booking path is the same primitive agents use. Availability, hold, and commit are not a special Alaska Road Trip integration; they are the protocol surface.
• Double-booking protection is by construction. A slot cannot be committed twice through AgentDraft because the final write resolves to one winner.

• Alaska Road Trip Concierge — the public offer page for the live planning-call tier.
• Calendar API for AI agents — the availability, hold, and commit path behind the handoff.
• The yoniryabinski.com booking widget — the sibling first-party scheduling story.