SkillClosing
Appointments and Bookings
Books into a real gap and refuses to leave one empty
What is Appointments and Bookings?
Appointment and booking management is the practice of offering, writing, reminding and reassigning slots strictly against a business's real calendar availability, so a cancelled slot goes to the first person waiting. luup opens the booking inside the conversation: while the customer is still on the line it reads the genuinely open hours, writes the chosen one into the calendar and sends confirmation on the customer's own channel. A cancelled slot is offered to the next person in the queue, not broadcast to everyone.
An empty hour stays empty; nobody hears about the cancellation and the day never fills back up.
The cancelled slot goes to the first person waiting and the day fills again.
How does it work?
- 1
Availability is read
Real gaps, service duration and the resource (engineer, room, chair) are computed together.
- 2
Hours are offered
Only genuinely open hours are named, while the customer is on the line or writing.
- 3
The booking is written
The chosen hour goes into the calendar and confirmation is sent on the customer's own channel.
- 4
A reminder goes out
A reminder is sent before the appointment, so a likely no-show shows up early.
- 5
Cancellations are reassigned
The freed slot is offered to the next person on the waiting list — one at a time, not to everyone.
What does it need?
A skill with a missing precondition is not hidden in the panel — it is shown with the gap. Hiding what is required only produces disappointment during setup.
- A connected calendar
- Service durations
- At least one inbound channel
What it deliberately does not do
Claiming a result is easy. What follows is not a claim but a set of limits the product enforces mechanically: the skill cannot do these things, because a layer that cannot be switched off stops it.
- It never offers an hour that is not genuinely free, and writes no overlapping booking.
- It does not broadcast a cancelled slot; it offers it to one person at a time, in order.
- It refuses bookings beyond capacity unless you have explicitly allowed it as a rule.
Where it sits on the autonomy ladder
A 0–4 ladder decides how much the assistant may do without asking you, and it is set separately for each channel and each topic. The meaning of each rung is the same across every skill.
Appointments and Bookings comes into play at rung 3 of the ladder.
- 0
Listens only
Writes nothing to customers; it only records.
- 1
Drafts a reply
Writes it but does not send it; the draft waits in the panel.
- 2
Waits for approval
The reply is ready; sending it is your decision.
- 3
Answers on its own
Sends, and stops to call you in when it gets stuck.
- 4
Full authority
Books, quotes and collects payment.
Wherever the ladder sits, every outgoing message passes the Conversation Rules and the consent check; neither layer can be switched off.
SSS
Sık sorulanlar
luup keeps the appointment in its own calendar and syncs it both ways with the calendar you connect. Until that connection exists, an entry in your external calendar is invisible to luup — which is why a calendar connection is required before the skill is switched on.
No. luup computes availability together with service duration and resource capacity, so a busy slot is never shown as free. If you want to deliberately overbook, you have to define that as a rule; the default behaviour is to refuse the clash.
The freed slot is offered to the first person on the waiting list, with a window to reply. If the window closes, it moves to the next person. Announcing one slot to everybody produced a race that nobody turned up for, so offers go out one at a time.
Yes. The link in the confirmation lets them move or cancel the appointment; the change lands in the calendar immediately and the freed slot returns to the waiting list.