rasa-pro 3.14.0.dev20250825__py3-none-any.whl → 3.14.0.dev20250922__py3-none-any.whl

rasa/cli/project_templates/telco/actions/general/action_human_handoff.py

@@ -0,0 +1,49 @@
+from typing import Any, Dict, List, Text
+
+from openai import AsyncOpenAI
+from rasa_sdk import Action, Tracker
+from rasa_sdk.events import BotUttered
+from rasa_sdk.executor import CollectingDispatcher
+from rasa_sdk.types import DomainDict
+
+
+class ActionHumanHandoff(Action):
+    def __init__(self) -> None:
+        super().__init__()
+        self.client = AsyncOpenAI()
+
+    def name(self) -> Text:
+        return "action_human_handoff"
+
+    async def run(
+        self, dispatcher: CollectingDispatcher, tracker: Tracker, domain: DomainDict
+    ) -> List[Dict[Text, Any]]:
+        # Collect conversation
+        convo = []
+        for event in tracker.events:
+            if event.get("event") == "user":
+                user_text = "{}".format(event.get("text"))
+                user_text2 = "user - " + user_text
+                convo.append(user_text2)
+            if event.get("event") == "bot":
+                bot_text = "{}".format(event.get("text"))
+                bot_text2 = "bot - " + bot_text
+                # print(bot_text)
+                convo.append(bot_text2)
+        prompt = (
+            f"The following is a conversation between a bot and a human user, "
+            f"please summarise so that a human agent can easily understand "
+            f"the important context. Conversation: {convo}"
+        )
+        response = await self.client.chat.completions.create(
+            model="gpt-4",  # or "gpt-3.5-turbo"
+            messages=[{"role": "user", "content": prompt}],
+        )
+        summarised_conversation = response.choices[0].message.content or ""
+        return [
+            BotUttered(
+                f"I will transfer the following summary of our conversation "
+                f"to the Callback Manager:\n"
+                f"{summarised_conversation}"
+            )
+        ]

rasa/cli/project_templates/telco/actions/network/actions_get_data_from_db.py

@@ -0,0 +1,48 @@
+import csv
+from typing import Dict, List
+
+from rasa_sdk import Action
+from rasa_sdk.events import SlotSet
+from rasa_sdk.executor import CollectingDispatcher
+from rasa_sdk.interfaces import Tracker
+from rasa_sdk.types import DomainDict
+
+
+class ActionGetCustomerInfo(Action):
+    def name(self) -> str:
+        return "action_get_customer_info"
+
+    def run(
+        self, dispatcher: CollectingDispatcher, tracker: Tracker, domain: DomainDict
+    ) -> List[Dict]:
+        # Load CSV file
+        file_path = "csvs/customers.csv"  # get information from your DBs
+        customer_id = tracker.get_slot("customer_id")
+
+        try:
+            with open(file_path, "r", newline="") as csvfile:
+                reader = csv.DictReader(csvfile)
+
+                # Filter data for the given customer ID
+                customer_info = None
+                for row in reader:
+                    if row["customer_id"] == str(customer_id):
+                        customer_info = row
+                        break
+
+                if customer_info is None:
+                    dispatcher.utter_message("No customer found with this ID.")
+                    return []
+
+                # Extract customer details
+                first_name = customer_info["first_name"]
+
+                # Set the retrieved name in a slot
+                return [SlotSet("customer_first_name", first_name)]
+
+        except FileNotFoundError:
+            dispatcher.utter_message("Customer database file not found.")
+            return []
+        except Exception:
+            dispatcher.utter_message("Error retrieving customer information.")
+            return []

rasa/cli/project_templates/telco/actions/network/actions_run_diagnostics.py

@@ -0,0 +1,28 @@
+import asyncio
+import random
+
+from rasa_sdk import Action
+from rasa_sdk.events import EventType, SlotSet
+from rasa_sdk.executor import CollectingDispatcher
+from rasa_sdk.interfaces import Tracker
+from rasa_sdk.types import DomainDict
+
+
+class ActionSleepAndRespond(Action):
+    def name(self) -> str:
+        return "actions_run_speed_test"
+
+    async def run(
+        self, dispatcher: CollectingDispatcher, tracker: Tracker, domain: DomainDict
+    ) -> list[EventType]:
+        await asyncio.sleep(10)
+        dispatcher.utter_message(
+            text="Thank you for waiting... ✅ "
+        )  # Send to the user
+
+        random_number = random.randint(
+            50, 150
+        )  # we will pick randomly the internet speed here
+        # for local testing purposes you can define the number
+        # for Production testing connect to the API to get this data
+        return [SlotSet("network_speed", random_number)]

