Retell AI Assistant Debug & Enhancement
Budget: $10 – $30 AUD
I have a voice assistant running on Retell AI that’s stuck in an infinite loop. I need you to:
1. Bug Fix
• Locate the faulty loop condition.
• Fix it so the assistant resumes normal flow.
• Trigger a concise status update in the logs once it resumes, so we can confirm the loop is resolved.
2. Conversation Model Extensions
Add three new conversation branches with clear variable handling and logging:
• Booking: After greeting the caller, the bot must request and store their phone number, name, and preferred booking date/time. These three fields must be logged, stored as variables, and passed to my existing booking webhook.
• Food Ordering: Add an intent that collects menu item, quantity, and any special notes, then streams the order payload to my order-handling endpoint.
• Cancel/Reschedule: Allow callers to cancel or move an existing booking by referencing either their phone number or booking ID. The assistant must confirm the change and post the update to my calendar API.
3. POS Integration
• Extend the assistant so it can connect with restaurant POS systems via a unified POS API (e.g., Apideck POS API or similar).
• Must support fetching the menu from the POS and pushing orders directly into it.
• Keep this modular, so we can later add support for multiple POS providers (Square, Lightspeed, Floreant, etc.).
Acceptance Criteria
• Infinite loop is eliminated, with a status log entry confirming recovery.
• All three new conversation branches reliably capture and log the required variables during testing.
• Booking, ordering, and cancellation data is passed correctly to their respective endpoints.
• POS integration successfully retrieves menu items and creates orders using the chosen unified API.
Resources Provided
• Access to current Retell AI project.
• API keys.
• Sample JSON schemas (for booking, ordering, calendar updates).
1. Bug Fix
• Locate the faulty loop condition.
• Fix it so the assistant resumes normal flow.
• Trigger a concise status update in the logs once it resumes, so we can confirm the loop is resolved.
2. Conversation Model Extensions
Add three new conversation branches with clear variable handling and logging:
• Booking: After greeting the caller, the bot must request and store their phone number, name, and preferred booking date/time. These three fields must be logged, stored as variables, and passed to my existing booking webhook.
• Food Ordering: Add an intent that collects menu item, quantity, and any special notes, then streams the order payload to my order-handling endpoint.
• Cancel/Reschedule: Allow callers to cancel or move an existing booking by referencing either their phone number or booking ID. The assistant must confirm the change and post the update to my calendar API.
3. POS Integration
• Extend the assistant so it can connect with restaurant POS systems via a unified POS API (e.g., Apideck POS API or similar).
• Must support fetching the menu from the POS and pushing orders directly into it.
• Keep this modular, so we can later add support for multiple POS providers (Square, Lightspeed, Floreant, etc.).
Acceptance Criteria
• Infinite loop is eliminated, with a status log entry confirming recovery.
• All three new conversation branches reliably capture and log the required variables during testing.
• Booking, ordering, and cancellation data is passed correctly to their respective endpoints.
• POS integration successfully retrieves menu items and creates orders using the chosen unified API.
Resources Provided
• Access to current Retell AI project.
• API keys.
• Sample JSON schemas (for booking, ordering, calendar updates).