Your customers already message you. MesaDash turns those conversations into real jobs priced from your own catalogue, scheduled to the right branch or chair, paid into your own account, and handed to a person the moment it stops being routine.
Tech ProviderEach thread stands on its own and remembers its own history: the branch they prefer, what they ordered last.
Show me
Coming soon
A product adds the catalogue, the scheduling rules and the hand-off policy for one trade. Everything below it is shared built once, and already running.
One shared inbox
Every channel arrives in one place your whole team can see. Assign a conversation, reply, hand it over the thread carries its own history with it.
Customer records
What they ordered last time, which branch they prefer, what they have spent with you. Remembered from the conversation itself, not typed in afterwards.
Your own payments
Paystack, Flutterwave, OPay, bank transfer, cash and Stripe. The money settles to you we never hold it and never take a percentage.
Branches and locations
Prices, availability and staff scoped per location, so a customer is always served by the branch that can actually deliver.
Team and roles
Invite staff and scope what each of them can see. Owner, admin, manager and floor staff each get their own view of the same business.
Many businesses, one login
Own or manage more than one business and switch between them without logging out. Each keeps its own channels, catalogue and team.
A model sits between the customer and your catalogue: narrow, checkable and stopped at the edges. It is the difference between a bot that helps and one you spend your evening apologising for.
It works from a fixed list
Each message is matched to a short list of things a customer can want: to book or order, check on it, cancel, ask a question or reach a person. When it is not sure, it takes no action.
It never claims it did something
It cannot confirm, charge or cancel on its own. It picks from what your catalogue offers at that step, and the same checks as every other booking or order do the rest.
It answers from your details, or asks
Prices, hours, locations and policies come from what you entered. When the answer is not there, it asks a short question instead of making one up.
It runs on an allowance
Each conversation and each month has a limit on how much the model is used. When it runs out, or you switch the assistant off, the regular replies and buttons keep working.
Restaurants get a menu with photos, a branch picker, a cart that survives a reload, and checkout. Salons and carwashes get a booking page where customers pick a service and a time, and pay. Put the link in your bio, on the flyer, in the chat. It is server-rendered, so Google indexes it and every chat app shows a proper preview.
Show me
Mama Ngozi’s Kitchen
Grilled chicken & jollof
Serves 1 · 20 min
Egusi & pounded yam
Serves 1 · 25 min
Goat meat pepper stew
Serves 1 · 25 min
One catalogue behind both
Change a price once. The page and the chat both follow, per branch.
One inbox behind both
An order from the page and an order from the chat arrive in the same place.
Your brand, your link
A page you own not a listing on someone else's marketplace.
No app to install
It opens in the browser they already have.
A delivery app keeps up to 30% of an order. A booking marketplace can keep 20% of a new client's first visit. A deal site keeps its share of every voucher. MesaDash takes none of it, and the payment settles into an account that is already yours.
30%
delivery app, top plan
20%
booking marketplace, first visit
0%
on MesaDash
Paid through your own provider, every time:
A generic bot can send a message. It cannot know that a meal deal has sizes and extras, that a deposit should be taken before a Saturday appointment is held, or that a full valet costs more on an SUV than on a hatchback. That knowledge is what a product is.
Coming soon
Each of these needs a catalogue shape, a scheduling rule and a hand-off policy from us, not a new platform.
One account, one inbox, one bill. Add a product to the same business when it ships.
No. They message you on WhatsApp, Instagram, Messenger or Telegram exactly as they do now, and the ordering or booking happens from there. The storefront opens in the browser they already have.
No. Payment goes through your own Paystack, Flutterwave, OPay or Stripe account, and cash and bank transfer are first-class options. MesaDash charges a flat subscription, never a share of what you sell.
In most cases, yes. We connect it through Meta's Tech Provider infrastructure. If the number is currently tied to the WhatsApp Business app we walk you through moving it across.
Beauty & Wellness. Salons, spas, barbershops, nail and lash studios, and therapists share staff calendars, service durations, deposits, rooms and equipment, and reminders that reduce no-shows.
It stops and hands the conversation to your team with the history and any order attached. It does not guess, and it does not loop. Anything that is not routine reaches a person.
Yes. Prices, availability, delivery zones and staff are scoped per branch, and an order routes to the branch that will actually fulfil it. One account can also hold more than one business.
No. Connect a channel, load your catalogue once, and open the inbox. There is no flow diagram to build and no webhooks to wire.
Connect your channels
Each connects its own way WhatsApp through Meta Tech Provider infrastructure, Instagram and Messenger through your Meta login, Telegram through a bot or a number. Connect one or connect all four; the accounts stay yours.
Load what you sell
Menu, services, or appointment types once. Branches, prices, availability, and delivery zones live in one place from then on.
Open the inbox
Orders and bookings start arriving with the customer, the payment, and the branch already attached.
