Booking Funnel Built for Kept Appointments

Kept appointments are the number. A calendar that fills sixty slots and holds forty-one is running a thirty-two percent no-show rate, which for local services and tour operations is unremarkable, and it is the figure this engagement moves. Booked volume is easy to raise and tells you almost nothing. What gets built: A booking flow where price, or an honest price range, appears before the time picker. Asking somebody to choose Tuesday at 14:00 before they know what it costs produces bookings that cancel, and undoing that is the most common change we make. Availability reads live from the Google Calendar freebusy endpoint, so a slot a technician blocked twenty minutes ago is already gone. Routing is round robin by service area or by tour language, with travel buffers and a minimum lead time that reflects how far your people actually drive rather than what the widget defaults to. No account creation at any point; a mobile number and an email is the entire record. Time, which is where these break: Israel's daylight saving does not follow Europe's. It starts the Friday before the last Sunday in March and ends on the Sunday between Rosh Hashanah and Yom Kippur, so any system holding a fixed UTC+3 offset runs an hour wrong for weeks every autumn. Times are stored in UTC with Asia/Jerusalem as the display zone, and both transition dates are tested explicitly before launch. Closures for chag and erev chag come from the Hebcal API rather than a spreadsheet somebody maintains, so a Sukkot slot is never sold. Friday hours end early and Saturday is closed by default; for a business that does operate on Shabbat, that is a switch we set on instruction, not an assumption we make about you. Confirmation and reminders: Confirmation over WhatsApp carrying the address as a maps link, the price, and what the customer needs to have ready when you arrive. Reminders at 24 hours and 2 hours, each with a one-tap reschedule. The reschedule link is what recovers revenue: somebody who cannot make Tuesday will move to Thursday if it takes one tap, and will simply not appear if it takes a phone call during working hours. For high-value slots, meaning a private tour or a same-day pickup, a deposit through Bit or card, sized so it stings slightly and refunded automatically on a reschedule inside the window. Phone is not a fallback: A visible tel: link at the top of the page on mobile, with calls tracked to source. A meaningful share of Israeli local-services buyers over fifty will never complete a form, and a page that buries the number to protect a funnel metric is losing the better lead. We will argue for the number staying visible even when it makes the dashboard look worse. Not included: We do not run dispatch, staff your phone, or write your cancellation policy. We do not build native apps. We will not put a booking widget in front of a calendar your staff do not actually keep; if the real source of truth is a paper diary at the front desk, that is an operations fix and it comes first. Integration with field service platforms goes as far as their public APIs and no further. Not a fit: Chains with more than twenty calendars and no single owner of scheduling data. Anyone whose stated problem is more bookings rather than better ones, since this work reduces booked volume in the first month about as often as it raises it. Delivery: The live flow, calendar and reminder integrations, the chag closure rules, and a four-week readout of booked against kept with the no-show reasons your staff recorded.