Solutions

Customer self-service for meal plans

Every 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.

The support burden is the scaling constraint

Cooking more portions is largely a labour and equipment problem, and it scales predictably. Reading and acting on messages does not: it grows with customers multiplied by how often they change something, and it lands on whoever is holding the phone.

That is why self-service is an operational feature rather than a customer-experience nicety. It removes work rather than redistributing it, which is the only kind of change that alters the slope.

What customers should be able to do without asking

  • Pause and resume

    Until a date or open-ended. The most requested action, and the one whose difficulty most directly causes cancellations.

  • Skip one delivery

    A lighter action than pausing, and the right answer for a single night away.

  • Pick their meals

    Up to the cut-off, with allergens and macros visible at the point of choosing.

  • Update address and access notes

    Cheap to record and expensive to miss, because a stale address costs a delivery and an interrupted kitchen.

  • See what is coming

    The upcoming schedule, which removes a large share of "when is my next delivery" messages.

Why an easy pause reduces churn

Some operators make pausing deliberately awkward, reasoning that friction protects revenue. In practice the customer’s alternative is not to keep paying — it is to cancel, because cancelling is always available and usually easier.

A paused customer keeps their plan, preferences, allergen record and delivery details, and resumes at no acquisition cost. That is a materially better outcome than a cancellation, and it is worth designing for deliberately.

Common questions

Does self-service mean losing control of the schedule?
No, because every customer action is still bounded by the cut-off. Before it the change is free; after it the system moves the request to the next open week rather than disturbing food already bought.
What should customers not be able to do themselves?
Anything the system cannot apply completely and audit. A partially-applied change is worse than a message, because it looks authoritative while being wrong.
Is a portal better than handling changes over WhatsApp?
They serve different moments. Messaging is excellent for notifications and simple unambiguous actions; a screen is better where the customer needs to see exactly which days a change will affect before confirming it.

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.