Skip to main content

Requests: orders

Orders from your restaurant, cloud-kitchen or events bot, or added by hand: confirm, prepare, send out or hand over, mark done, and track the payment.

Open Requests → Orders (/app/requests/orders). The list shows Still to do (every order not yet done or cancelled), newest first. Pick All statuses or one status in the menu, or search by order number (1042 or #1042), name or items.

Each row: the order number (#1042), the items, the customer, Delivery or Pickup, when it came in, the total with its currency, the payment badge and the status.

Work an order

  1. Press the order.
  2. Leave Tell the customer on to message them in their language at each step.
  3. Press the next step:
  • Confirm order → Confirmed
  • Start preparing → Preparing
  • Out for delivery (delivery orders) or Ready for pickup (pickup orders)
  • Mark done → Done
  1. Cancel order asks for an optional reason (the customer reads it) — press Cancel it. A cancelled order can be put back with Reopen as new. A done order cannot change any more.

Payment links

OmniBrand never takes payments in the chat. Use your own payment page:

  1. In the drawer's Payment box, paste the link in Payment link.
  2. Press Mark link sent. With Tell the customer on, the customer gets "You can pay for order #… here: …".
  3. When the money has arrived, press Mark paid. The order shows Paid.

The Payment box is not shown on a cancelled order. On a done order only Mark paid is left. Once an order is paid, the box says "This order is paid. There is nothing more to do here." and offers no buttons.

What the bot collects

An Order step saves what the customer ordered in their words (or item by item with quantities and prices), delivery or pickup, the address or shared location (Open in maps), notes and the total. When the bot asks how the customer will pay, the drawer shows Payment method: Pay online or Pay in person; an in-person order that is not paid yet shows Payment: Not paid yet. The order's timeline starts with the bot that took it.

Bots that take orders today: restaurant and cloud-kitchen bots, and events bots (ticket orders). Shop bots look up orders in your store's own system instead, and car-service bots take bookings.

When the list is empty

  • With no bot that takes orders: No orders yet and "Press Add order to take an order on the phone or in person. Customers can also order through an inbox bot." with Add order and Set up your bot (Manage your bots when you have bots), which opens the Inbox bots page, in the menu under Engage.
  • With bots that do not take orders it is the same: No orders yet with Add order and Manage your bots.
  • Otherwise, and whenever your workspace already has orders (finished or cancelled ones, say): No orders to work on; pick All statuses to see finished ones.

Add an order by hand

For a phone call or a walk-in:

  1. Press Add order.
  2. Pick the customer from your contacts, or type their name and phone number.
  3. Type what they ordered, one item per line, for example 2 x Chicken shawarma.
  4. Choose pickup or delivery. For delivery, type the address.
  5. Optionally type the total (for example 1,250.50; Arabic digits work too), pick the Currency (optional) from the list (it starts on your workspace's currency), and add notes.
  6. When you picked a contact, the switch Message the customer that we received the order sits next to the buttons at the bottom. It is off: switch it on to send them "We have received your order #…". Press Add order. The order is new, numbered like your bot's orders, opens in its drawer, and its contact's chat is linked, so the customer can be told at each next step. Cancel closes the window without adding it. If the person you picked has no chat with you (for example they only commented on a post), the window says No chat with this person: they will not be messaged about this request. instead of the switch, and nothing is sent.

When there are more orders than one page holds, the line above the list says Showing … of …; press Load more for the next ones.

Checked against the product on Oct 20, 2026

In this section: Engage

All articles