rasa/cli/project_templates/telco/actions/network/actions_session_start.py

@@ -0,0 +1,18 @@
+import asyncio
+
+from rasa_sdk import Action
+from rasa_sdk.events import EventType
+from rasa_sdk.executor import CollectingDispatcher
+from rasa_sdk.interfaces import Tracker
+from rasa_sdk.types import DomainDict
+
+
+class ActionSleepAndRespond(Action):
+    def name(self) -> str:
+        return "action_sleep_few_sec"
+
+    async def run(
+        self, dispatcher: CollectingDispatcher, tracker: Tracker, domain: DomainDict
+    ) -> list[EventType]:
+        await asyncio.sleep(3)
+        return []

rasa/cli/project_templates/telco/config.yml

@@ -0,0 +1,29 @@
+# Rasa Agent Configuration
+# This file controls your agent's language, message processing pipeline, and conversation policies.
+# For full documentation, see: https://rasa.com/docs/pro/build/configuring-assistant
+recipe: default.v1
+language: en
+
+# The agent project unique identifier
+# This default value must be replaced with a unique agent name within your deployment
+assistant_id: placeholder_default
+
+pipeline:
+- name: SearchReadyLLMCommandGenerator
+  llm:
+    model_group: openai-gpt-4o
+  flow_retrieval:
+    active: false
+
+
+policies:
+- name: FlowPolicy
+- name: EnterpriseSearchPolicy
+  vector_store:
+    type: "faiss"
+    source: "./docs"
+  llm:
+    model_group: openai-gpt-4o
+  embeddings:
+    model_group: openai-embeddings
+  check_relevancy: true

rasa/cli/project_templates/telco/credentials.yml

@@ -0,0 +1,33 @@
+# This file contains the credentials for the voice & chat platforms
+# which your bot is using.
+# https://rasa.com/docs/rasa-pro/connectors/messaging-and-voice-channels/
+
+rest:
+#  # you don't need to provide anything here - this channel doesn't
+#  # require any credentials
+
+
+#facebook:
+#  verify: "<verify>"
+#  secret: "<your secret>"
+#  page-access-token: "<your page access token>"
+
+#slack:
+#  slack_token: "<your slack token>"
+#  slack_channel: "<the slack channel>"
+#  slack_signing_secret: "<your slack signing secret>"
+
+#socketio:
+#  user_message_evt: <event name for user message>
+#  bot_message_evt: <event name for bot messages>
+#  session_persistence: <true/false>
+
+#mattermost:
+#  url: "https://<mattermost instance>/api/v4"
+#  token: "<bot token>"
+#  webhook_url: "<callback URL>"
+
+# This entry is needed if you are using Rasa Enterprise. The entry represents credentials
+# for the Rasa Enterprise "channel", i.e. Talk to your bot and Share with guest testers.
+rasa:
+  url: "http://localhost:5002/api"

rasa/cli/project_templates/telco/csvs/billing.csv

@@ -0,0 +1,19 @@
+customer_id,date,amount,source
+123,01/01/2025,150.50,Internet
+123,01/02/2025,55.00,Internet
+123,01/03/2025,60.00,Internet
+123,01/04/2025,65.00,Internet
+123,01/05/2025,70.00,Internet
+123,01/06/2025,75.00,Internet
+123,01/07/2025,80.00,Internet
+123,01/08/2025,85.00,Internet
+123,01/09/2025,90.00,Internet
+123,01/10/2025,95.00,Internet
+123,01/11/2025,100.00,Internet
+123,01/12/2025,105.00,Internet
+124,01/01/2025,53.00,TV
+124,01/02/2025,53.00,TV
+124,01/03/2025,53.00,TV
+125,01/01/2025,89.75,Mobile
+125,01/02/2025,89.75,Mobile
+125,01/03/2025,89.75,Mobile

rasa/cli/project_templates/telco/csvs/customers.csv

@@ -0,0 +1,5 @@
+customer_id,first_name,last_name
+123,Serena,Williams
+124,Lionel, Messi
+125,Tom, Cruise
+456,Beyoncé, Knowles

