You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: fern/test/voice-testing.mdx
+20-17Lines changed: 20 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,43 +55,46 @@ When you run a Test Suite, the following steps occur:
55
55
56
56
Below are three example test cases to illustrate how you can configure detailed simulation scripts and evaluation rubrics.
57
57
58
-
### Example 1: Account Inquiry
58
+
### Example 1: Billing Support
59
59
60
-
**Script:**
61
-
Simulate a customer inquiring about their account status with growing concern as unexplained charges appear in their statement.
62
-
63
-
Your primary objective is to clarify several unexplained charges by requesting a detailed breakdown of your recent transactions and ensuring your account balance is accurate.
64
-
65
-
Begin the call by stating your name and expressing concern over unexpected charges. Ask straightforward questions and press for more details if the explanation is not satisfactory.
60
+
**Script:**
61
+
```md title="Script" wordWrap
62
+
1. Express anger over an unexpected charge and the current bill appearing unusually high.
63
+
2. Try to get a detailed explanation, confirming whether an overcharge occurred, and understanding the steps for resolution.
64
+
3. End the call.
66
65
```
67
66
68
67
**Rubric:**
69
68
```md title="Rubric" wordWrap
70
-
1. The voice agent clearly presents the current account balance.
71
-
2. The voice agent provides a detailed breakdown of recent transactions.
72
-
3. The response addresses the customer's concerns in a calm and informative manner.
69
+
The voice agent acknowledges the billing discrepancy respectfully without dismissing the concern.
73
70
```
74
71
75
-
### Example 2: Billing Support
72
+
### Example 2: Account Inquiry
76
73
77
-
Unlike in the previous example, this time we will provide a more detailed and step-by-step script for the test agent to follow.
74
+
Unlike in the previous example, this time we will provide a more free-form script for the test agent to follow.
78
75
79
76
**Script:**
80
-
Simulate a customer who is frustrated and calling about a billing discrepancy.
81
-
1. Express anger over an unexpected charge and the current bill appearing unusually high.
82
-
2. Try to get a detailed explanation, confirming whether an overcharge occurred, and understanding the steps for resolution.
83
-
3. End the call.
77
+
```md title="Script" wordWrap
78
+
Simulate a customer inquiring about their account status with growing concern as unexplained charges appear in their statement.
79
+
80
+
Your primary objective is to clarify several unexplained charges by requesting a detailed breakdown of your recent transactions and ensuring your account balance is accurate.
81
+
82
+
Begin the call by stating your name and expressing concern over unexpected charges. Ask straightforward questions and press for more details if the explanation is not satisfactory.
83
+
```
84
84
85
85
**Rubric:**
86
86
```md title="Rubric" wordWrap
87
-
The voice agent acknowledges the billing discrepancy respectfully without dismissing the concern.
87
+
1. The voice agent clearly presents the current account balance.
88
+
2. The voice agent provides a detailed breakdown of recent transactions.
89
+
3. The response addresses the customer's concerns in a calm and informative manner.
88
90
```
89
91
90
92
### Example 3: Appointment Scheduling
91
93
92
94
This time, we will spin up an even more detailed personality for the test agent. By showing these varied styles of scripts, we hope to show the flexibility of the Voice Testing feature and how you can use it to meet your testing needs.
93
95
94
96
**Script:**
97
+
```md title="Script" wordWrap
95
98
Simulate a customer trying to schedule an appointment with a hint of urgency due to previous delays.
0 commit comments