Ask an owner what their hours are and they'll tell you in a second. Ask where those hours are written down and it takes longer, because the honest answer is: in five or six places, typed by different people at different times.
- Your Google Business Profile
- Your website footer or contact page
- Your online booking page
- Your voicemail greeting
- Whatever answers the phone — a person with a sticky note, or software
- Often a social profile or two, and any delivery or reservation app
Every one of those is a promise. When they disagree, the customer believes whichever one they happened to see, and the first time they learn it was wrong is when they're standing outside.
The copy nobody updated
Hours drift for a boring reason: each place was set up once, by whoever was setting it up, and nobody owns keeping them in step.
You extend Thursdays to eight. You change the sign on the door and tell the staff. Google still says six, because the person who claimed the profile left two years ago. The booking page still offers nothing after six, so the new evening slots never fill — and you conclude nobody wants Thursday evenings.
That last part is the expensive bit. Wrong hours don't only send people to a locked door. They also hide hours you're open, and the demand that would have filled them never shows up anywhere you'd notice.
The one that invents hours
There's a worse failure than stale hours: hours nobody set at all.
Some booking systems, when a business hasn't entered its hours, quietly fall back to a default — often something like 9 to 7, every day of the week. The page looks complete. It offers Sunday mornings. It takes bookings for them.
We found exactly this in our own stack last month. A demo shop that had never filled in its hours was being described to callers as open 9:00 to 7:00 daily, because the scheduling engine filled the gap with its default and nothing downstream could tell a default from a real schedule. The phone stated it as fact. We changed it so assumed hours are now marked as assumed, and the phone stops asserting them — but the lesson is worth checking on whatever you use: if you never told it your hours, find out what it thinks they are.
Holidays are where it shows
Regular hours are usually right in at least one place. Holiday hours are usually right in none.
Closing early on Christmas Eve means updating Google's special hours, the booking page and the voicemail, and telling whoever answers the phone — and doing it well before the week, because the people planning around you check ahead. Most places change the door on the day, which is too late for everyone who already made plans.
A fifteen-minute check
Do this once now, and again at every change of season:
- Search for your business on Google from a phone and read the hours panel, including the special hours for the next holiday.
- Open your booking page and try to book on your earliest and latest day. Does it offer times you're closed, or hide times you're open?
- Call your own number after hours and listen to the greeting. Does it state hours? Are they right?
- Ask whatever answers the phone "what time do you close on Saturday?" and hear what it says.
- Read the website footer and contact page, and any listing a web developer set up for you.
Where they disagree, fix the one customers see most first — for most businesses that's Google — then decide which one is the source everything else gets updated from.
Make one of them the master
The long-term fix isn't more checking. It's one place where hours are set, and everything else reading from it.
That's hard when your listings are spread across five companies, but you can get close by making sure the two places that make commitments read the same schedule: the booking page and the phone. A wrong Google listing sends someone to a locked door. A wrong booking system books them into it.
In Sonorch the booking page and the phone read the same schedule, which is much of the point of the nail salon POS system being one system rather than several. And if the phone is where your hours cause the most trouble, it's worth reading why it rings hardest when you can't answer.