Tattoo studios and barbers
Fictional internal demonstrationA request arrives mid-session. The chair keeps the artist, the system keeps the request.
An artist is halfway through a half-day session when a new half-sleeve inquiry lands. The phone is sitting right there on the bench, and answering it properly means stopping the work in front of a paying client.
Nobody breaks the session. The customer chooses an artist, holds a slot, and pays the deposit that makes the slot real.
what actually ran
Step by step, without the owner in the middle.
Customer record
One fictional half-sleeve request, first message to return visit.
Moment
Customer sees
Studio record
01Inquiry becomes a booking record
Customer sees
“Here is the half-sleeve request form. Pick an artist to continue.”
Studio record
Record opened · source: studio inbox · status: unbooked
02Customer chooses artist and time
Customer sees
“Two openings with your artist this month. Hold one for 15 minutes.”
Studio record
Artist + slot attached · status: held, unpaid
03Deposit confirms the slot
Customer sees
“Deposit received. Your session is confirmed and applies to the final price.”
Studio record
Deposit cleared · status: confirmed · slot removed from availability
04Reminder and reschedule path scheduled
Customer sees
“Session in 24 hours. Need to move it? Reschedule here.”
Studio record
Reminder set queued · reschedule link live · old reminders cancelled on change
05Completed visit triggers review, then rebooking
Customer sees
“Thanks for coming in. One-tap review link. Touch-up window opens later.”
Studio record
Marked complete · review ask sent once · rebooking nudge scheduled
Needs attention: customer requests a policy exception
Deposit waiver asked for outside the stated policy. The record pauses here and waits for the owner.
- Rule
- A slot is not held until the deposit clears.
- Exception
- A policy exception request pauses the record for the owner.
- Check
- A test booking without payment must not create a held slot.
Illustrative workflow · fictional business and data · subject to tool compatibility and written scope.
what stays true after handoff
- A slot is not held until the deposit clears.
- Deposit applies to the final price. The cancellation window is stated at checkout.
- Reminders send on a fixed schedule tied to appointment start time.
- Review requests send only after a completed appointment, never after a cancellation.
what it will not do
It will not decide the deposit amount or the cancellation policy. The owner sets both, and the system enforces exactly what the owner wrote.
- It does not create demand. If nobody is trying to book, this changes nothing.
- It does not decide the deposit amount or refund policy for the owner.
- It does not manage disputes or chargebacks on the owner's behalf.
the system in this story
Booking-to-Review System · $3,500
Deposits, confirmations, reminders, review requests, and rebooking connected behind the site you already have. Timeline: 10 business days.
other stories