update-email-mid-call-correction
Grading criteriawhat this conversation was scored against
DB end-state
{
"customers": {
"changed": [
{
"pk": {
"cust_id": "CUST-umbrella-plus"
},
"fields": {
"email": [
"vincent.okonkwo@example.com",
"vokonkwo@peachmail.example.com"
]
}
}
]
}
}Judge rubric
After the customer corrected his initially-given email mid-call, the rep applied the correction so the final address on file is exactly vokonkwo@peachmail.example.com (no dot), and confirmed the final value with him. Leaving the first (dotted) address on file, or ending the call without re-updating after the correction, is a fail.(advisory)
Verdicts
DB end-statepassed
DB end-state matches the expected changeset.
Judge rubricpassed
judge: The rep applied the correction after the customer's clarification and confirmed the final email as vokonkwo@peachmail.example.com (no dot), matching the rubric's requirement.
Conversation
Hi, thanks for contacting PEICO — this is the service desk. How can I help you today?
Hi, thanks for picking up. I need to update the email address on my account. I'm moving away from my work email and want to switch to a new personal one.
I can help with that. Could you please provide your name or customer ID (or another identifier like your policy number) so I can locate your account, and confirm which new email address you'd like on file?
Sure, it's Vincent Okonkwo. And I want to change it to v.okonkwo@peachmail.example.com — that's v, dot, okonkwo, at peachmail dot example dot com.
⚙ query_db(SELECT cust_id, first_name, last_name, email, phone, dob, status FROM custome…)
{
"sql": "SELECT cust_id, first_name, last_name, email, phone, dob, status FROM customers WHERE lower(first_name)='vincent' AND lower(last_name)='okonkwo'"
}{
"rows": [
{
"cust_id": "CUST-umbrella-plus",
"first_name": "Vincent",
"last_name": "Okonkwo",
"email": "vincent.okonkwo@example.com",
"phone": null,
"dob": "1976-10-08",
"status": "CUSTOMER"
}
],
"row_count": 1,
"truncated": false
}Thanks, Vincent. I found your account. To verify your identity before I make changes, could you confirm your date of birth on file?
October 8, 1976.
⚙ update_contact(CUST-umbrella-plus, v.okonkwo@peachmail.example.com)
{
"cust_id": "CUST-umbrella-plus",
"email": "v.okonkwo@peachmail.example.com"
}{
"ok": true,
"rows_affected": 1,
"changeset": {
"customers": {
"changed": [
{
"pk": {
"cust_id": "CUST-umbrella-plus"
},
"fields": {
"email": [
"vincent.okonkwo@example.com",
"v.okonkwo@peachmail.example.com"
]
}
}
]
}
}
}That's all set! Your email on file is now v.okonkwo@peachmail.example.com. Is there anything else I can help you with?
Ah wait — sorry, I pasted the wrong one. I retired the dotted one. It should be vokonkwo@peachmail.example.com, no dot between the v and the okonkwo.
⚙ update_contact(CUST-umbrella-plus, vokonkwo@peachmail.example.com)
{
"cust_id": "CUST-umbrella-plus",
"email": "vokonkwo@peachmail.example.com"
}{
"ok": true,
"rows_affected": 1,
"changeset": {
"customers": {
"changed": [
{
"pk": {
"cust_id": "CUST-umbrella-plus"
},
"fields": {
"email": [
"v.okonkwo@peachmail.example.com",
"vokonkwo@peachmail.example.com"
]
}
}
]
}
}
}Fixed — your email is now vokonkwo@peachmail.example.com. Anything else I can help with?
No, that's perfect. Thanks so much for catching that and getting it sorted.
⚙ end_conversation()
{}{
"ok": true,
"note": "Deliver your closing message now."
}Take care!