The Barbershops pack

Everything in the pack,
and everything it will not do.

The CRM fields and stages that follow every call, what it connects to, and what it never says. Why any of it matters is on the Barbershops page.

Barbershops — this pack was built for the calls that reach this kind of business. Illustrative photograph.

Fields that are filled when the call ends

This trade pack is built to order. Below is the design we switch on for you: the fields, stages and never-say list are drafted, so with your price list and hours it can be switched on within days.

Service and time neededBarber requestedSlot bookedPrice quoted from your listWalk-in or appointmentSame-day reminder sent

The stages an inquiry moves through

How many inquiries sit at each stage, on one line — in the order work actually flows in a Barbershops.

Inquiry→Booked→Same-day reminder→In the chair→Four-week rebook
PipelinePipelineInquiry4Booked3Same-day 2In the ch1Four-week1

What it will not do

Not a setting you switch on and off. These are blocked when the Barbershops answering is built; anything that touches them goes to a person instead of being answered.

  • It never judges scalp problems or hair loss.“My hair is thinning” or “my scalp itches” gets no cause and no product — it gets a dermatologist and a note for the owner.
  • It never guesses which barber someone means.“The guy from last time” is logged as a request, not resolved by a machine. The owner assigns the chair.
  • It never states a walk-in wait time it cannot see.No “ten minutes, tops.” It books a slot, or reads the live wait count you keep — nothing else.
  • It never prices a service that is not on your list.Perms, colour or anything unlisted is logged as “we’ll confirm and call back.”

This page is the list; the argument is on the other one. What kind of call comes in at night, what a missed one costs, and why a machine must not say certain things are written on the page this pack came from.