rasa/cli/project_templates/telco/data/billing/flow_understand_bill.yml

@@ -0,0 +1,45 @@
+flows:
+  understand_bill:
+    if: slots.user_authenticated # the user has to be authenticated in order to access this flow
+    description: This flow allows users to check their bill and billing related details.
+    steps:
+      - collect: bill_month
+        ask_before_filling: False
+      - action: action_verify_bill_by_date
+      - collect: breakdown_cost
+        description: |
+          This slot is boolean variable. it holds one of two possible values: true or false
+          (breakdown_cost = True, breakdown_cost = False), and if the user says "yup," it should be considered True, while "nope" should be considered False
+          (e.g., breakdown_cost = True for "yup", breakdown_cost = False for "nope").
+        ask_before_filling: true # This can be useful some LLMs will prefill bool slots here we make it mandatory for the bot to ask the user
+        next:
+          - if: slots.breakdown_cost # it has to be 'slots' with an 's', this means breakdown_cost is True
+            then:
+              - action: action_recap_bill
+              - collect: more_bill_details
+                next:
+                  - if: slots.more_bill_details
+                    then:
+                      - action: utter_provide_bill_sources
+                        next: "END"
+                  - else: issue_solved_section # this will call "issue_solved_section" section
+
+          - else: issue_solved_section
+
+      - id: issue_solved_section # This will help avoid re-writting the same piece of code, this way it can be re-used
+        collect: issue_solved
+        description: |
+          This slot is boolean variable. it holds one of two possible values: true or false
+          (issue_solved = True, issue_solved = False), and if the user says "yup" it should be considered True, while "nope" should be considered False
+          (e.g., issue_solved = True for "yup", issue_solved = False for "nope").
+        ask_before_filling: true
+        next:
+          - if: not slots.issue_solved # this means issue_solved is False
+            then:
+              - action: utter_connect_to_human
+              - action: action_sleep_few_sec
+              -  link: human_handoff
+
+          - else:
+            - action: utter_end_conversation
+              next: "END"

rasa/cli/project_templates/telco/data/data.md

