Restaurant AI assistant vs customer-facing agent

Who is the AI working for?

An in-house restaurant AI assistant works for the owner or operations team. Its starting point is the restaurant's records: a sales period, a branch's performance, or a complaint that needs attention. Bloub sits inside the Nexara dashboard and answers questions from the company's own numbers with citations.

A customer-facing agent works on the customer's behalf. The customer gives it an intention, such as finding dinner within a budget or ordering a particular meal for pickup. The agent needs menu items, prices, availability and a checkout it can finish.

What does Bloub read, and what can it do?

Bloub can compare periods, retrieve sales summaries and show channel breakdowns. It can examine cancellations, top products, customer mix and peak hours. A manager investigating weak service can start with a specific question and follow the cited records into the relevant report.

Its view also includes inventory alerts, menu item status, printer status, open complaints and workflow tasks. It can generate reports and feedback reports, open a dashboard page, prefill a form and create a workflow task.

Overnight, Bloub checks six patterns: demand shift, item trend, basket anchor, regulars gone, price change attach drop and operations friction. Its morning brief gives the owner a starting point for checking what changed.

Bloub does not independently change menu prices or issue refunds. Those decisions stay with the responsible person. The Bloub restaurant AI assistant overview explains its role inside the dashboard.

How does an agent place a customer's order?

Agent ordering is built into every Nexara restaurant storefront for agents that speak ACP (2026-04-17), UCP or MCP. A compatible agent can read the menu, obtain a delivery quote and complete an order through the storefront.

1. Read the live menu. The agent gets items, prices, availability and available options.
2. Get a server-priced delivery quote. Nexara calculates the total from the menu, selected options and delivery zone. The agent cannot choose its own price.
3. Verify the customer. Anonymous agents verify the customer's Jordanian phone by SMS code. Trusted platforms that have verified their buyer complete with a key.
4. Place the order. The customer pays cash on delivery, or pays at the counter for pickup.
5. Send it into service. The order enters the kitchen queue, prints in the kitchen and appears on the order board with an AI agent badge.
6. Track the order. A tracking permalink supports follow-up. Platforms that registered for updates can receive signed order_create and order_update webhooks.

The Nexara agent ordering page describes this storefront capability. Discovery and selection inside an assistant follow that platform's own decisions.

Where do Bloub and customer agents meet?

They use the same menu and operating records. Nexara supports product options, channel menus and availability by branch. A customer agent reads the storefront's live menu, while Bloub can retrieve menu item status inside the dashboard.

Nexara brings phone, website, app, table QR, Talabat and Careem orders into one branch queue. An agent order enters that queue and carries an AI agent badge on the board. Kitchen tickets can print in Arabic and include English on the same ticket.

Every order attaches to a customer record the restaurant owns, with addresses and order history. Agent orders count like website orders. Bloub can retrieve order details and sales summaries from company records. The Nexara features overview covers the menu, customer records and printing.

What should a restaurant prepare for customer agents?

An agent needs a clear restaurant identity, menu items it can identify, and a checkout it can finish. Nexara storefronts include structured Restaurant, Menu and MenuItem information with availability. Keep the same restaurant name, location, hours and service facts across every listing.

• Write one clear entity sentence stating the restaurant's name, cuisine, location and whether it offers delivery or pickup.
• Keep the Google Business Profile consistent with the storefront, especially the restaurant name, address and opening hours.
• Maintain item names, prices, required options and branch availability so the menu supports an actual purchase decision.
• Keep reviews and customer feedback under regular review, and publish a phone number that someone answers.

A menu photograph may help a person recognise a dish. Separate item names, prices and choices give an agent the information needed to order. Nexara supplies that menu form. The restaurant supplies the correct contents.

How should an owner evaluate both kinds of AI?

For Bloub, choose a question with a defined period and branch, then inspect the citations and relevant report. If follow-up is needed, create a NexaraFlow workflow task. During the evaluation, remember that NexaraFlow workflows are a Pro-plan feature.

For customer ordering, walk through menu selection, the delivery quote and phone verification. Check the completed order on the board and the printed ticket. Include a required modifier so you can confirm that the kitchen receives the customer's actual choice.

Nexara has a free plan plus paid plans per branch in JOD, with current rates on request. Free and Starter include 0 printers, Growth includes 1 printer, and Pro includes unlimited printers. The call center is a Pro-plan feature.

Message Issa Al-Dalu, Nexara's founder, through the WhatsApp button at nexaratech.io. Bring one question you want Bloub to answer and one customer order you want to walk through. You can also review the Nexara FAQ or Issa Al-Dalu's founder page before the conversation.