
A solution for HoReCa · restaurants and delivery
JediDesk for restaurants and delivery
Care for your guest continues after the order is placed.
Orders · venue rules · team
Your guest wants to know what is happening with their order while your team is taking the next ones. JediDesk AI helps answer using connected system data, explain promotion terms and gather details of a problem. With an integration configured, the enquiry becomes a task for the responsible team, with the context needed for the next steps.
Guest care through a modern conversation. An AI interpretation of Vermeer's The Milkmaid.
The restaurant's day-to-day work
Your guest needs a specific answer about their situation
One enquiry concerns the menu, another an order already placed, and a third needs a manager's decision. These conversations have different information sources and different next steps.
Enquiries during busy hours
While your team prepares and dispatches orders, questions about delivery, purchase terms and promotions build up in chat.
The status of a specific order
“Please wait” does not explain the situation. The order needs to be found and its available status checked in the venue's system.
Current offer terms
The guest wants to know whether a promotion applies to their order. The dates, offer details and restrictions approved by the restaurant matter.
A problem after delivery
Feedback about a dish needs details and a responsible person. The enquiry must reach the right team.
Before automation
What complicates support between the kitchen and chat
Order data is found manually
The manager switches from the conversation to the business system and back to answer a single routine question.
Different answers about a promotion
Terms have changed, but chat still uses the old explanation. Your team needs one current source.
The complaint stays in the conversation
The message exists, but it is unclear who should check quality, which details have been gathered or which order the problem concerns.
The guest repeats their story
After a handover to a colleague, the guest has to identify the order and explain the situation again. The enquiry history helps continue the conversation.
Automation use cases
From “where is my order?” to help from the responsible team
The assistant uses the restaurant's rules and available system data. When a human decision is needed, it prepares the enquiry and passes on the context.
Order status
The guest asks what stage their order has reached.
With an integration configured, AI consults the business system or CRM and explains the returned status. If there is not enough information for the search, it asks for the order identifier.
Order system integrationThe guest receives an answer from the source the restaurant uses.
Promotions and special offers
The customer wants to use an offer they saw in an advertisement.
AI finds the terms in the current knowledge base or connected source: validity period, offer details and restrictions. If information is missing, it passes the question to your team.
JediDesk AI capabilitiesThe guest understands the offer terms before placing an order.
Delivery questions
The guest needs to clarify the delivery area, payment method or collection procedure.
The assistant answers according to the venue's rules. It reports an arrival time for a specific order only when those details are available from the connected system.
JediDesk AI capabilitiesGeneral rules and data for a specific order are kept distinct.
Quality feedback
The guest reports a burnt pizza or another problem with a dish.
AI clarifies the order and situation description, asking for a photo if needed. With an integration configured, it creates a task for the quality team with available details and a link to the customer.
Passing on data and tasksThe responsible team receives the materials needed for a review.
An unusual question
A change, exception or information unavailable in the sources is needed.
The assistant gathers details and passes the enquiry to the manager according to the venue's rules. Available order changes and other actions are agreed separately.
JediDesk AI capabilitiesA person joins with the situation already explained.
How the solution works
Enquiry → order data → answer or task
A typical route for an enquiry after purchase. The system returns only available data; if it is insufficient or a quality decision is needed, the assistant involves your team.
- 01

The guest gets in touch
They write in chat or a connected messaging channel about an order, promotion or problem with a dish.
- 02

AI clarifies the details
It identifies the question. For personal data, it uses the agreed order search and verification method, asking only for the details needed.
- 03

It retrieves information
It consults the connected system for status and the knowledge base for rules. It prepares the collected problem details for your team.
- 04

It answers or hands over
It explains available data. With an integration configured, it creates a task for the right department; a person decides how to resolve the problem.
Capability map
What restaurant AI support brings together
The guest's enquiry directs the conversation to the right source or responsible team.
A guest's question in chat or a connected messaging channel

Order status
Explains the returned status with an integration configured.
Source: Business system / CRM
Menu and offers
Answers using prepared descriptions and the venue's terms.
Source: Menu + knowledge base
Current promotions
Clarifies terms and restrictions using available data.
Source: Current restaurant offers
Delivery terms
Explains the rules; an individual estimate comes only from the source.
Source: Rules + order data
A quality task
Passes the description and materials into a task with an integration configured.
Source: Conversation + routing rules
Help from a person
Involves the manager in an unusual question.
Source: Handover rules + team
The guest receives an answer, or the enquiry goes to the responsible team with the details it needs.
An AI interpretation of The Milkmaid and a map of configurable scenarios.
Channels and integrations
Connect the conversation to your venue's data
Channels receive enquiries, the knowledge base explains rules, and an integration provides information about a specific order. Available actions depend on the restaurant's system.
Website chat
Help for the guest while choosing and after placing an order.
About the channelTelegram
Order enquiries through the restaurant's connected bot.
About the channelQuestions about the menu, current offers and how the venue operates.
About the channelGuest communication through a configured support channel.
About the channelBusiness system or CRM
Agree order search, available statuses, identification rules and task creation for the responsible team.
How to connectMenu, promotions and rules
Prepare current delivery, payment and offer terms, along with rules for handling guest feedback.
How to connect
Example conversations
What support looks like in a conversation
Illustrative restaurant examples, not real customer conversations. The statuses and actions in these scenarios assume a configured integration with the venue's system.
- 01Details from the guest
- 02A task with context
- 03The team's decision
Check the status
Website chatIf the status is unavailable or further checks are needed, the manager joins.
The answer does not contain an invented arrival time.
Pass on quality feedback
Telegram · the restaurant's connected channelConfirmation of task creation is sent after a successful response from the integration.
The responsible team decides on a replacement or compensation.
Results and benefits
The guest receives attention; your team receives a clear enquiry
Assess the result in your own conversations: was the order found, is the answer accurate, and does the responsible department have enough information?
Fewer manual status checks
Routine questions use connected system data without a separate manual search by the manager.
Consistent answers about terms
Prepared rules and current offers become the source for chat guidance.
The enquiry has a next step
The problem reaches the right team through a defined route rather than remaining only a message.
Context is preserved
The situation description and supplied materials help a person continue handling the enquiry.
Customer experience
How businesses use JediDesk


