Automating bookings at a store is less about the software than about deciding what a slot is. A fitting slot is a person and a room for a length of time. A rental is an item for a date range, plus the handling time on either side. Get those definitions right and the booking rules follow. Get them wrong and the calendar will be wrong no matter which product runs it.
Decide what is bookable
Write the list before configuring anything. For most stores it looks like this: fittings and alterations, rental collections and returns, consultations for custom or bulk orders, and equipment servicing where the store offers it.
Leave ordinary shopping out. A calendar full of walk-in sales is a calendar nobody trusts.
For each entry, note three things: how long it takes, who or what it needs, and how much notice is required. A fitting might need an associate and a room for half an hour with a day of notice. A trailer rental needs the trailer, a collection window, and enough lead time to inspect it when it comes back.
Build buffers and treat items as resources
Buffers are the part stores skip and later regret. Between two fittings, ten minutes is enough to reset a room. Between two rentals of the same item, the buffer has to cover return, inspection and cleaning, which is often most of a day.
Set the buffer per item, not globally, because a costume and a floor sander do not share handling time. Where a single buffer is applied to everything, either the popular items get double-booked or the slow ones get blocked unnecessarily.
Two callers wanting the last available unit on the same weekend is the case that breaks naive booking tools. The calendar has to treat the unit as a single resource, not as a service with unlimited capacity.
Where the store has several identical units, define them as a pool with a count. The assistant can then offer the second unit without exposing which physical one it is, and the counter assigns the specific item at collection.
Where there is only one, the assistant says so and offers the nearest alternative dates rather than placing a provisional hold that will later be cancelled.
Set the lead time and the cut-off
Two numbers do most of the work. The minimum notice before a booking, so nobody books a fitting for twenty minutes from now while the associate is on the floor. And the cut-off for same-day rentals, which is usually tied to the last collection time that still allows inspection before closing.
Both should be visible to the caller as a reason, not just a refusal. "The earliest fitting today is at two" is better than "that is not available".
Confirm, remind, and record the deposit rule
Every automated booking needs a confirmation text with the date, the time, the item or service, and what to bring. Then a reminder the day before, and for rentals a second one on the collection day.
Deposits are a policy question for the owner, but the assistant needs the rule in writing so it says the same thing every time: how much, when it is taken, when it is returned, and what happens if the item is not collected. Where a payment link is part of the setup, it goes out with the confirmation rather than in a separate message later.
Write the calendar back
The booking has to appear where the counter staff look. If the assistant holds its own calendar and the store holds another, the two will disagree within a week.
Elevoi writes bookings against the live calendar and captures the caller's details at the same time, so the counter sees the booking with a name and a phone number attached. When a customer calls to move it, the same assistant can find it and move it rather than creating a second one.
Test the edges before opening it up
Run these five scenarios on your own phone before the assistant goes live.
Book a fitting at the earliest allowed time and check it appears with the buffer. Ask for two of the same rental item on one weekend and see what the second caller is offered. Request a collection outside the store's hours. Ask to move a booking that does not exist. Call at the moment the store closes and listen to what happens.
Each of those is a decision someone has to make, and making it in advance is the whole job. Elevoi for retail and rentals sets out the configuration fields, and reducing no-shows covers what happens after the booking is made.