WhatsApp Business for play centres: ownership, templates, the 24-hour window and consent

Why does WhatsApp matter to a play centre?

In many of the markets play centres trade in, a parent asking about a party, checking whether socks are required or confirming a booking sends a WhatsApp message long before they open an email, and they expect an answer while the question is still warm. The venue that answers in five minutes gets the party. The venue whose phone is in somebody's pocket out on the floor gets the follow-up "never mind".

The same channel carries the messages a venue sends first: a reminder the day before a party, a note that a child's play time is nearly up, a welcome after a first visit, a birthday message, a request for feedback. Every one of those is easy to send badly. Sending them well is mostly a matter of owning the profile, respecting the platform's rules and respecting the parent.

Who should own the WhatsApp profile?

The venue. That sounds obvious, and it is the most common mistake in the industry. A profile created on a manager's personal number, or inside a software vendor's business account, belongs in practice to that person or that vendor: when they leave, the number, the conversation history and the approved templates leave with them, and a venue that has spent two years teaching families one number starts again.

Set it up so that it survives any change of people or software:

• A number the business controls. A SIM or virtual number in the company's name, paid from the company account, that no individual takes home in a pocket.
• A business portfolio the owner administers. The profile lives inside the platform's business manager, with the owner as an administrator and staff added as users at the access their job needs.
• Business verification in the venue's name. Verification, with the licence and the address, is what unlocks the display name and higher messaging limits. Do it once, properly, as the venue.
• Software gets access, not ownership. Any system that sends or reads messages for you connects to your profile with access you grant and can revoke on the day you change your mind.
• One profile per venue. A second site can be a second profile in the same portfolio, so each location's number, hours and templates are its own.

What is the 24-hour window?

One rule shapes everything else: after a customer sends you a message, you may reply with free-form typed text for 24 hours from their last message. That is the customer service window. Once it closes, you can reach that customer only with a message template approved in advance, until they write to you again and the window reopens.

In practice this splits your messages into two kinds:

• Replies inside the window. Anything the desk types in answer to a parent's question. No template, no approval, just a fast and accurate answer. The only discipline is speed: a question answered after the window has shut needs a template to reopen it, and "we are open until six" is not a template anybody has written.
• Messages you start. A party reminder, a timer reminder, a welcome, a birthday, a feedback request, a broadcast. The parent either did not message first or did so more than a day ago, so each of these has to be an approved template.

The practical consequence for a play centre is a staffing one. If the desk answers within the hour on weekdays, most conversations are handled as free-form replies and your template list stays short. If replies routinely wait until the next morning, you will find yourself writing templates for questions a person could have answered in ten seconds. Speed is cheaper than paperwork.

What is a message template, and how does approval work?

A template is a message written in advance, with placeholders for the parts that change — the child's name, the party date, the time slot — submitted to the platform and approved before it can be sent. Templates are sorted into categories; broadly, messages a customer expects because of something they did sit in one category, promotional messages in another, and the category affects both what the message may contain and, on some plans, what it costs. The current category rules live in the platform documentation linked above.

Approval is a review by the platform, not by any software vendor. It usually takes minutes to a day, and the common reasons for rejection are avoidable:

• A placeholder that could be filled with anything at all, leaving the reviewer to guess what the message will actually say.
• Promotional content submitted in a non-promotional category.
• Vague or misleading wording, a bare link with no context, or content that breaks the commerce policy.
• Formatting mistakes: placeholders out of sequence, a template that starts or ends with a placeholder, unsupported characters.

Write templates the way you would speak at the desk: who you are, why you are messaging, what the parent needs to know, and how to reply or stop hearing from you. Submit them under your own profile, in your own WhatsApp Manager, and keep a copy of the wording somewhere outside the platform, because the wording is one of the few assets in this channel that is genuinely yours.

Asking for consent, and honouring a request to stop

The platform requires that people agree to hear from a business before it messages them, and your privacy and marketing law says how that agreement must be gathered and recorded. The operational rule that satisfies both, in almost every venue, is short: ask on the way in, record it against the family, and let a request to stop win every time.

