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 operations dashboard — without your customers needing to download anything new.

Think of it as the layer between your kitchen and your customers: taking orders, routing them to the right screen, managing walk-in queues, sending receipts, and keeping service moving without extra apps for guests.

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. We offer a trial period and a guided onboarding call where we walk through the owner and manager dashboards on your floor. Book a call to get started.

Already a customer and need help? Message +91 95009 96033 on WhatsApp — you'll see our technical support workflow there.

A stable Wi-Fi or 4G connection is sufficient for each device. The kitchen display, manager board, and owner dashboard are all browser-based — they work on any phone, tablet, or laptop without installing an app. For the kitchen display, a tablet on Wi-Fi mounted near the pass is the most common setup. We recommend reliable connectivity in the dining area and kitchen so orders and status updates are not delayed.

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 day-to-day restaurant operations. If you already use a POS for billing, GST, inventory, or aggregator (delivery platform) integration, Munafe works alongside it — it adds the WhatsApp ordering channel and customer conversation layer that most 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 core 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. scheduled campaigns, reservation reminders, feedback invites).

Order confirmations, cart replies, and other messages inside an active customer chat are session messages — they don't need a pre-approved template because the customer initiated the conversation.

Beyond submitting templates to Meta, Munafe also:

• Drafts and stores template copy (including AI-assisted rewrites) before submission
• Tracks approval status and surfaces rejected templates with reasons
• Maps approved templates to scheduled broadcasts and automations
• Enforces opt-in rules so marketing sends stay within Meta policy

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 Manager Portal — availability changes sync to the WhatsApp catalog when items are linked. Managers can also mark special dishes of the day (shown as a friendly suggestion in chat, not in the catalog). Time-slot filtering automatically shows or hides items by hour (e.g. idli only during morning tiffin).

There is one menu per outlet — not separate dine-in, takeaway, and delivery menus. You control which services are active (dine-in, takeaway, delivery, reserve-a-table) independently. Time-slot filtering shows or hides items by hour, and managers can mark today's specials. Full per-service menu splits (different items per channel) are 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 WhatsApp orders, Munafe uses Razorpay for in-chat payment. Customers receive a payment link after confirming their cart; once payment succeeds, the order is released to the kitchen (KDS) and the customer gets confirmation and a digital receipt.

Restaurants can configure payment behaviour — including prepay before kitchen release. Table reservations can also collect an advance via Razorpay; the advance is applied as credit on the final dine-in bill.

Cash or UPI at the counter remains an option where you configure post-pay or counter settlement for specific flows.

If a customer messages about a complaint or order change mid-chat, Munafe's intent detection flags it and sends a WhatsApp alert to your manager so staff can respond quickly.

Munafe does not automatically cancel confirmed orders in chat. Changes after confirmation are handled manually by your manager from the dashboard or in person — for example adjusting items, voiding a line, or handling a genuine service issue on the floor.

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. Orders appear the instant a customer confirms — no manual entry, no verbal relay from waiter to cashier to kitchen.

Each order shows the table number or token, items, special notes, and how long it's been waiting. 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.

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. Nothing leaves half-packed.

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 / takeaway)
• Customer complaint or change request flagged in chat
• Post-visit feedback rated 1–2 stars (poor)

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 (which staff can use to manually create tokens) 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 ordering from WhatsApp will see the updated table list within 5 minutes.

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.

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 (WhatsApp Business Account). 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. There's no confusion, no manual routing, no shared inbox bottleneck.

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. No fixed outlet.
• Outlet-level roles (Owner, Manager, Kitchen, Captain, Waiter) — scoped to their specific outlet. They only see their own data.

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. The exact per-conversation cost depends on the conversation category (service vs. marketing) and country. 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.

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 (GB WhatsApp, WhatsApp Plus) that aren't Meta-approved. These are the single biggest cause of restaurant bans in India.
• Sending unsolicited marketing. Blasting promotions ("Happy Hour tonight!") 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. Meta's system interprets this as spam-like behaviour.
• Sending marketing after a greeting. Automatically replying to a customer's "Hi" with a menu, price list, images, or offers is classified as unsolicited marketing — even though it feels like customer service.
• 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 to avoid the marketing rate.

Yes — significantly. Unofficial automation tools (tools not built on Meta's official Business API) 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.

Many restaurant owners who come to Munafe are switching from unofficial bots after their number was restricted. Recovering a banned number requires a formal Meta appeal process that can take weeks and sometimes fails permanently.

Act in this order:

• 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. For partial blocks (1–3 days), the restriction may simply expire — appealing is optional but recommended.
• 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. This is why avoiding restrictions in the first place is critical for restaurants that rely on WhatsApp ordering during service.

Several layers of protection are built in:

• 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 and won't push your account over them.
• Conversation-first design — ordering is triggered by the customer messaging you, not by you pushing messages at them. Customer-initiated conversations carry much lower ban risk than business-initiated ones.
• Quality score monitoring — if your account's quality score drops (due to block/report rates), 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 (fraud, scams, illegal content). 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

Standard restaurant operations — ordering, reservations, marketing — carry none of these risks. These scenarios are listed for completeness; they don't apply to legitimate restaurant use.