Solutions
WhatsApp notifications for meal-plan customers
Email open rates in this market are poor and app notifications assume an app the customer installed. WhatsApp is where a message is genuinely read, which makes it the highest-leverage notification channel a Gulf meal business has.
The notifications that actually pay for themselves
Most notification projects start with marketing sends and get switched off within a quarter. The ones that survive are operational, because each prevents a specific piece of work rather than generating some.
The cut-off reminder is the clearest example. A customer with unselected meals two hours before the week freezes will either choose, or receive a default they did not pick and possibly complain about. A single message resolves that at essentially zero cost, and it removes both the default and the complaint.
Delivery confirmations are the second. A large share of "where is my food" contacts exist purely because nobody told the customer it arrived. A message at the point the driver closes the stop removes the question before it is asked.
What is worth sending
Cut-off approaching, meals unselected
Targeted only at customers with empty slots, which keeps volume low and relevance high.
Delivery confirmed
Triggered by the driver closing the stop, so it is true rather than scheduled.
Delivery failed
With what happens next, because silence after a failure is what turns it into a complaint.
Change applied
Confirming a pause or skip took effect. This closes the loop that otherwise produces a follow-up message asking whether it worked.
Term ending soon
Which is a renewal conversation rather than a notification, and works best when it does not read like marketing.
How it is wired, honestly
Messaging sits behind a provider interface in Mealroh, with a WhatsApp Business Cloud API adapter as the real implementation. Without credentials configured it falls back to deterministic mock behaviour, which means the system runs end to end in development without sending anything.
To send real messages you need your own WhatsApp Business account, a phone number, and approved message templates — that approval process is Meta’s, it takes time, and it is a genuine prerequisite rather than a detail. We do not resell or provision it for you.
Template approval also constrains what you can send. Operational notifications of the kinds listed above are the sort that get approved; broad promotional messaging is a different category with different rules.
Where a messaging channel stops being enough
Inbound free-form messages are ambiguous. "Skip next week" from a customer with three delivery days could mean several different things, and guessing produces a change they did not request — which is worse than asking.
The workable division is that unambiguous requests can be handled in the thread, and anything requiring interpretation gets a link to a screen showing exactly which days will change before confirming. That keeps the convenience without inventing intent on the customer’s behalf.
It is also worth being clear that this is not a shared team inbox. There is no ticket assignment, no SLA tracking and no conversation history management. If your support team needs those, keep your helpdesk.
Common questions
- Do I need my own WhatsApp Business account?
- Yes. You need a WhatsApp Business account, a phone number and Meta-approved message templates. That approval is Meta’s process and takes time; we do not resell or provision it on your behalf.
- Can customers pause their plan by replying?
- Only where the request is unambiguous enough to apply completely and audit. For anything requiring interpretation the better answer is a link to a screen showing exactly which days change, because a guessed change is worse than a question.
- What happens without WhatsApp credentials configured?
- The messaging provider falls back to deterministic mock behaviour, so the system runs end to end without sending anything. Nothing breaks; no messages leave.
- Is this a shared inbox for the support team?
- No. There is no ticket assignment, SLA tracking or conversation management. It sends operational notifications and handles simple structured actions; a helpdesk remains a separate tool.
See it running against a real kitchen
The product pages show the actual admin loaded with a demonstration kitchen — production, packing, routes and the dashboard, exactly as an operator sees them.
Related reading
- GuidesUsing WhatsApp as an operational channel, not an inboxIn much of the Gulf, a meal-plan business runs on WhatsApp whether or not it planned to. The question is not whether to use it but whether the messages arriving there turn into correct changes.
- SolutionsCustomer self-service for meal plansEvery routine change a customer cannot make themselves becomes a message someone has to read, interpret and apply correctly before a cut-off. That workload grows with your customer count, not with your feature list.
- GuidesSetting a meal delivery cut-off that actually holdsThe cut-off is the single most consequential number in a meal-plan operation. It is the line between a change that costs nothing and a change that costs food.
- SolutionsMeal delivery software for customer service teamsIn most meal-plan businesses the support queue is not complaints. It is amendments — pauses, skips, swaps, address changes — and the job is applying them correctly before a cut-off.