Can customers order directly through WhatsApp?

Yes. A customer builds an order in the conversation, confirms it, gives an address, and gets status updates on the same thread.

Do you connect to delivery marketplaces?

Not by integration. The usual route is capturing customers directly, with a QR code on packaging or at the counter, so the relationship is yours.

Can it answer allergen questions?

From the documents you connect, with sources shown. Given the stakes, most kitchens route allergen questions to a person, and Otobiz supports that.

Can we message customers about a new menu?

Yes, to contacts with a consent basis, with quiet hours and frequency caps applied. Contacts with no opt-in are excluded with the reason shown.

Can we handle peak service without anyone watching the phone?

Routine questions can be answered automatically once you enable it. Everything else waits in the inbox with a draft already written.

Do we need one number per outlet?

A workspace connects one WhatsApp number. Several outlets usually means several workspaces, switched between from one login.

How do we get marketplace customers onto our own channel?

A code on the packaging or the receipt opens a chat with a reference attached. The customer chooses to message you, which is also what makes the consent real.

Can we take reservations?

Reservation questions are answered from your own content, and a booking page shows only the slots you can actually serve.

Regulars, remembered.

Restaurants and cloud kitchens run on repeat customers, and most of them are strangers to the till.

Restaurants, cafes, cloud kitchens, and food brands use business messaging to take direct orders, confirm reservations, and keep in contact with regulars. The commercial reason is margin: an order taken directly is worth more than the same order through a marketplace, and the customer record that comes with it is the one asset a marketplace never hands over.

What usually goes wrong.

Marketplaces keep the customer: You cook the food, pay the commission, and never learn who ate it. Rebuilding a direct relationship starts with a channel you control.
Order and reservation messages arrive at the worst moment: Peak service is exactly when nobody can look at a phone, and exactly when the messages arrive.
Menu questions repeat forever: Allergens, portion sizes, delivery radius, and opening hours are asked hundreds of times and answered from the same three facts.

What Otobiz does about it.

Menu and policy questions answered automatically

Load the menu, allergen information, and delivery rules, and routine questions are answered from them with sources shown. Anything unusual goes to a person.

Menu and allergen answers from your own documents
Card carousels and option lists instead of long text
Handoff on anything the content does not cover

Direct ordering in the conversation

A customer picks items in chat, confirms the cart, gives an address, and receives status updates on the same thread as the order moves through the kitchen.

Cart building and confirmation inside the chat
Address capture and price reconciliation before confirming
Status updates sent as the order progresses

Regulars turned into a segment

Order history and conversation history make it possible to define regulars, lapsed customers, and high-value customers, and to message each group differently with consent screening applied.

Segments from order recency, frequency, and value
Quiet hours so an offer does not land at midnight
Frequency caps across campaigns

A person on anything that matters

Campaigns, scheduled sends, and anything that writes to another system queue for approval. The approval is bound to the exact message you approved and re-checked at send time, so what the approver saw is what goes out.

Approve, edit, or reject before anything leaves
The message you approved is the message that sends
Every send logged with who approved it

Capturing the customers you cannot see

A code on the packaging, the receipt, or a table card opens a chat with a reference attached, which is how a marketplace order becomes a customer you can contact again.

Trackable links and codes that open a chat
The source recorded on the contact from the first message
Consent captured at the point of contact, with the wording stored

What matters most here.

Common questions

Can customers order directly through WhatsApp?: Yes. A customer builds an order in the conversation, confirms it, gives an address, and gets status updates on the same thread.
Do you connect to delivery marketplaces?: Not by integration. The usual route is capturing customers directly, with a QR code on packaging or at the counter, so the relationship is yours.
Can it answer allergen questions?: From the documents you connect, with sources shown. Given the stakes, most kitchens route allergen questions to a person, and Otobiz supports that.
Can we message customers about a new menu?: Yes, to contacts with a consent basis, with quiet hours and frequency caps applied. Contacts with no opt-in are excluded with the reason shown.
Can we handle peak service without anyone watching the phone?: Routine questions can be answered automatically once you enable it. Everything else waits in the inbox with a draft already written.
Do we need one number per outlet?: A workspace connects one WhatsApp number. Several outlets usually means several workspaces, switched between from one login.
How do we get marketplace customers onto our own channel?: A code on the packaging or the receipt opens a chat with a reference attached. The customer chooses to message you, which is also what makes the consent real.
Can we take reservations?: Reservation questions are answered from your own content, and a booking page shows only the slots you can actually serve.