WhatsApp Chatbot for Restaurant Ordering
Budget: $250 – $750 USD
Scope of Work
The Service Provider agrees to deliver a fully functional WhatsApp chatbot that will fulfill the following features and functionalities:
2.1 Chatbot Interaction Behavior and Logic
No Redundant Messages: The chatbot will ensure that repetitive messages are minimized, especially during the initial stages of conversation, and streamline the user experience.
Automatic Combo Inclusion: When a customer orders a hot dog or hamburger, the chatbot must automatically offer and add the combo (fries + 400ml soda) unless the customer specifies otherwise.
Confirmation without Repetition: During order confirmation, the chatbot will confirm the details without unnecessarily repeating the items in the dish, focusing only on verifying the customer’s final decision.
2.2 Order Finalization Process
The final order confirmation message sent to the customer should include:
"¡Excelente [Customer Name]! Your order is almost ready to be sent. ? To finalize, I need a few more details for delivery:
1️⃣ Location: Please send your exact location via WhatsApp using the 'Share Location' option. ?
2️⃣ Reference: Please provide a reference to help us find you easily (e.g., 'Blue house, red gate').
Once we receive this, we’ll confirm your order and you can enjoy your delicious hamburgers soon! ??
Additionally, please provide:
Full Name ?
Contact Number ?
If you require an electronic invoice ? or plan to pay via bank transfer, please include:
NIT or ID Number and Email ?"
2.3 Payment Methods Integration
The chatbot should be capable of presenting and processing the following payment methods:
Cash on Delivery (COD)
Bank Transfer
Credit/Debit Card (if applicable via integrated third-party services)
2.4 Handling Time and Work Hours
The chatbot should operate within defined working hours and display a relevant message if a customer interacts outside of those hours.
If the customer engages during non-working hours, the bot should notify them of the operating hours and suggest returning later.
2.5 Delivery Fees
The system must calculate and apply the correct delivery fee based on the customer’s location, using predefined rate tables or integration with a location-based API.
2.6 Handling Common Phrases
Certain phrases such as “perra super + papas + bebida,” “puedo pedir,” and “alcanzó a pedir” should trigger appropriate responses from the chatbot rather than invalid or irrelevant answers. These triggers should be configured within the system to handle edge cases and common customer inquiries effectively.
2.7 Combos vs. Promotions
The chatbot must clearly differentiate between Combos (standard meal combinations) and Promotions/Offers (special deals or limited-time discounts). Each should have its own dedicated section in the menu, and the chatbot should guide customers accordingly when presenting these options.
2.8 AI Configuration and Flexibility
The chatbot should be developed using a flexible AI architecture that allows the chatbot's AI model to be changed or updated at any time, for example, switching from Gemini to ChatGPT, or other compatible models.
The chatbot should include an interface that enables easy updates to instructions and responses, allowing the Client to modify or train the chatbot to improve performance based on real-time data.
2.9 Dashboard and Management Console
The Service Provider will develop a web-based dashboard that allows the Client to manage, monitor, and configure various aspects of the chatbot system.
Features of the Dashboard:
Order Monitoring: Real-time tracking of orders, categorized by status (Not started, Cooking, Ready for Dispatch, Delivered).
Menu and Promotion Configuration: Interface to update the menu, set up new combos, promotions, and remove outdated items.
Customer Data Management: View and update customer information, including order history, contact details, and payment preferences.
AI Configuration: A section for adjusting the AI settings, updating prompts, and changing the response models.
Analytics: Basic reporting on sales, order volumes, delivery times, and customer satisfaction metrics.
2.10 Multitenancy for Multiple Locations
The system should support multitenancy, allowing the Client to manage multiple restaurant locations from a single platform with the ability to customize the menu, promotions, and delivery options for each location.
2.11 Data Verification
The chatbot will verify customer data (name, contact number, location) against the internal database before confirming the order. If data is missing, the chatbot will request the customer to provide it before proceeding.
2.12 Time Management and Reminders
If a customer does not respond within a set time (e.g., 5 minutes) after a prompt, the chatbot should automatically follow up with a reminder to encourage completing the order.
If there is no response after multiple follow-ups, the order will be automatically canceled to prevent system clutter.
2.13 Human Interaction
The chatbot must allow the customer conversation to be delegated to a human agent if requested or necessary.
Admin Intervention: Admin users will have the ability to intervene in any active chat session to provide direct assistance or override AI responses.
2.14 Order Status Tracking
After an order is placed, the chatbot will monitor the order’s status (e.g., cooking, dispatched, delivered) and provide updates to the customer.
If an order’s status changes (e.g., dispatched or delayed), the chatbot will proactively notify the customer.
3. Frontend and User Interface
3.1 Order and Status Dashboard
The Service Provider will develop a user-friendly dashboard where administrators can:
View incoming orders in real-time.
Track the order’s status from preparation to delivery.
Adjust any necessary parameters, such as delivery fee rates or promotional discounts.
3.2 Statistics and Reports
The dashboard will offer robust reporting functionality, with the ability to generate customizable reports based on various filters such as order date, product type, location, delivery times, and total sales.
3.3 Source Code Delivery
Upon final approval and successful deployment of the chatbot system, the Service Provider agrees to deliver the full source code to the Client. This includes all scripts, configurations, and code required for the operation of the chatbot, the management dashboard, and any integrations with external APIs.
A Similar project can be test via WhatsApp +57 313 7405042
The Service Provider agrees to deliver a fully functional WhatsApp chatbot that will fulfill the following features and functionalities:
2.1 Chatbot Interaction Behavior and Logic
No Redundant Messages: The chatbot will ensure that repetitive messages are minimized, especially during the initial stages of conversation, and streamline the user experience.
Automatic Combo Inclusion: When a customer orders a hot dog or hamburger, the chatbot must automatically offer and add the combo (fries + 400ml soda) unless the customer specifies otherwise.
Confirmation without Repetition: During order confirmation, the chatbot will confirm the details without unnecessarily repeating the items in the dish, focusing only on verifying the customer’s final decision.
2.2 Order Finalization Process
The final order confirmation message sent to the customer should include:
"¡Excelente [Customer Name]! Your order is almost ready to be sent. ? To finalize, I need a few more details for delivery:
1️⃣ Location: Please send your exact location via WhatsApp using the 'Share Location' option. ?
2️⃣ Reference: Please provide a reference to help us find you easily (e.g., 'Blue house, red gate').
Once we receive this, we’ll confirm your order and you can enjoy your delicious hamburgers soon! ??
Additionally, please provide:
Full Name ?
Contact Number ?
If you require an electronic invoice ? or plan to pay via bank transfer, please include:
NIT or ID Number and Email ?"
2.3 Payment Methods Integration
The chatbot should be capable of presenting and processing the following payment methods:
Cash on Delivery (COD)
Bank Transfer
Credit/Debit Card (if applicable via integrated third-party services)
2.4 Handling Time and Work Hours
The chatbot should operate within defined working hours and display a relevant message if a customer interacts outside of those hours.
If the customer engages during non-working hours, the bot should notify them of the operating hours and suggest returning later.
2.5 Delivery Fees
The system must calculate and apply the correct delivery fee based on the customer’s location, using predefined rate tables or integration with a location-based API.
2.6 Handling Common Phrases
Certain phrases such as “perra super + papas + bebida,” “puedo pedir,” and “alcanzó a pedir” should trigger appropriate responses from the chatbot rather than invalid or irrelevant answers. These triggers should be configured within the system to handle edge cases and common customer inquiries effectively.
2.7 Combos vs. Promotions
The chatbot must clearly differentiate between Combos (standard meal combinations) and Promotions/Offers (special deals or limited-time discounts). Each should have its own dedicated section in the menu, and the chatbot should guide customers accordingly when presenting these options.
2.8 AI Configuration and Flexibility
The chatbot should be developed using a flexible AI architecture that allows the chatbot's AI model to be changed or updated at any time, for example, switching from Gemini to ChatGPT, or other compatible models.
The chatbot should include an interface that enables easy updates to instructions and responses, allowing the Client to modify or train the chatbot to improve performance based on real-time data.
2.9 Dashboard and Management Console
The Service Provider will develop a web-based dashboard that allows the Client to manage, monitor, and configure various aspects of the chatbot system.
Features of the Dashboard:
Order Monitoring: Real-time tracking of orders, categorized by status (Not started, Cooking, Ready for Dispatch, Delivered).
Menu and Promotion Configuration: Interface to update the menu, set up new combos, promotions, and remove outdated items.
Customer Data Management: View and update customer information, including order history, contact details, and payment preferences.
AI Configuration: A section for adjusting the AI settings, updating prompts, and changing the response models.
Analytics: Basic reporting on sales, order volumes, delivery times, and customer satisfaction metrics.
2.10 Multitenancy for Multiple Locations
The system should support multitenancy, allowing the Client to manage multiple restaurant locations from a single platform with the ability to customize the menu, promotions, and delivery options for each location.
2.11 Data Verification
The chatbot will verify customer data (name, contact number, location) against the internal database before confirming the order. If data is missing, the chatbot will request the customer to provide it before proceeding.
2.12 Time Management and Reminders
If a customer does not respond within a set time (e.g., 5 minutes) after a prompt, the chatbot should automatically follow up with a reminder to encourage completing the order.
If there is no response after multiple follow-ups, the order will be automatically canceled to prevent system clutter.
2.13 Human Interaction
The chatbot must allow the customer conversation to be delegated to a human agent if requested or necessary.
Admin Intervention: Admin users will have the ability to intervene in any active chat session to provide direct assistance or override AI responses.
2.14 Order Status Tracking
After an order is placed, the chatbot will monitor the order’s status (e.g., cooking, dispatched, delivered) and provide updates to the customer.
If an order’s status changes (e.g., dispatched or delayed), the chatbot will proactively notify the customer.
3. Frontend and User Interface
3.1 Order and Status Dashboard
The Service Provider will develop a user-friendly dashboard where administrators can:
View incoming orders in real-time.
Track the order’s status from preparation to delivery.
Adjust any necessary parameters, such as delivery fee rates or promotional discounts.
3.2 Statistics and Reports
The dashboard will offer robust reporting functionality, with the ability to generate customizable reports based on various filters such as order date, product type, location, delivery times, and total sales.
3.3 Source Code Delivery
Upon final approval and successful deployment of the chatbot system, the Service Provider agrees to deliver the full source code to the Client. This includes all scripts, configurations, and code required for the operation of the chatbot, the management dashboard, and any integrations with external APIs.
A Similar project can be test via WhatsApp +57 313 7405042