AgeBridge
AgeBridge Guided Project Reference build by AgeBridge

WhatsApp Booking Assistant

An assistant that reads the request, offers three openings taken from the live calendar, books the one the customer picks, confirms it and reminds them a day before. Anything that is not a booking goes to a person.

AgeBridge built this as a worked example of the solution. No client results are claimed. Build your own version and it becomes proof on your profile.

Build this yourself

Business problem

Clinics, studios and salons take most bookings over WhatsApp. Requests arrive in the evening, staff answer them the next morning, and by then some customers have booked elsewhere.

Solution

An assistant that reads the request, offers three openings taken from the live calendar, books the one the customer picks, confirms it and reminds them a day before. Anything that is not a booking goes to a person.

What was built

  • •WhatsApp Cloud API webhook with the conversation kept per phone number
  • •Understanding step that returns service, time window and name as fixed fields
  • •Three openings read from Google Calendar free/busy, never invented
  • •Booking with an idempotency key so a repeated reply cannot double book
  • •Handover to a human for complaints, prices and anything unclear

Architecture / workflow

  1. 1Message arrives on the WhatsApp Cloud API webhook
  2. 2The last five messages of that chat are loaded as context
  3. 3The model extracts the booking request, or asks one question back
  4. 4Calendar free/busy returns the openings that really exist
  5. 5The chosen slot is re-checked, booked with an idempotency key and confirmed

Integrations

WhatsAppGoogle CalendarSlack

Tools / stack

OpenAIn8nGoogle Sheets

Screenshots

Screenshot slot
Screenshot slot

Demo

No demo added yet. Builders can attach a short video.

Results

No verified results shared. AgeBridge only displays real, builder-reported outcomes.

Evidence

  • Architecture notes · Flow, data shape and the double booking guardHow data flows and why you designed it that way.

Proof

Proof score

10/100

Add demo video — 60 seconds showing the thing actually running. The single strongest proof.

Not reviewed yet. Evidence is shown exactly as the builder attached it.

Decisions and tradeoffs

  • •The calendar decides what is available. The model never suggests a time.
  • •One question at a time, in the language the customer wrote in.
  • •Complaints and price questions are handed to a person with the thread attached.

What went wrong

Nothing notable was reported.

What I'd do next

A deposit at booking time, and a waiting list for weeks that are full.

Need something like this?

Talk to the builder behind the project, or build your own version.

View in marketplaceBuild something like this