A request is notan appointment.

The Ol’ Clip Joint sits at 5620 N 7th Street in Phoenix, and Matt runs the chair. Classic cuts, walk-ins welcome, cash only, and open till 11:30 every night of the week — which means the booking questions arrive at all hours too.

Off-the-shelf booking tools will happily put a stranger in the chair at 9 PM without asking anyone. For a single-chair shop that is not convenience, it is a scheduling problem arriving by surprise — and a client who turns up to a slot that was never really available.

The whole system is built on one rule: a request is not an appointment until Matt says so. Nothing on the site can put a client in the chair.

A client picks a service, a day, a time and leaves a name and mobile. That texts Matt with who, what and when, a confirm link, and a reply code. The client is immediately texted that it is a request and nothing is booked yet. Only when Matt confirms — one tap, or a text back — does the client get the message that says they are booked.

Online, by text, or by phone for anything sooner than an hour out. The text route writes the message and opens Messages; it is still a request, and the site says so in those words.

A pending request holds its slot, so two people cannot be sent to the same 9 PM chair. If Matt does not answer within two hours the hold expires, the time goes back on the board, and the client is told it lapsed rather than being left wondering.

The server tracks only the online flow, and the booking states — requested, held, confirmed, declined, expired — are explicit, because the failure everyone remembers is a double booking. Confirmation happens over SMS, where Matt already is, rather than in an admin panel he would have to remember to open.

Shipped with the online request flow, the SMS confirmation loop, slot holds with expiry, and the text and phone routes alongside.