Munafe is a WhatsApp-first restaurant management platform. It turns your existing WhatsApp Business number into a complete ordering system, kitchen display, table management board, and customer outreach tool — without your customers needing to download anything new.

Think of it as the layer that sits between your kitchen and your customers, handling everything that usually falls on your staff: taking orders, routing them to the right screen, managing walk-in queues, tracking who your regulars are, and sending re-engagement messages on a schedule.

No. Customers order, book, and get updates entirely through WhatsApp — an app they're already using. There's no QR code to scan to a website, no login to create, no new app to install.

They message your restaurant's WhatsApp number, browse the menu using native WhatsApp interactive buttons and catalog, add items, and confirm. That's it.

Setup has three parts:

• WhatsApp Business API — connecting your phone number through Meta's official API (typically 24–48 hours for Meta's review).
• Menu upload — either via Excel/CSV or by syncing directly from your existing Meta catalog. Takes an hour or less.
• Staff onboarding — adding your manager, kitchen, and captain accounts from the Settings panel. Each gets login credentials and a WhatsApp invite. Under 30 minutes.

Most restaurants are live within 2–3 business days of signing up. We guide you through the full process.

Yes — but it doesn't have to be a new SIM. Munafe runs on the WhatsApp Business API, which requires the number to be migrated from the standard WhatsApp or WhatsApp Business app to the API.

Once migrated, the number can't be used on the regular WhatsApp app on a phone, but it works fully on Munafe's platform. Many restaurants use a dedicated landline or a second SIM for this purpose. We walk you through the migration.

Yes. Message +91 9500996033 on WhatsApp to experience the live demo — you'll go through a real ordering flow as a customer so you see exactly what your guests see. We also offer a guided onboarding call where we walk through the owner and manager dashboards screen by screen.

A stable Wi-Fi or 4G connection is sufficient. The kitchen display, manager board, and owner dashboard are all browser-based — they work on any device (phone, tablet, laptop) without installing an app. For the kitchen display specifically, a tablet with Wi-Fi mounted near the pass is the most common setup.

Munafe is intentionally hardware-light:

• Kitchen Display (KDS) — any Android or iOS tablet, or a cheap laptop. A ₹6,000–8,000 Android tablet works well.
• Manager board — any smartphone or tablet already in use at your front desk.
• Receipts — sent digitally to customers via WhatsApp. No thermal printer required for customer copies (though you can still use one for KOTs).
• Takeaway QR scanning — the captain uses the same browser on their phone to scan customer QR codes.

No proprietary terminals, no locked-down tablets, no vendor-supplied hardware needed.

Munafe handles WhatsApp ordering, kitchen display, table management, and customer outreach. If you already use a POS like Petpooja for billing, GST, inventory, or Zomato/Swiggy aggregator integration, Munafe works alongside it — it adds the WhatsApp ordering channel and customer layer that POS systems don't cover.

For restaurants that don't have a POS, Munafe's built-in KDS, KOT printing, and GST invoice generation cover the day-to-day operational needs without a separate system.

The WhatsApp Business app is the free mobile app used by small businesses. It has no automation, no multi-agent support, and a daily broadcast limit of about 256 contacts. It's fine for manual messaging but can't power an ordering system.

The WhatsApp Business API is Meta's official platform for businesses that need automation, multi-agent inboxes, chatbots, and broadcast to large audiences. It's accessed through Meta-approved platforms like Munafe — not directly by the business. Munafe is built entirely on the official API.

Yes. Munafe operates through Meta's official WhatsApp Business Platform. Your WABA (WhatsApp Business Account) is registered under your own Meta Business Manager — Munafe doesn't hold or own your account. You own your number, your data, and your WABA.

Not immediately. You can start with an unverified WABA and run the ordering flow, KDS, and table management from day one. However, Meta verification unlocks:

• Higher messaging tiers (start at 1,000 conversations/day; scales to unlimited)
• Your verified business name showing next to your number
• Eligibility for the green tick (Official Business Account)

We recommend completing verification within the first two weeks. It requires submitting your GSTIN, business registration documents, or utility bill. Typically approved within 2–5 business days.

Meta uses a tiered system based on account quality and volume. New accounts start at 1,000 conversations per day. If you consistently send high-quality messages (low block/report rate), Meta automatically moves you up:

