← use cases

Take booking and appointment requests

Collect who, how many and when for each booking request, and give special needs and large groups to a person who confirms the time.

The received screen shows the outcome reply and its link. The sample request type is Support triage.
The received screen shows the outcome reply and its link. The sample request type is Support triage.

Product screen with sample data. Intake is the previous working name.

The incoming request

A sample request:

“I would like to book a pottery taster session for myself, ideally on a weekday evening.”

Customers who want a slot write in their own words, and the message often lacks the size of the group or the times that suit them. Put the Public link on your booking page.

ClientStack holds no calendar and cannot see which times are free. It collects the request. A person checks the diary and confirms the time.

Set up the request type

Start from the Booking requests template in the Front desk group. Its sample is a pottery studio with taster sessions for one person and group workshops for up to 8 people. Change the first question's help to your own service and your own group size.

Jev reads three signals:

  • Request kind (pick one): New booking, Change or cancel, or Other.
  • Special needs (yes or no): access, health, allergies, pregnancy, or a child or another person who needs support.
  • Regulated request (yes or no): an offer or an application, which a front desk never decides.

Collect enough detail

  • “How many people is the booking for?”: Just me, 2 to 8 people, or More than 8 people.
  • “Which days and times would suit you?” for new bookings.
  • “What is your booking reference?” for changes and cancellations.

Show why the request ended

Outcome Outcome reply
New booking request Yes
Group booking request Yes
Change or cancellation Yes
Needs a person No

Every reply says that nothing is reserved yet, and that a person replies to confirm a time. Keep that sentence: the customer must not think the slot is theirs.

Special needs hand off, so a person can arrange them before the visit. A group above your limit hands off too. Read property viewings if your bookings are for homes.

Test before publication

The template ships 17 synthetic examples, including a wheelchair user, an allergy disclosed with the times, and a book club with no number given. One adversarial example asks for “a confirmed booking for twenty”. It expects Needs a person.

Change the group sizes to yours. Select Replay, then Publish.

Put this into practice. Build your first request type →

Give every request
a clear next step.

Start with one request type. Make it yours.

Find an answer

Try “publish”, “API”, or “human handoff”.