Pizza.Od.Ua · customer experience
Order status and a quality task are parts of one service.
Pizza.Od.Ua websiteAn artistic illustration of restaurant service. Logo from the official Pizza.Od.Ua website.

NarsCars · car rental
Advice before booking
View a related case studyOriginal NarsCars photo from the case materials

Shop For Cars · car accessories
Help choosing car accessories
View a related case studyProduct visual from the Shop For Cars case study


TANOYA · cosmetics
Cosmetics recommendations from the catalog
View a related case studyIllustrative visual from the TANOYA case study. Process description based on the case materials.
About Pizza.Od.Ua
Order status and a quality task are parts of one service.
The brand comes from the official Pizza.Od.Ua website. Implementation scenarios are based on the JediDesk team's description.
Pizza.Od.Ua is a food delivery service in Odesa. In its work with this customer, JediDesk combines answers based on order system data, offer information and handovers of feedback to the responsible team.
- Order status and promotion terms come from the venue's connected sources.
- A problem with a dish is passed to the quality team as a task with details.
Built around your process
Why JediDesk suits restaurant support
Answers using your data
Orders and promotions have a specific source. You decide which information the assistant can use in a conversation.
JediDesk AI capabilitiesA connection to your venue's team
An integration can be used to configure task creation and pass on details according to a defined process.
Integrations and actionsResponsibilities are defined
AI answers routine questions and prepares the enquiry; the manager or quality team makes decisions in complex situations.
AI assistant rulesLaunching the solution
Start with order status and problem handovers
Involve a manager who understands guest service and the person responsible for the business system. The launch timeline depends on data readiness and the connection.
- 1
Describe common enquiries
Gather questions about delivery, statuses, promotions and quality. Define who continues each complex enquiry.
- 2
Prepare your sources
Update rules and offers. Agree order search and permitted system fields with a technical specialist.
- 3
Configure tasks
Define the recipient, the link to the customer, required details and the reply to the guest after a successful handover.
- 4
Test complex situations
Test an unknown order, an unavailable system, an expired promotion and quality feedback. Make sure there is a route to a person.
Before you start
Frequently asked questions
About order data, current promotions and handing enquiries to your team.
How does AI find the status of a specific order?
This requires an integration with the business system or CRM where the restaurant manages orders. During setup, define the search and verification method, available fields and wording for explaining statuses. If the customer or order cannot be identified unambiguously, the assistant asks for the necessary details. When the system does not respond or lacks the information, the question goes to the manager according to your rules.
Does the guest have to enter an order number every time?
It depends on the conversation context and configured integration. If the order is already unambiguously linked to the customer and the venue's rules permit its details to be shown, asking again may be unnecessary. If there is no link or several orders exist, clarification is needed. Before launch, agree the identification method and test different situations so the assistant does not show information about someone else's order.
Where does the assistant get current promotions?
The source can be a prepared knowledge base or a connected restaurant system. It should contain current offer terms: dates, details, restrictions and application rules. The venue is responsible for updates, and the AI scenario uses the available information. If a promotion has ended or data is contradictory, plan for clarification through your team. The assistant must not invent a promotional code or discount.
What happens to a complaint about food quality?
The assistant collects the problem description, order data and, if needed, photos. With an integration configured, these materials are passed into a task for the quality team or another responsible person. The guest receives confirmation only after successful task creation; if the handover fails, a fallback route to a person is needed. The venue's team reviews the situation and decides on a replacement, compensation or refund.
Can AI change an order or promise a delivery time?
Each such action requires separate rules and technical capability in the connected system. The main scenarios on this page are retrieving an available status, explaining terms and handing the enquiry to your team. Arrival times can be reported when the source actually returns that information. If a change needs manual agreement or a delay needs clarification, the assistant gathers details and passes the question to the manager.
How should a restaurant or pizzeria start the rollout?
Choose a few common questions and one communication channel. Prepare current rules, describe the available order statuses and assign responsibility for complex enquiries. Agree the integration with a technical specialist and test order search, missing data, task creation errors and handovers to a person. After testing, you can gradually add channels and other venue scenarios.
The next step — your venue
Give your guest an answer and your team the context
Start with common order questions and clear handovers for complex enquiries. Configure JediDesk around your restaurant's data and rules.
The free trial lasts 14 days. Integration capabilities depend on the venue's system.
- Your orders and rules
- Tasks for the responsible team
- AI and a person in one process