@@ -0,0 +1,11 @@
+## 📂 `data/` – The Agent's Business Logic
+
+This folder holds files that define your agent’s skills using "flows". [1](https://rasa.com/docs/pro/build/writing-flows) Each flow is a step-by-step conversation pattern (like a recipe) for handling a user goal (e.g., checking a balance, updating an address).
+
+**What you'll find:**
+- **billing/**: Billing and payment flows (bill inquiries, payment processing)
+- **network/**: Network service flows (troubleshooting, diagnostics, service checks)
+- **general/**: General telecom conversations (greetings, help, support)
+
+**Edit YAML files in this folder** to add new telecom features, modify existing flows, or adjust what the agent asks customers.
+

rasa/cli/project_templates/telco/data/general/bot_challenge.yml

@@ -0,0 +1,6 @@
+flows:
+  bot_challenge:
+    name: bot challenge
+    description: This flow clarifies that the user is talking to a chatbot, when the user ask if they are talking to a chatbot or a human
+    steps:
+      - action: utter_bot_challenge

rasa/cli/project_templates/telco/data/general/feedback.yml

@@ -0,0 +1,20 @@
+# Simple thumbs up/down feedback flow
+flows:
+  leave_feedback:
+    name: leaving feedback
+    description: This flow collects simple thumbs up or thumbs down feedback
+    if: False # Flow guard to prevent direct triggering
+    steps:
+      - collect: feedback_rating
+        description: Ask user for thumbs up or thumbs down feedback
+      - id: feedback_response
+        noop: true
+        next:
+          - if: slots.feedback_rating == "thumbs_up"
+            then: positive_response
+          - else: negative_response
+      - id: positive_response
+        action: utter_thankyou_positive
+        next: END
+      - id: negative_response
+        action: utter_thankyou_negative

rasa/cli/project_templates/telco/data/general/goodbye.yml

@@ -0,0 +1,6 @@
+flows: 
+  goodbye:
+    description: Handle user goodbye messages, say farewell, and collect feedback
+    steps:
+      - action: utter_goodbye
+      - link: leave_feedback

rasa/cli/project_templates/telco/data/general/hello.yml

@@ -0,0 +1,6 @@
+flows:
+  hello:
+    description: Flow for greeting the user hello
+    name: hello
+    steps:
+      - action: utter_hello

rasa/cli/project_templates/telco/data/general/human_handoff.yml

@@ -0,0 +1,16 @@
+version: "3.1"
+flows:
+  human_handoff:
+    description: When you are unable to handle the request or the user is frustrated - offers to hand the user over to a live human agent. 
+    steps:
+      - collect: confirm_human_handoff
+        ask_before_filling: True
+        next:
+          - if: slots.confirm_human_handoff
+            then:
+            - action: utter_transferring_to_human
+            - action: action_human_handoff
+              next: END
+          - else:
+            - action: utter_human_handoff_cancelled
+              next: END

rasa/cli/project_templates/telco/data/general/patterns.yml

@@ -0,0 +1,30 @@
+flows:
+  pattern_completed:
+    description: A flow has been completed and there is nothing else to be done
+    if: False
+    steps:
+      - noop: true
+        next: END
+
+  pattern_correction:
+    description: Handle a correction of a slot value.
+    name: pattern correction
+    steps:
+      - action: action_correct_flow_slot
+        next: "END"
+
+  pattern_search:
+    description: Flow for handling knowledge-based questions
+    name: pattern search
+    steps:
+      - id: 0_action_trigger_search
+        next: END
+        action: action_trigger_search
+
+  pattern_session_start:
+    description: Flow for starting the conversation
+    name: pattern session start
+    nlu_trigger:
+      - intent: session_start
+    steps:
+      - action: utter_greeting

rasa/cli/project_templates/telco/data/network/flow_reboot_router.yml

@@ -0,0 +1,8 @@
+flows:
+  reboot_router: # only reboot/restart the router
+    if: False
+    description: Help user reboot and restart their router, the user will be doing this action
+    steps:
+      - action: utter_explain_reboot_router
+      - collect: reboot_router
+        reset_after_flow_ends: true

rasa/cli/project_templates/telco/data/network/flow_reset_router.yml

@@ -0,0 +1,7 @@
+flows:
+  reset_router: # restet the router rometely
+    if: False
+    description: Help user reset their router, the bot will do this action on behalf of the user
+    steps:
+      - action: utter_explain_reset_router
+      - action: utter_image_reset_router

rasa/cli/project_templates/telco/data/network/flow_solve_internet_issue.yml

@@ -0,0 +1,73 @@
+flows:
+  fix_internet_slow: # flow name mandatory – this defines a conversational flow for running diagnostics.
+    description: Help users solve when internet is slow and provide solutions # description another madatory field this will be sent to CALM
+    steps:
+      - action: utter_acknowledge_issue # an utter a response that the agent will display to the end user.
+      - action: action_sleep_few_sec # Adding sleep time in a chatbot conversation makes interactions feel more natural,
+                                    #improves readability, and simulates processing delays for a better user experience.
+      - call: run_diagnostics # Call a flow, this flow can be re-used multiple times.
+                              # fix_internet_slow will (parent flow) call run_diagnostics (child flow)
+                              # when you call a flow, you go to the child flow and then be back to the parent flow
+                              # first call
+        next:
+          - if: slots.network_speed < 100 # the syntax is important it has to be slots, this slot has to be float as well
+            then:
+              - action: utter_acknowledge_speed_test_not_good
+              - action: action_sleep_few_sec
+              - action: utter_propose_reboot_router_solution
+              - action: action_sleep_few_sec
+              - call: reboot_router
+                next:
+                  - if: slots.reboot_router # this slot is boolean
+                    then:
+                      - call: run_diagnostics # Second call
+                        next:
+                          - if: slots.network_speed > 100
+                            then:
+                              - action: action_sleep_few_sec
+                              - action: utter_speed_issue_resolved
+                                next: "END" # this has to be added, either next END to explain the flow end or point to another section
+                          - else:
+                            - action: action_sleep_few_sec
+                            - action: utter_speed_issue_not_resolved
+                            - call: reset_router
+                            - action: utter_final_diagnistics_run
+                            - call: run_diagnostics # Third call
+                              next:
+                                - if: slots.network_speed < 100
+                                  then:
+                                    - action: utter_acknowledge_speed_test_not_good
+                                    - action: utter_fail_to_find_fix
+                                    - link: human_handoff # when you link a flow, you go to the child flow and then the flow ends there.
+                                - else:
+                                  - action: action_sleep_few_sec
+                                  - action: utter_final_try_worked
+                                  - action: utter_speed_issue_resolved
+                                    next: "END"
+
+
+                  - else:
+                    - link: human_handoff
+          - else:
+            - action: utter_speed_network_not_issue
+            - action: action_sleep_few_sec
+            - action: utter_propose_other_solutions
+            - action: action_sleep_few_sec
+            - collect: more_help_needed
+              next:
+                - if: slots.more_help_needed
+                  then:
+                    - link: human_handoff
+                - else:
+                  - action: action_sleep_few_sec
+                  - action: utter_final_help
+                    next: "END"
+
+
+  run_diagnostics:
+    if: False # Conditional check – this flow will not run unless this condition is verified.
+              #when it is False this means this flow will only be run if it is called by another flow, not the user.
+    description: run diagnostics to check the internet speed for the user
+    steps:
+      - action: utter_communicate_run_diagnosticss
+      - action: actions_run_speed_test

rasa/cli/project_templates/telco/docs/docs.md

@@ -0,0 +1,8 @@
+## 📂 `docs/` – The Agent's Knowledge Base (optional)
+
+If your agent answers knowledge-based questions (FAQs, policies, etc.), you can put markdown, PDFs, or text files in this folder. Rasa can use this content for retrieval-augmented responses if set up with a vector store [2](https://rasa.com/docs/pro/build/retrieval-actions).
+
+**What you'll find:**
+- **network/**: Technical documentation for network troubleshooting and diagnostics
+
+**Edit here** to update what your agent can retrieve and summarize for users.

rasa/cli/project_templates/telco/docs/network/reset_vs_rboot_router.txt

@@ -0,0 +1 @@
+Rebooting a router means simply turning it off and back on without changing any settings. This helps resolve temporary issues like slow speeds or dropped connections and is done by pressing the power button or unplugging the device for a few seconds before turning it back on. Resetting a router, on the other hand, restores it to factory settings, erasing all custom configurations such as the Wi-Fi name, password, and advanced settings. This is done by holding the reset button for about 10-30 seconds until the router restarts. While rebooting is a quick fix for minor issues, resetting should only be done as a last resort when troubleshooting persistent problems.

rasa/cli/project_templates/telco/docs/network/restart_router.txt

@@ -0,0 +1,6 @@
+Here are concise summaries of how to turn your router on and off:
+Using the Power Button: Press the power button to turn off the router, wait 30 seconds, then press it again to turn it back on.
+Unplugging Method: Disconnect the power cable, wait 30 seconds, then plug it back in to restart the router.
+Full Restart for Issues: Turn off the router, wait 1 minute, then turn it back on to refresh the connection.
+
+To turn your router off, press the power button (if available) or unplug it from the power source. Wait about 30 seconds to 1 minute before turning it back on by pressing the power button again or plugging it back in. This helps refresh the connection and resolve minor network issues.

rasa/cli/project_templates/telco/docs/network/run_speed_test.txt

@@ -0,0 +1,6 @@
+Speed test is run by a special software to check what is the current speed of your Internet when uploading or downloading files
+You can use "Fast.com", "Speedtest.net", or Google "Internet speed test"
+An internet speed test measures your connection's performance by evaluating download and upload speeds (Mbps), ping (latency in ms), and jitter.
+It helps determine how fast data is sent and received, impacting streaming, gaming, and video calls.
+Speed tests are useful for diagnosing slow connections and verifying ISP performance.
+You can use our App for a speed test. Go to the Home menu, select WLAN speed test and run it.

rasa/cli/project_templates/telco/domain/billing/understand_bill.yml

@@ -0,0 +1,102 @@
+actions:
+  - action_get_customer_info
+  - action_verify_bill_by_date
+  - action_recap_bill
+
+slots:
+  bill_month:
+    type: categorical
+    mappings:
+      - type: from_llm
+    values:
+      - January
+      - February
+      - March
+      - April
+      - May
+      - June
+      - July
+      - August
+      - September
+      - October
+      - November
+      - December
+
+  bill_amount:
+    type: float
+    mappings:
+      - type: controlled
+
+  user_authenticated:
+    type: bool
+    mappings:
+      - type: controlled
+    initial_value: True
+
+  average_bill:
+      type: float
+      mappings:
+        - type: controlled
+
+  difference:
+      type: float
+      mappings:
+        - type: controlled
+
+  breakdown_cost:
+      type: bool
+      mappings:
+        - type: from_llm
+
+  issue_solved:
+      type: bool
+      mappings:
+        - type: from_llm
+
+  more_bill_details:
+      type: bool
+      mappings:
+        - type: from_llm
+
+responses:
+  utter_ask_customer_id:
+    - text: |
+        Can you please provide me your customer id?
+
+  utter_ask_bill_month:
+    - text: |
+        Alright. Could you please specify the month? 📅
+
+  utter_ask_breakdown_cost:
+    - text: |
+        Would you like to see the breakdown of the costs?
+      buttons:
+        - title: "Yes, please"
+          payload: "/SetSlots(breakdown_cost=True)"
+        - title: "No, all good"
+          payload: "/SetSlots(breakdown_cost=False)"
+
+  utter_ask_issue_solved:
+    - text: |
+        Did I manage to provide all the information you need?
+      buttons:
+        - title: "Yes, all good"
+          payload: "/SetSlots(issue_solved=True)"
+        - title: "No, I need further help"
+          payload: "/SetSlots(issue_solved=False)"
+
+  utter_ask_more_bill_details:
+      - text: |
+          You can see more details in your account.
+          Would you like a link to the overview that contains all your bills?
+        buttons:
+        - title: "Yes, please"
+          payload: "/SetSlots(more_bill_details=True)"
+        - title: "No, it's enough"
+          payload: "/SetSlots(more_bill_details=False)"
+
+  utter_provide_bill_sources:
+      - text: |
+          I've provided a quick summary of your bill ⤵️
+          For full details, please log in to your account and check your billing history here:
+          https://companyName/account/your-bills 🔗

rasa/cli/project_templates/telco/domain/domain.md

@@ -0,0 +1,13 @@
+## 📂 `domain/` – The Agent's Brain
+
+This folder contains YAML files that define the telecom agent's:
+- **Slots**: The agent's memory (e.g., customer account, service status, network diagnostics) [1](https://rasa.com/docs/reference/primitives/slots/).
+- **Responses**: The messages your agent can say to customers (e.g., greetings, service confirmations, technical explanations) [2](https://rasa.com/docs/reference/primitives/responses).
+- **Actions**: Custom logic your agent can run (e.g., running network diagnostics, checking service status) [3](https://rasa.com/docs/reference/primitives/custom-actions).
+
+**What you'll find:**
+- **billing/**: Domain configuration for billing and payment features
+- **network/**: Domain setup for network diagnostics and troubleshooting
+- **general/**: General telecom customer service domain elements
+
+You can organize the domain as one big file or many small ones. Rasa will automatically merge everything during training [1](https://rasa.com/docs/reference/config/domain).

rasa/cli/project_templates/telco/domain/general/bot_challenge.yml

@@ -0,0 +1,4 @@
+
+responses:
+  utter_bot_challenge:
+    - text: "You got it - I’m a virtual agent. I’ll do my best to help with your internet or mobile plan."

rasa/cli/project_templates/telco/domain/general/feedback.yml

@@ -0,0 +1,25 @@
+slots:
+  feedback_rating:
+    type: categorical
+    values: [thumbs_up, thumbs_down]
+    mappings:
+      - type: from_llm
+
+responses:
+  utter_ask_feedback_rating:
+    - text: "We'd love to hear about your experience! How are we doing?"
+      buttons:
+        - title: "👍 Great"
+          payload: "/SetSlots(feedback_rating=thumbs_up)"
+        - title: "👎 Could be better"
+          payload: "/SetSlots(feedback_rating=thumbs_down)"
+
+  utter_thankyou_positive:
+    - text: "That's wonderful to hear! We appreciate you taking the time to provide us with feedback. 🌟"
+    - text: "So glad we could help! Thanks for the positive feedback! 😊"
+    - text: "Amazing! We're thrilled you had a great experience. Thank you for your feedback! 🎉"
+
+  utter_thankyou_negative:
+    - text: "We appreciate you taking the time to provide us with feedback. We're always working to improve our service."
+    - text: "Thank you for your honest feedback. We'll use it to make our service better."
+    - text: "Thanks for letting us know. Your feedback helps us improve our agent."