Read next
Slow-slot fill
What to actually offer in that Status, and why it should not be a discount.
Use Status for the same-day stuff and a broadcast for the rare, important thing. A Status is visible for twenty-four hours to every contact who has your number saved, needs nobody's permission and costs nothing — which makes it the right home for “two chairs free at three, walk in”. A broadcast lands in the chat, needs the person to have opted in, and should be uncommon enough that people still open it. Status daily. Broadcast monthly, at most.
Why Status is your best channel and the least used
The economics are unusual. Your audience is already assembled — it is everyone who saved your number, which is essentially everyone who ever booked. There is no algorithm deciding whether to show it. There is no cost per message. And the format is forgiving: a slightly crooked photograph of your actual reception desk outperforms a designed poster, because it reads as a person saying something rather than as an advertisement.
The catch is that it only works if it is habitual. A Status posted three times in a week and then not for a month gets skipped. Daily, or near enough, and people start checking it the way they check a shop's shutter.
What goes in a walk-in Status
Three elements, and nothing else:
- A photograph of the real thing. The empty chair. The new colour on today's client, with their permission. The specialist who has a gap. Not a stock image, not a graphic with a percentage on it.
- A legible time. “Free at 3 and 3:45 today.” Big enough to read at arm's length in sunlight. Specific times outperform “this afternoon” because they force a decision.
- One instruction. “Reply OK and I'll hold it.” One. Not a phone number and a link and a booking site.
The reply is the point, and it is why “reply OK” beats “call us”. When somebody replies to your Status it arrives as a normal chat, which is a conversation the person started — so you can answer freely, hold the slot, and confirm, without any of the template machinery that governs businesses messaging people out of the blue. Watch replies, not views. Views are vanity; a reply is a booking in progress.
The broadcast is a different instrument
A broadcast reaches a list you have built, in the chat window, whether or not anybody asked today. That is powerful and it is exactly why it needs to be rationed and why consent is not optional:
- Opt-in is a record, not an assumption. Somebody walking in once is not consent to be messaged. A tick box on the booking form, a “yes, message me about offers” on the lead page, or a reply to an explicit ask — with a date attached.
- Business messaging has rules. Outside a twenty-four hour window opened by the customer, a business message has to use a template the platform has approved. This is not our policy, it is WhatsApp's, and ignoring it is how numbers get restricted.
- Leaving has to be easy. One instruction, in the message, every time. A list people cannot leave stops being a list and becomes a complaint.
- Roughly monthly. Festival hours, a genuinely new service, the bridal package going live. If you cannot say why this had to interrupt someone, it is a Status.
Building the list without becoming the business that spams
The list that matters is small and specific. Ask at the counter, once, while the client is happy: “shall I message you when we have a slot in the afternoons?” That question gets a yes far more often than “can we add you to our offers list”, because it describes something the person actually wants.
Then record it. Which contact, which date, what they agreed to. Consent that lives in a receptionist's memory is not consent you can demonstrate, and the same record is what lets you stop messaging somebody the moment they ask. Contacts, permission, import and export come with the Launch plan and up, and offers go by email to people who said yes. The Status itself you post from your own WhatsApp; the WhatsApp page covers what the channel does specifically.
What the engine does here
The work it takes off you is the daily one: it drafts the line, sizes the image for Status, produces it in the language that client group actually reads, and puts it in front of you at the hour it should go out — so posting a Status becomes a ten-second approval rather than a thing you meant to do at eleven and remembered at four. Posting the Status itself happens from your own WhatsApp.
Where CoreLayerEngine fits
The engine drafts the offer in your voice, sizes the image, picks the hour from your own past results, holds it in an approval queue, and gives it a tracked link, so everyone who answers through it lands as a contact with a consent record.
Instagram, Facebook, LinkedIn, YouTube and Google Business Profile publish the moment you approve. Everything else arrives in your post kit finished — the image, the caption and the hour to post — one tap from your phone. The plan, the calendar, the lead page, the contact list and the reporting run either way.
This page is one of six moves. The pillar it belongs to — how an appointment business fills weekday afternoons — explains how they fit together, and links the other five.
