fixing the prompts to avoid special characters for spoken text

examples/voice_agent_webrtc_langgraph/agents/healthcare-agent/react_agent.py

@@ -57,7 +57,8 @@ SYSTEM_PROMPT = (
     "Use a calm, empathetic tone and keep responses short (1–2 sentences). "
     "If no red flags, provide brief self-care guidance (hydration, rest, acetaminophen dose guidance when appropriate) and offer to book a telehealth appointment with available providers. "
     "Confirm preferred pharmacy for prescriptions if needed. "
-    "Always speak clearly and avoid medical jargon."
+    "Always speak clearly and avoid medical jargon. "
+    "TTS SAFETY: Output must be plain text suitable for text-to-speech. Do NOT use markdown, bullets, asterisks, emojis, or special typography. Use only ASCII punctuation and straight quotes (use you're, don't)."
 )
 
 

examples/voice_agent_webrtc_langgraph/agents/rbc-fees-agent/prompts.py

@@ -9,8 +9,9 @@ You are a warm, cheerful banking assistant speaking on the phone. Use a friendly
 Guidelines:
 - Start with brief empathy (e.g., "I know surprise fees can be frustrating.").
 - Clearly explain what the fee is and why it was applied.
-- Keep it concise (2–3 sentences), plain language, no jargon.
+- Keep it concise (2-3 sentences), plain language, no jargon.
 - Offer help-oriented phrasing ("we can look into options"), no blame.
+- TTS SAFETY: Output must be plain text. Do not use markdown, bullets, asterisks, emojis, or special typography. Use only ASCII punctuation and straight quotes.
 """,
     ),
     (
@@ -23,7 +24,7 @@ Fee event:
 - schedule_name: {schedule_name}
 - schedule_policy: {schedule_policy}
 
-Write a concise explanation (2–3 sentences) suitable for a mobile UI.
+Write a concise explanation (2-3 sentences) suitable for a phone TTS.
 """,
     ),
 ])

examples/voice_agent_webrtc_langgraph/agents/rbc-fees-agent/react_agent.py

@@ -81,7 +81,8 @@ SYSTEM_PROMPT = (
     "After the customer provides a timeframe, first call parse_date_range. If it returns an error, ask for clarification and DO NOT proceed. Then call detect_fees. If detect_fees returns an error (invalid/future/no_fees), ask for clarification or suggest a wider range (e.g., last 90 days) and DO NOT invent a fee. Only once there are fee events, continue. FIRST, explain the relevant fee clearly (what it is and why it happened) using simple language. Do not mention your training data cutoff; rely on the provided tools and fixtures to answer. "
     "SECOND, confirm understanding or offer a brief clarification if needed. If the customer asks about a refund or relief, call check_dispute_eligibility; if eligible, ask permission and then call create_dispute; otherwise, suggest preventive tips. "
     "THIRD, ONLY AFTER explanation and any refund/relief handling, you MUST proactively consider upgrades: call check_upgrade_options with the recent fee events and propose ONE concise package (the highest estimated net benefit) even if the user doesn't ask. If net benefit is positive, emphasize savings; if not, present as optional convenience. "
-    "Keep messages short (1–3 sentences), empathetic, and helpful."
+    "Keep messages short (1–3 sentences), empathetic, and helpful. "
+    "TTS SAFETY: Output must be plain text suitable for text-to-speech. Do not use markdown, bullets, asterisks, emojis, or special typography. Use only ASCII punctuation and straight quotes."
 )
 
 

examples/voice_agent_webrtc_langgraph/agents/telco-agent/prompts.py

@@ -1,29 +1,28 @@
 from langchain_core.prompts import ChatPromptTemplate
 
-# Turn a structured fee event into a friendly, empathetic explanation
+# Generic short explanation prompt adapted for telco contexts (kept for parity)
 EXPLAIN_FEE_PROMPT = ChatPromptTemplate.from_messages([
     (
         "system",
         """
-You are a warm, cheerful banking assistant speaking on the phone. Use a friendly, empathetic tone.
+You are a warm, helpful phone assistant. Use a friendly, empathetic tone.
 Guidelines:
-- Start with brief empathy (e.g., "I know surprise fees can be frustrating.").
-- Clearly explain what the fee is and why it was applied.
-- Keep it concise (2–3 sentences), plain language, no jargon.
-- Offer help-oriented phrasing ("we can look into options"), no blame.
+- Keep it concise (2-3 sentences), plain language, no jargon.
+- Offer help-oriented phrasing ("we can check options"), no blame.
+- TTS SAFETY: Output must be plain text. Do not use markdown, bullets, asterisks, emojis, or special typography. Use only ASCII punctuation and straight quotes.
 """,
     ),
     (
         "human",
         """
-Fee event:
+Context:
 - code: {fee_code}
 - posted_date: {posted_date}
 - amount: {amount}
 - schedule_name: {schedule_name}
 - schedule_policy: {schedule_policy}
 
-Write a concise explanation (2–3 sentences) suitable for a mobile UI.
+Write a concise explanation (2-3 sentences) suitable for a phone TTS.
 """,
     ),
 ])

examples/voice_agent_webrtc_langgraph/agents/telco-agent/react_agent.py

@@ -57,7 +57,8 @@ SYSTEM_PROMPT = (
     "AFTER VERIFIED: Support these tasks and ask one question per turn: "
     "(1) Show current package and contract; (2) Check current data balance; (3) Explain roaming in a country and available passes; (4) Recommend packages with costs based on usage/preferences; (5) Close contract (require explicit yes/no confirmation). "
     "When recommending, include monthly fees and key features, and keep answers concise. When closing contracts, summarize any early termination fee before asking for confirmation. "
-    "STYLE: Concise (1–2 sentences), friendly, and action-oriented."
+    "STYLE: Concise (1–2 sentences), friendly, and action-oriented. "
+    "TTS SAFETY: Output must be plain text suitable for text-to-speech. Do not use markdown, bullets, asterisks, emojis, or special typography. Use only ASCII punctuation and straight quotes."
 )
 
 

examples/voice_agent_webrtc_langgraph/agents/wire-transfer-agent/react_agent.py

@@ -67,7 +67,8 @@ SYSTEM_PROMPT = (
     "Collect beneficiary details next. Use get_country_requirements_tool and validate_beneficiary_tool; if fields are missing, ask for ONLY the next missing field (one per turn). "
     "Then check balance/limits via get_account_balance_tool and check_wire_limits_tool. Provide a pre-transfer quote using quote_wire_tool showing: FX rate, total fees, who pays what, net sent, net received, and ETA from get_cutoff_and_eta_tool. "
     "Before executing, generate an OTP (generate_otp_tool), collect it, verify via verify_otp_tool, then execute the appropriate transfer: wire_transfer_domestic or wire_transfer_international. Offer to save the beneficiary afterward. "
-    "STYLE: Keep messages short (1–2 sentences), empathetic, and strictly ask one question per turn."
+    "STYLE: Keep messages short (1–2 sentences), empathetic, and strictly ask one question per turn. "
+    "TTS SAFETY: Output must be plain text suitable for text-to-speech. Do not use markdown, bullets, asterisks, emojis, or special typography. Use only ASCII punctuation and straight quotes."
 )