hi jeff!! i'm rishabh 👋
I saw you're hiring for agentic commerce.
I have a booking idea I'd like to work on.
your September 1 post
you're bringing 20 platforms
into agentic commerce
travel
tickets
food
home services
I kept thinking about what happens
when the thing you want isn't available yet.
"anything after 5
on Thursday?"
nothing yet
check again
still nothing
An operator in your replies raised this exact issue:
agents repeatedly reading availability before checkout.
a quick bit about me
I'm studying AI engineering at Penn State.
This summer, I built infrastructure simulations at Cisco.
Mandate is about scoped permission for agents.
BYOA runs a user's agent in its own sandbox.
what I'd propose
let the agent
leave a booking request
The platform saves what the customer wants.
When a slot opens, it sends the agent an offer.
I'd start with a platform that already has a waitlist.
example customer flow
"my usual barber.
Thursday or Friday, after 5.
up to $60."
agent submits the request
"I'll tell you when a spot opens."
For the first version, the customer approves every booking.
what I'd actually ship
an agent toolsubmit, check, or cancel a booking request
a platform connectoruse its waitlist and listen for matching openings
an offer callbackdeliver a priced slot with a hold expiry
a booking stepget approval, then return the confirmed appointment
A reference integration with one booking partner first.
the request outlives the chat
customer + permissionwho asked, and which agent can act
booking preferencesservice, time window, maximum total
request statuswaiting, offered, booked, cancelled, or expired
offer + booking IDsretry without charging or booking twice
The platform keeps the request.
A sleeping agent can pick up where it left off.
a cancellation comes in.
Thursday, 5:30. $45 total.
platformholds the slot and sends an offer
agent"this fits. want me to book it?"
customerapproves the actual price and appointment
platformconfirms the booking and returns its reference
If the hold runs out, the agent needs a fresh offer.
where Stripe fits
use what already exists
Link for agent payment approval
the partner's customer account
its waitlist, prices, and booking API
what we'd add
agent tools for booking requests
an adapter for the partner
reliable offer delivery + status
The partner still decides who gets the appointment.
the first demo I'd build
start with a full calendarsubmit the haircut request and end the chat
cancel an appointmentwatch the platform send a matching offer
deliver the callback twiceshow one offer and one booking
let the next offer expireshow that approval cannot book a stale slot
One real partner integration. These are proposed demo cases.
does it get more
appointments booked?
compare with the partner's current agent flow
count completed bookings and customer interventions
check availability calls per completed booking
If the existing waitlist integration already does this well, I'd move on.
I'd love to work on this
with you.
My starting point would be a booking platform
and a real request that its agents struggle to finish.