WhatsApp campaigns for your restaurant’s guests
The 4Labs PRO CRM organizes the guest book populated by reservations and bills. Prepare WhatsApp campaigns for groups of consenting guests, with a preview and opt-out checks before sending.
The three questions a campaign decides
Who: drawn from what the guest actually did
The audience is built from the address book that reservations and floor checks fill, filtered on what really happened: who hasn't come in a month, who's a club member, who carries a given tag. Before anything goes out you see the exact count and the first names on the list.
- The preview is mandatory: there is no send button until you've seen it.
- The number shown is the number sent, because the same query computes both.
- Anyone without a phone or who opted out is excluded always, whatever the filter says.
How it goes out: in batches, without repeats, without burning the number
The list is frozen the moment you send, so nobody enters or leaves the campaign halfway through. Messages go out spaced on purpose: the same number confirms the restaurant's reservations, and three hundred identical messages in a minute is exactly the pattern that gets it blocked.
- A recipient cannot get the same campaign twice. The database guarantees it, not luck.
- If the send is cut off halfway, it picks up on its own where it left.
- Cancelling stops what's left; what already went out stays on record as it went.
Who's left out: opt-outs enforce themselves
Whoever asks not to be written to is opted out by phone number, not by record. That's the difference that matters: a record gets deleted and recreated with the next reservation; the number doesn't. And the opt-out is checked again at the moment each message goes out, not just when the list is built.
- A guest can reply «SALIR» and is opted out without anyone writing it down.
- Whoever asks by phone or on the floor is registered from that same screen.
- Anything that looks like an opt-out without being one goes to a queue for a person to read.
What's included, at no extra charge
Mandatory preview
A menu copied too widely gets deleted. A message sent to the wrong list can't be pulled back.
No double sends
The database prevents one number from receiving the same campaign twice, even if the send is retried.
Careful pacing
Messages go out spaced so they don't trip the spam filters on the number that also confirms reservations.
Sent campaigns aren't editable
They stand as the record of what was sent to whom and when. Cancelling doesn't erase what already left.
A queue for the ambiguous
«I want off the list» doesn't match the keyword exactly. Rather than guess, someone reviews it.
The address book fills itself
Every reservation leaves a record. No contact list to upload before you can start.
It doesn't crowd out operations
Reservation confirmations and campaigns have separate budgets: one can't leave the other without a message.
Only management sends
Writing to three hundred people on the restaurant's behalf is not a floor-level action.
Frequently asked questions.
What number do the messages come from?+
The WhatsApp number the restaurant already uses to confirm reservations. That's why the send rate is deliberately limited: going slower costs nothing, and losing that number cuts the whole channel.
Is there a message cap?+
There's a per-recipient limit so nobody gets an avalanche, and that budget is separate from operational notifications: a campaign can't leave a guest without their reservation confirmation.
Who can send a campaign?+
Management or the owner. Registering an opt-out, on the other hand, anyone on the team can do: whoever hears «stop writing to me» is usually whoever answers the phone.
Can the message be personalized?+
Yes, with the guest's name and the location's details. The sign-off with the opt-out instruction is appended by the system, always, and can't be removed from the template.