• Tier 1: 1,000 conversations/day
• Tier 2: 10,000 conversations/day
• Tier 3: 100,000 conversations/day
• Tier 4: Unlimited

For most restaurants, even busy ones, 1,000 conversations/day is more than enough. A conversation is a 24-hour window, not a single message. One customer ordering and confirming is one conversation — not 10 messages.

Yes. One WABA can have multiple phone numbers — one per outlet. Each outlet gets its own WhatsApp number and appears as a separate contact to customers. The routing happens automatically: a customer messaging your T. Nagar number gets T. Nagar's menu; a customer messaging your Anna Nagar number gets Anna Nagar's menu.

From the owner side, a single brand dashboard shows aggregate revenue, orders, and customer segments across all outlets.

Meta requires approval for outbound marketing templates — messages your restaurant sends to customers who haven't messaged you in the last 24 hours (e.g. "Missed you" campaigns, reservation reminders, feedback requests).

Munafe manages template submission and approval on your behalf. The templates used for order confirmations, KDS notifications, and within-session conversations are session messages — they don't require pre-approval because the customer initiated the conversation.

Template approval from Meta typically takes 2–24 hours.

Yes, with one important note: migrating a number from the WhatsApp Business app to the API will delete your existing chat history on that number (because the API doesn't store chats locally). The number itself is preserved — customers can still message the same number.

If you have important chat history you want to keep, export it before migration. If you prefer to keep the app number for your personal use, using a second number for Munafe is the cleaner path.

Three ways:

• Excel/CSV upload — download our template, fill in item names, prices, categories, and photos, upload. Done in under an hour.
• Meta Catalog sync — if you already have a product catalog in Meta Business Manager (common if you run Facebook/Instagram ads), Munafe can pull it directly.
• Manual entry — add items one by one from the dashboard for smaller menus.

You can toggle items in/out of stock in real time from the dashboard — changes reflect for customers within seconds. The catalog also supports time-slot availability (e.g. Idly only visible during morning tiffin hours).

You can control which services are active (dine-in, takeaway, delivery, reserve-a-table) independently. Time-slot filtering automatically shows or hides items based on the hour — so your dinner menu doesn't appear at 8 AM. Full per-service menu configuration is on the roadmap.

• Dine-in — customer messages from the table, orders go to KDS
• Takeaway — customer orders remotely, picks up with QR token
• Delivery — customer shares live location in chat, rider assigned by manager
• Reserve a table — advance booking with date/time picker inside WhatsApp, optional prepayment
• Walk-in — staff creates a token at the desk for customers who arrive in person

For immediate dine-in and walk-in takeaway, Munafe uses a pay-at-counter model — the order is confirmed via WhatsApp and payment happens when the customer collects or at the end of the meal using your existing cash/UPI/card setup.

For scheduled takeaway and scheduled delivery, customers pay upfront via a Razorpay link in WhatsApp after the manager approves the order. The booking is confirmed only after payment succeeds.

For table reservations, an advance payment can be collected to secure the booking. The advance is automatically applied as a credit against the final dine-in bill.

If a customer messages about a modification, cancellation, or complaint mid-chat, Munafe's intent detection flags it immediately and sends a WhatsApp alert to your manager — so they can act before the customer leaves or writes a review.

Order modifications at the POS level (after confirmation) are handled manually by the manager from the dashboard.

Yes. Every confirmed order generates a branded digital receipt — a PNG image with your restaurant name, itemised bill, GST breakdown, and a QR code. It's sent automatically to the customer's WhatsApp chat and stored for 48 hours at a unique URL. No thermal printer required on the customer side.

For kitchen use, a KOT (Kitchen Order Ticket) is generated for each order and can be printed on a connected receipt printer.

The KDS is a browser-based screen that kitchen staff open on any tablet or laptop at app.autom8.works/dashboard/kitchen. It has three tabs:

• Live orders — immediate dine-in, walk-in takeaway, and orders whose kitchen start time has arrived
• Future — prepaid scheduled takeaway and delivery with a pickup/delivery slot more than an hour away
• History — completed orders from the current service day

Each order shows the token, items, special notes, and wait time. Kitchen staff tap to mark items in-progress or ready. When an order is ready, the manager gets a WhatsApp ping and the customer receives a "your order is ready" message.

When a customer books a future slot via WhatsApp and pays after manager approval, the order lands in the KDS Future tab with two times:

• Start time — when the kitchen should begin cooking (computed from cook time, packing, and a safety buffer)
• Slot time — when the customer expects pickup or delivery

For delivery, the start time is earlier than takeaway for the same slot because transit time to the customer is included. When the start time arrives, the order moves to Live automatically.

Yes — this is called multi-counter mode. If your kitchen has separate stations (e.g. Sweets counter, Hot food counter, Beverages), each section can fulfil its part of an order independently. The captain scans the customer's QR code at each counter; the order is only marked complete when all sections have scanned their part.

When a takeaway order is confirmed, the customer receives a QR token in their WhatsApp chat. When they arrive to collect, the captain or staff scans the QR code from Munafe's Captain Portal on any smartphone. The system verifies the order, marks it collected, and prevents duplicate collection.

If the same QR is scanned twice, the system shows a warning with the time and name of the first collection — preventing fraud.

Your manager receives WhatsApp notifications for:

• New walk-in customer arrived (with token number and link to manager portal)
• Large party request — needs approval before confirming
• Order ready for service (dine-in)
• New complaint or cancellation request from a customer
• Post-visit feedback rated 1–2 stars (poor)
• Nightly summary — covers, revenue, cancellations

You can configure which roles receive which notifications from Settings → WhatsApp.

Orders already received will remain visible in the KDS. New WhatsApp orders from customers won't come through until connectivity is restored. The manager's walk-in form works on cached state briefly, but full functionality requires a connection.

For high-traffic environments, we recommend keeping a mobile data hotspot as backup. Most restaurant-grade broadband comes with failover — check with your ISP.

From Settings → Tables, add tables individually or use bulk-add (e.g. "add 10 tables starting from Table 1, 4-seater"). Each table has a number, section, and capacity. Changes take effect immediately.

Customers type "Reserve a table" or tap the Reservation option. Munafe launches a native WhatsApp Flow — a structured form inside the chat where they pick a date, time, and party size without leaving WhatsApp. They can also pay an advance to confirm the booking.

24 hours and 1 hour before the booking, Munafe sends automatic reminder messages to reduce no-shows. If a booking doesn't show up, the table is released automatically after the grace period — no manual check required.

Munafe detects reservations that haven't been seated past the booking time and releases the table automatically. The manager also gets a WhatsApp alert. For customers who repeatedly no-show, you can track their history in the customer profile — and the advance payment feature ensures there's some accountability built in from the start.

When a customer requests a table for a party above your configured threshold, Munafe routes the request to the manager on WhatsApp with the party details and a proposed table combination. The manager approves or rejects with one tap. The customer is notified immediately on WhatsApp — no phone call needed.

Yes. After a reservation is confirmed, Munafe sends a menu prompt to the customer via WhatsApp so they can pre-order. Any advance payment they made is automatically applied as a credit to their food bill when they dine. This reduces wait time on arrival and improves kitchen prep.

Every customer who orders through Munafe is automatically profiled by their WhatsApp number. Munafe tracks visit frequency, recency, average spend, preferred service type, and favourite items — with no manual data entry required.

Customers are then automatically assigned to one of five RFM segments: Champion, Loyal, Promising, At-Risk, or Lost — updated after each visit.

From the Marketing dashboard, describe your goal in plain English — for example: "Send a weekend offer to customers who haven't visited in 3 weeks." Munafe identifies the right audience (your At-Risk segment), drafts the WhatsApp message, and shows you a preview before sending. You approve and send — no template writing, no segmentation spreadsheets.

Yes — this is a Meta policy requirement, not just ours. You can only send marketing messages to customers who have explicitly opted in. Customers who have ordered via your WhatsApp number are considered opted in for transactional communications — but for pure marketing messages, explicit opt-in is required.

Munafe tracks opt-in status per customer and will not send campaign messages to opted-out contacts. Violating this rule is one of the fastest ways to get your WABA restricted.

Two hours after a customer's visit is marked complete, Munafe sends a brief rating request to their WhatsApp: a star rating from 1 to 5. If they rate 4 or 5, the conversation closes. If they rate 1 or 2, your manager gets an immediate WhatsApp alert so the issue can be addressed the same evening — before it becomes a public review.

All feedback is logged in the dashboard for trend tracking.

After a successful order, Munafe prompts customers to share a personal referral code with friends. When a new customer places their first order using that code, they get a discount automatically applied, and the referring customer earns a reward credit. The entire loop runs over WhatsApp — no app, no QR scavenger hunt, no manual tracking by staff.

Customers classified as At-Risk or Lost (haven't ordered in 14+ days) automatically receive a personalised re-engagement message on a schedule. The message uses their name, mentions their last order, and includes an offer or prompt to return — sent on auto-pilot without any staff involvement.

Yes. Munafe supports chain restaurant setups with a Brand Owner login that shows aggregate KPIs across all outlets — total revenue, top outlet, top-selling item chain-wide, and at-risk customer count. You can drill into any outlet's full dashboard from a single view.

Each outlet gets its own WhatsApp number, menu, staff, and settings. The brand owner can push a master menu to all outlets at once, with each outlet able to override individual items locally.

Each outlet has its own phone number registered under your shared WABA. Customers message their nearest outlet's number — routing is automatic. A customer in T. Nagar messages the T. Nagar number and sees T. Nagar's menu; Anna Nagar customers message a different number.

Yes. From the Brand Dashboard, you can send a broadcast campaign to customers across all outlets or a selected subset. Segment by customer type (all customers, champions, at-risk) and choose which outlets are included. Each campaign is dispatched through the respective outlet's WhatsApp number — so the message appears to come from the outlet the customer knows.

There are two staff scopes in chain mode:

• Brand-level roles (Brand Owner, Brand Manager) — can see all outlets, aggregate reports, and manage chain-wide settings.
• Outlet-level roles (Owner, Manager, Kitchen, Captain, Waiter, Marketing) — scoped to their specific outlet only.

Each staff member logs into the same dashboard URL — the view they see is determined entirely by their role.

Munafe is a monthly SaaS subscription. Pricing is based on the number of active outlets and the features enabled. We offer a trial period for new restaurants so you can validate the system on your floor before committing. Contact us for current pricing — we'll share a detailed breakdown based on your restaurant type and size.

Meta charges separately for WhatsApp Business API conversations beyond the free tier (currently 1,000 free service conversations per month per WABA). Munafe passes these through at Meta's published rates — we don't add a markup on Meta's API charges. Current rates are published at Meta's pricing page.

For most restaurants in India, the WhatsApp API cost for operational ordering conversations is minimal — customer-initiated service conversations are free within the 24-hour session window.

You own your data — your customer list, order history, and menu. Munafe holds it on your behalf under the terms of our Data Processing Addendum (DPA). You can request a full data export at any time. If you leave Munafe, your data is returned to you and deleted from our systems per our DPA terms.

Your WABA, WhatsApp number, and Meta Business Manager account remain yours — Munafe doesn't hold or control them.

Monthly plans have no lock-in — cancel anytime. Annual plans are billed upfront at a discount. There's no exit fee. If you cancel, your account remains active until the end of the paid period.

Munafe Supply is a separate product line for supplier → restaurant trade. Your restaurant clients message your supplier WhatsApp number to get an order form link, check outstanding balance, track deliveries, and log offline payments (UPI, cash, bank transfer). Munafe does not process supplier payments — your team confirms them in the dashboard.

Clients reply 1 or Place order on WhatsApp. The bot sends a signed link to a web form with their personalised prices pre-loaded. They enter quantities only — no typing item names in chat. After submit, the order is recorded and their credit ledger is updated.

Ordering is typically open daily from 6 PM until your configured cutoff (e.g. 10 PM IST), unless you enable always open for a client or supplier.

Each client has a credit limit. Outstanding balance increases when orders are placed and decreases when you confirm a payment in the dashboard. If utilisation reaches 100% and auto-block is on, new orders are paused until payment is recorded. Clients can reply 4 — I've paid to log a payment claim for your team to verify.

At app.autom8.works/dashboard/supply (supplier owner login). Add clients (WhatsApp number must match), catalog items, and optional per-client price overrides. Pending payment claims and recent orders appear in the same dashboard.

No. Restaurant Munafe is for diners ordering from a restaurant (menu, cart, KDS, tables). Munafe Supply is for restaurants ordering from their supplier. They use different WhatsApp numbers, database tables, and agent logic. A supplier can use Munafe Supply while their restaurant clients use Munafe for their own customers.

1. Run the Supabase migration (add_supply_b2b.sql)
2. Create a supplier record with your WhatsApp Business phone_number_id
3. Register each restaurant client's WhatsApp number
4. Upload your catalog and any client-specific rates
5. Deploy the feature/munafe-supply branch on API, chat, and frontend

Contact Autom8 Works for onboarding assistance.

Meta uses a progressive enforcement ladder — it doesn't jump straight to a permanent ban:

Each stage (except immediate ban for severe violations) follows a warning. The key is acting on warnings immediately — Meta gives you visibility into active restrictions in your Meta Business Suite → Business Support Home.

For restaurants specifically, the most common violations are:

• Using unofficial automation tools. Third-party WhatsApp bots, bulk-message apps, or "WhatsApp mod" software that aren't Meta-approved. These are the single biggest cause of restaurant bans in India.
• Sending unsolicited marketing. Blasting promotions to customers who didn't opt in — even if they're your own regulars.
• High block/report rate. If recipients frequently tap "Report" or "Block" on your messages, your account's quality score drops.
• Sending marketing after a greeting. Automatically replying to a customer's "Hi" with a menu, price list, or offers is classified as unsolicited marketing.
• Too many messages in rapid sequence. Sending 3–4 messages back-to-back immediately after a customer initiates a chat flags the automation pattern.
• Template misclassification. Sending promotional content through a "transactional" or "utility" template category.

Yes — significantly. Unofficial automation tools bypass Meta's rate limits and consent systems. WhatsApp detects these tools through behavioural signals — message cadence, API fingerprints, and header patterns — and typically bans the number within days to weeks of detection.

• Don't panic or change settings randomly — acting too quickly can worsen the situation.
• Log in to Meta Business Suite → Business Support Home → look for active restrictions and the exact policy cited.
• Read the specific policy you violated. Meta cites the exact rule.
• Click "Request Review" to submit an appeal.
• While appealing, stop sending the type of message that triggered the restriction. Continuing the same behaviour during an appeal almost always results in escalation.
• Document your correction steps in the appeal — Meta expects you to demonstrate you understand the violation and how you're fixing it.

Most first-time restrictions (warnings, partial blocks) are resolved within 1–7 days if addressed correctly.

During a full block, no WhatsApp messages can be sent or received on that number. Customers who message your restaurant will see the message stuck on "one tick" (not delivered). Orders placed via WhatsApp will not come through.

Munafe's manager portal and KDS continue to work — existing confirmed orders are still visible. But no new WhatsApp-originated orders will arrive until the block is lifted.

• Official API only — no unofficial automation, no policy bypass.
• Opt-in enforcement — Munafe will not send marketing campaigns to customers who haven't opted in.
• Approved templates — all outbound marketing messages go through Meta's template approval process before sending.
• Rate-limit compliance — Munafe respects Meta's messaging tier limits.
• Conversation-first design — ordering is triggered by the customer messaging you, not by you pushing messages at them.
• Quality score monitoring — if your account's quality score drops, we alert you before it becomes a restriction.

For the Disabled stage (the final level), yes — the WABA is permanently removed from the WhatsApp Business Platform and cannot be recovered. The underlying phone number itself is not affected (it's still a working SIM), but it can no longer be used on WhatsApp Business API.

This level is reserved for repeated violations after multiple warnings, or for immediate severe violations. For a restaurant following normal operating practices on the official API, reaching this stage would require ignoring multiple escalating warnings over weeks or months.

Meta bypasses the progressive ladder and immediately disables accounts that violate its most serious policies. For restaurants, the scenarios that could theoretically apply are:

• Facilitating fraud or financial scams through the business number
• Selling controlled substances, alcohol to minors, or prohibited goods
• Coordinated inauthentic behaviour (fake reviews, fake order volume)
• Account used for phishing, impersonating another business, or deceptive practices