WhatsApp that the shop already has

Four steps Mesa already ships: pair the number, train from files or your site, go live, work the shared inbox.

1 · Pair

QR session or Cloud API

Connect the business number. No Tech Provider badge required to start on QR.

2 · Train

PDFs, price lists, shop URL

Knowledge base ingest — including Firecrawl “Add from URL”. The bot answers only from that store.

3 · Go live

Keywords, flows, AI, hours

Turn the chatbot on. Out-of-hours message covers nights. Handoff when a person must decide.

4 · Inbox

Team thread + CRM

Live Chat, notes, deals, orders, Status and campaigns sit on the same contact.

QR scan or Cloud API?

Both. Pair a number with a QR session, or connect WhatsApp Cloud API. Same inbox, bot and campaigns either way.

What happens when the bot should stop?

A transfer pauses AI for that contact until a human resumes it. CRM escalate writes the handover note and marks the conversation pending.

Mobile Money?

Staff confirm Airtel, MTN and Zamtel screenshots on the thread. Billing itself is Lipila in kwacha.

Status and the website?

Status posts from the dashboard. The website widget is one script — same bot and CRM as WhatsApp, not a second inbox product.

Instagram on Mesa is a product catalogue connect, not an Instagram inbox. Bookings are flows + a human — not Calendly.

WhatsApp us