• Ask at the waiver and the booking form. Both are moments when the parent is already giving you their number. Add a plain-language question — "Yes, message me about offers and events" — left unticked and kept separate from the terms they have to accept.
• Separate expected messages from marketing. A reminder for the party a parent booked is something they are waiting for, and is usually treated differently from a promotion. A birthday offer is marketing. Send marketing only to families who said yes, and where a message sits on the line, treat it as marketing.
• Agree the replies that mean stop. Decide which words count — the obvious one, and its equivalents in the languages your families use — and make sure a matching reply removes the family from every journey and campaign, not only the one they replied to.
• Check the list before every send. The do-not-message check belongs on the server, ahead of every message, whichever feature is sending it, so a campaign built on Tuesday can never reach somebody who asked you to stop on Wednesday.
• Never buy or borrow a list. Numbers from a school, a mall or another venue never agreed to hear from you, and messaging them is the fastest route to a blocked number.

Which messages are worth sending, and what might they say?

The wording below is suggested starter text only. Copy it, rewrite it in your venue's voice, add your name and your placeholders, and submit it yourself. Nothing here has been approved for you, and approval is never guaranteed.

• Party reminder (the day before): "Hello, this is a reminder that the party for [child] is booked at [venue] on [date] at [time]. Please arrive fifteen minutes early so we can get everyone in socks and on the floor. Reply here if anything has changed."
• Timer reminder (a few minutes before time is up): "Hello from [venue]. [Child]'s play time ends at [time]. If you would like to add more, just ask at the desk."
• Welcome after a first visit (families who said yes to marketing): "Thank you for visiting [venue] today. We hope [child] had a great time. Our opening hours and price list are at [link]. Reply STOP and we will leave you be."
• Birthday message: "Happy birthday to [child] from everyone at [venue]. If you are planning a celebration, our party packages are at [link]. Reply STOP and we will leave you be."
• Feedback after a party or visit: "Thank you for choosing [venue] for [child]'s party. We would love to hear how it went: [link]. Reply STOP and we will leave you be."
• Pass ending soon: "Hello from [venue]. [Child]'s visit pass ends on [date] with [n] visits left. Renewing before then keeps the unused visits. Reply STOP and we will leave you be."
• Broadcast (rare — an off-peak offer, or a closure): "Hello from [venue]. We are closed on [date] for [reason] and open as usual from [date]. Reply STOP and we will leave you be."

Keep the list short. A venue that sends a reminder, a welcome, a birthday and a feedback request, and nothing else, is one families are glad to hear from. Every extra message you add is borrowed against that goodwill.

How do you keep the inbox answered?

A venue's WhatsApp goes unanswered for a structural reason rather than a rude one: the phone is in one pocket and that person is on the floor. So fix the structure.

• A shared inbox on every signed-in screen. The desk answers between customers, the office answers between bills, and nobody waits for the phone to come back from the ball pit.
• A status per conversation. Open, waiting on the parent, done. The team can see what still needs an answer without reading every thread.
• Quick replies. The ten answers you type most — hours, socks, prices, party menu, parking — dropped in with one tap and edited before sending.
• The family's record beside the conversation. Their waiver, their bookings, their pass and their marketing preference, so the answer is specific and the preference is visible before anyone types.
• An automatic first reply that only knows what you wrote. If you use an assistant for common questions, it should answer only from a knowledge base you maintain — hours, rules, prices, party terms — and hand over to a person the moment the answer is not in there, with every reply logged for you to read the next morning.

Turn automatic messages on one at a time. Send each to a staff phone first, check the placeholders filled correctly, then let it run for real and read the first day's log before adding the next one.

What should a play centre never do on WhatsApp?

• Run the venue on a staff member's personal number.
• Message a family that never agreed to hear from you, or keep messaging one that asked you to stop.
• Share numbers between venues, or import a list nobody agreed to be on.
• Let an automatic reply invent a price, a policy or a promise it was never given.
• Send a template that has not been approved, or keep sending one that was paused.
• Blast a broadcast to everybody at once on a new number. Daily messaging limits grow with a verified profile and good behaviour, and a burst on day one is how they shrink.
• Discuss an incident, a complaint about a child or a refund dispute in a marketing thread. Move it to a person and a phone call.

Get those right and WhatsApp becomes what it should be for a play centre: the fastest way to fill a Tuesday morning, and the reason a party enquiry at nine in the evening is still a booking on Saturday. The WhatsApp inbox and reminders page shows what running this on your own profile looks like day to day.