Skip to content

Conversation

@badri-singhal
Copy link
Contributor

@badri-singhal badri-singhal commented Nov 11, 2025

dev-proof.wav

Summary by CodeRabbit

  • New Features

    • Added support for detecting and handling when users are busy during order interactions.
  • Improvements

    • Refined conversational messages across order confirmation, cancellation, and address update flows for more natural, user-friendly interactions.

@coderabbitai
Copy link

coderabbitai bot commented Nov 11, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This PR refines the order confirmation websocket bot by rewriting system messages to be more concise and human-friendly, updating descriptions for existing flow functions, and introducing a new "user_busy" flow state with corresponding handlers and node linkage.

Changes

Cohort / File(s) Summary
Flow function updates and message rewrites
app/agents/voice/breeze_buddy/workflows/order_confirmation/websocket_bot.py
Added new user_busy flow function entry to initial node set and order_functions node set with description and handler; updated cancel_order descriptions to specify cancellation on explicit customer request; rewrote system task_messages across multiple nodes (order confirmation, cancellation, user busy, unrelated questions, address updates) to remove instructional phrasing and quoted prompts in favor of natural, spoken content; added user_busy flow node path with post-actions and flow linkage; simplified verbosity in confirmation messages and final prompts.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Review message content rewrites for tone/clarity consistency across all affected flow nodes
  • Verify new user_busy state integration follows existing flow patterns and handler conventions
  • Confirm updated cancel_order descriptions accurately reflect behavior change

Possibly related PRs

Suggested reviewers

  • swaroopvarma1
  • murdore

Poem

🐰 A bunny's whisper, calm and clear,
No more prompts for ears to hear,
When customers are busy, we now know—
Friendlier words, less fuss, let's go!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
Title check ❓ Inconclusive The title contains a typo ('Persistnet' should be 'Persistent') and is vague about what 'language' changes are being made. While the raw summary shows systematic updates to task messages and flow descriptions for better clarity and consistency, the title doesn't clearly communicate this main improvement. Consider revising the title to be more specific, such as 'Improve message clarity and consistency in order confirmation workflow' or 'Simplify task messages for natural speech output'. Also fix the typo 'Persistnet' to 'Persistent'.
✅ Passed checks (1 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
app/agents/voice/breeze_buddy/workflows/order_confirmation/websocket_bot.py (1)

681-681: Consider refining the phrasing for better clarity.

The message has slightly awkward phrasing with "I am here just to" and a run-on sentence structure. Consider making it more natural and grammatically clear.

Apply this diff for a clearer, more natural flow:

-                            "content": "Thank you for confirming the order. I am here just to confirm your order, for any questions related to the order please refer to the website for more details. Have a good day.",
+                            "content": "Thank you for confirming the order. I'm only here to confirm your order. For any other questions, please refer to the website for more details. Have a good day.",
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c619b43 and 813b8f3.

📒 Files selected for processing (1)
  • app/agents/voice/breeze_buddy/workflows/order_confirmation/websocket_bot.py (8 hunks)
🔇 Additional comments (3)
app/agents/voice/breeze_buddy/workflows/order_confirmation/websocket_bot.py (3)

541-541: LGTM! More specific cancel_order description.

The updated description clarifies that the function should only be called when the customer explicitly asks to cancel, which provides better guidance for the LLM function calling.

Also applies to: 571-571


602-608: LGTM! Good addition of user_busy to order flow.

Adding the user_busy function to the order_functions list is a smart improvement. Users can indicate they're busy at any stage of the conversation, not just during the initial greeting. The function is properly integrated with its handler and flow node.


669-669: LGTM! Natural and conversational message updates.

The updated task messages across these flow nodes are more direct, human-friendly, and appropriate for a voice agent. The removal of instructional phrasing in favor of natural speech improves the user experience.

Also applies to: 693-693, 705-705, 717-717

@badri-singhal badri-singhal force-pushed the language-persistent-throught-the-flow branch from 813b8f3 to 0f9675b Compare November 11, 2025 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant