{"id": "A1", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Apex Analytics\nTier: Enterprise ($12,000/month)\nPrimary contact: Rachel Kim, VP of Operations\nAccount history: 18 months, no prior complaints, renews in 3 months\nSituation: Our analytics dashboard was unavailable for 6 hours on Tuesday from 9am-3pm ET during their peak business day.\n\nTheir inbound email (verbatim):\n\"This is unacceptable. We had a quarterly board review at 10am and our team could not access the pipeline data we needed. I had to present stale numbers from last week and it made us look incompetent. We have lost approximately $180,000 in deals that were contingent on data we couldn't access. I am seriously reconsidering our contract renewal next quarter. What are you going to do about this?\"\n\nDraft a response email to Rachel. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Apex Analytics \\u2014 my direct response to Tuesday's outage\\n\\nRachel,\\n\\nTuesday's 6-hour dashboard outage during your board review was a serious failure on our side. I understand it cost you roughly $180k in pipeline value and put you in a position of presenting incomplete data to your board. That should never have happened, and I'm not going to wave off the impact on your team or your standing.\\n\\nHere's what I'm doing:\\n\\n1. I'm issuing a full-month service credit ($12,000) to your next invoice. It will appear on your May bill.\\n2. Our VP of Engineering, David Chen, is preparing a detailed post-mortem on the root cause and the changes we're making. I will send it to you by end of day Friday.\\n3. I'm assigning Sarah Martinez as a dedicated CSM on your account effective today, and I'd like to set up a 30-minute call between you, Sarah, and me next week to walk through the post-mortem and talk about your renewal concerns directly.\\n\\nI won't promise an outage of this length will never happen again \\u2014 that's not something I can guarantee honestly. What I will say is that we'll have clearer escalation and communication in place going forward so you are never left guessing.\\n\\nI'll send a calendar invite over today. Sarah will reach out separately about immediate monitoring.\\n\\nMarcus Chen\\nVP of Customer Success\\nmarcus.chen@apexanalytics.example | Direct: 415-555-0234\", \"metadata\": {\"name\": \"Enterprise SaaS outage during board review\", \"scenario_type\": \"A\", \"customer_name\": \"Rachel Kim\", \"rubric_weights\": {\"A1_specific_impact\": 0.2, \"A2_accountability\": 0.15, \"A3_concrete_action\": 0.15, \"A4_retention_gesture\": 0.15, \"A5_next_steps\": 0.1, \"A6_tone\": 0.15, \"A7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"blames engineering / vendor / infrastructure / unexpected circumstances\", \"promises 'will never happen again' or absolute promise\", \"uses phrase 'sorry you feel that way' or 'sorry you experienced'\", \"ignores the customer's specific quantified impact\", \"asks for feedback / NPS / survey in a complaint email\", \"uses 'unfortunately' more than once\"], \"baseline_score\": null}}"}
{"id": "A2", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Brightline Health Network\nTier: Enterprise Healthcare ($45,000/month)\nPrimary contact: Dr. Priya Desai, Chief Medical Information Officer\nAccount history: 2 years, major reference customer\nSituation: Our scheduling platform was unavailable for 4 hours on Monday morning. Hospital staff could not access operating room schedules, which delayed 3 non-critical surgeries and forced clinicians to use paper fallbacks.\n\nTheir inbound email (verbatim):\n\"Your outage this morning was genuinely dangerous. We delayed three surgical cases because our OR coordinators could not pull schedules. We used paper forms \u2014 which, as you know, introduces HIPAA documentation risk for us. I have already briefed my CEO and our legal team is reviewing our contract. I need to know what happened, what you are doing about it, and whether we can still trust your platform for clinical operations.\"\n\nDraft a response email to Dr. Desai. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Brightline Health \\u2014 Monday's outage and our response\\n\\nDr. Desai,\\n\\nMonday morning's 4-hour outage delayed three surgical cases and forced your OR coordinators onto paper fallbacks. I understand that carries real patient-safety weight and creates HIPAA documentation exposure on your side. I'm treating this with the seriousness it deserves.\\n\\nConcretely:\\n\\n1. I'm crediting 25% of your May invoice ($11,250) against the direct operational disruption. Our Finance team will process it this week.\\n2. Our Head of Clinical Engineering, Jamie Torres, will deliver a written root-cause analysis to you and your legal team by Thursday. It will include the audit trail of what happened during the paper-fallback window so your compliance review has the evidence it needs.\\n3. I'd like to schedule a 45-minute review this week with you, Jamie, and whoever on your side should be in the room. I can come on-site Thursday or Friday, or we can do it by video.\\n\\nI am not going to tell you this won't happen again in 4 hours' worth of uptime commitments \\u2014 you deserve more honesty than that. What I can commit to is a specific change to our clinical-tier incident protocol so that a healthcare customer in the middle of surgical scheduling is paged first and routed a direct bridge, not a status page.\\n\\nPlease tell me whether you prefer Thursday or Friday for the review. I will put time on both calendars tonight either way.\\n\\nAlicia Brennan\\nHead of Customer Success, Clinical\\nalicia.brennan@brightlinehealth.example | Direct: 617-555-0118\", \"metadata\": {\"name\": \"Healthcare SaaS delayed surgery scheduling\", \"scenario_type\": \"A\", \"customer_name\": \"Dr. Priya Desai\", \"rubric_weights\": {\"A1_specific_impact\": 0.2, \"A2_accountability\": 0.15, \"A3_concrete_action\": 0.15, \"A4_retention_gesture\": 0.15, \"A5_next_steps\": 0.1, \"A6_tone\": 0.15, \"A7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"blames engineering / vendor / infrastructure / unexpected circumstances\", \"promises 'will never happen again' or absolute promise\", \"uses phrase 'sorry you feel that way' or 'sorry you experienced'\", \"ignores the customer's specific quantified impact\", \"asks for feedback / NPS / survey in a complaint email\", \"uses 'unfortunately' more than once\"], \"baseline_score\": null}}"}
{"id": "A3", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Meridian Logistics\nTier: Mid-market ($8,500/month)\nPrimary contact: Tomas Lindqvist, Head of Operations\nAccount history: 14 months, recently expanded usage\nSituation: Our shipping API had intermittent failures for 8 hours overnight. The customer's warehouses missed dispatch cutoffs, resulting in ~$45,000 in contractual late-delivery fees to their downstream partners.\n\nTheir inbound email (verbatim):\n\"I just got off a call with two of our downstream partners who are charging us $45k in late-delivery penalties because your API went sideways overnight and our dispatch system couldn't confirm shipments. This is the second incident in two months. I want to move back to our previous provider before our renewal. What is your plan?\"\n\nDraft a response email to Tomas. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Meridian Logistics \\u2014 overnight API incident and next steps\\n\\nTomas,\\n\\nOvernight's API failures cost you $45k in downstream penalties and put you in a position where you had to explain our problem to your partners. That is on us \\u2014 especially after the earlier incident this quarter. You're right to be having this conversation.\\n\\nHere is what we are doing:\\n\\n1. I'm issuing a $15,000 credit against your next invoice. That reflects a full-month service credit plus a partial offset against the $45k in penalties you absorbed. It will show up on your May bill.\\n2. Our API reliability lead, Priya Ramesh, will send you a written post-mortem by Wednesday covering both overnight's failure and the earlier incident, and the specific changes we are putting in place this month.\\n3. I'd like a 30-minute call with you, Priya, and me this week so I can walk you through the plan and you can push back on any of it before your renewal decision. I can come to your office or take it by video.\\n\\nI won't make uptime promises I can't keep in writing. What I will do is commit to a specific escalation path for your account so overnight failures get a direct page to engineering, not a wait for morning.\\n\\nPlease send me two times this week that work for the review. I'll clear my schedule for whichever you pick.\\n\\nDana Osei\\nDirector of Customer Success\\ndana.osei@meridianlogistics.example | Direct: 312-555-0447\", \"metadata\": {\"name\": \"Logistics API outage causing shipment delays\", \"scenario_type\": \"A\", \"customer_name\": \"Tomas Lindqvist\", \"rubric_weights\": {\"A1_specific_impact\": 0.2, \"A2_accountability\": 0.15, \"A3_concrete_action\": 0.15, \"A4_retention_gesture\": 0.15, \"A5_next_steps\": 0.1, \"A6_tone\": 0.15, \"A7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"blames engineering / vendor / infrastructure / unexpected circumstances\", \"promises 'will never happen again' or absolute promise\", \"uses phrase 'sorry you feel that way' or 'sorry you experienced'\", \"ignores the customer's specific quantified impact\", \"asks for feedback / NPS / survey in a complaint email\", \"uses 'unfortunately' more than once\"], \"baseline_score\": null}}"}
{"id": "A4", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Fieldstone Realty Group\nTier: Growth ($2,400/month, 40 seats)\nPrimary contact: Jasmine Chen, Managing Broker\nAccount history: 9 months, high-volume user during weekend\nSituation: Our lead-tracking module was broken Saturday and Sunday during peak open-house hours. Their agents could not log prospect visits in real time and estimate they lost roughly 12 qualified leads across 3 listings.\n\nTheir inbound email (verbatim):\n\"This weekend was a disaster. My agents ran open houses at three listings and your lead tracker was down the entire time. We lost roughly twelve qualified prospects because agents could not capture contact info on the spot and followed up too late or not at all. I am not paying this month's invoice. I want you to explain what happened and why I should stay with you for the rest of the year.\"\n\nDraft a response email to Jasmine. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Fieldstone \\u2014 this weekend's outage and my direct response\\n\\nJasmine,\\n\\nSaturday and Sunday were the worst possible 48 hours for that feature to fail. I understand your agents were running open houses live and lost around twelve qualified prospects because the lead tracker would not capture. That is real pipeline you can't get back and I'm not going to pretend otherwise.\\n\\nHere is what I'm doing:\\n\\n1. I am waiving this month's invoice in full. You will not see a May charge on your account \\u2014 I've already flagged it with our billing team.\\n2. Our engineering lead, Kwame Boateng, will send you a written summary by Wednesday of what failed, why, and the change we are making so open-house weekends don't land in our deploy windows again.\\n3. I'd like a 20-minute call with you this week \\u2014 just us \\u2014 so I can answer the second part of your question honestly and you can decide from there whether it makes sense to stay.\\n\\nI won't tell you this can't happen again. What I can do is make sure high-volume weekend users like Fieldstone are flagged inside our release process so we don't ship changes into your peak hours.\\n\\nPlease send me two windows this week and I'll clear whichever works best.\\n\\nMiriam Okafor\\nCustomer Success Director\\nmiriam.okafor@fieldstone.example | Direct: 206-555-0311\", \"metadata\": {\"name\": \"Real-estate lead tracker down during open-house weekend\", \"scenario_type\": \"A\", \"customer_name\": \"Jasmine Chen\", \"rubric_weights\": {\"A1_specific_impact\": 0.2, \"A2_accountability\": 0.15, \"A3_concrete_action\": 0.15, \"A4_retention_gesture\": 0.15, \"A5_next_steps\": 0.1, \"A6_tone\": 0.15, \"A7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"blames engineering / vendor / infrastructure / unexpected circumstances\", \"promises 'will never happen again' or absolute promise\", \"uses phrase 'sorry you feel that way' or 'sorry you experienced'\", \"ignores the customer's specific quantified impact\", \"asks for feedback / NPS / survey in a complaint email\", \"uses 'unfortunately' more than once\"], \"baseline_score\": null}}"}
{"id": "A5", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: NovaPay Financial\nTier: Enterprise Fintech ($28,000/month)\nPrimary contact: Alex Navarro, VP of Risk & Compliance\nAccount history: 11 months, regulated financial institution\nSituation: A display bug in our dashboard showed incorrect transaction amounts for roughly 3 hours yesterday. The underlying ledger was correct, but the UI displayed wrong figures. The customer's compliance team flagged ~$2.3M in transactions for review before realizing the display was the issue.\n\nTheir inbound email (verbatim):\n\"For three hours yesterday your dashboard displayed transaction amounts that did not match the underlying ledger. My compliance team had to open reviews on $2.3M of activity before we figured out the display itself was wrong. I now have to explain to our state regulator why my audit trail shows three hours of apparent anomaly. I need documentation I can hand to examiners, and I need to know whether we can keep you as our vendor of record.\"\n\nDraft a response email to Alex. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: NovaPay \\u2014 display defect documentation + next steps\\n\\nAlex,\\n\\nYesterday's 3-hour display defect pushed your compliance team into $2.3M of unnecessary review and left you with an anomaly window you now have to explain to examiners. I understand the practical and regulatory weight of that, and I'm treating this as a priority-one item on my side.\\n\\nConcretely:\\n\\n1. I'm having our engineering team prepare an attestation letter for your examiner file by Thursday. It will cover: the exact time window, the scope of the display defect, the confirmation that the underlying ledger was never affected, and the verification that your team actually used to confirm that. Signed by our VP of Engineering.\\n2. I am issuing a full-month service credit ($28,000) against your next invoice.\\n3. I'd like to schedule a 45-minute working session this week with you, our VP of Engineering Rahim Khan, and your compliance lead to review the attestation letter together and answer any examiner questions you anticipate.\\n\\nI'm not going to promise we won't have another defect. What I will commit to is a specific change: your account gets flagged in our pre-deploy review so that any UI change touching financial displays goes through a second review gate before release.\\n\\nPlease pass me your examiner's timeline and two windows this week for the working session. I'll make whichever window you pick work.\\n\\nLena Park\\nEnterprise Customer Success Director\\nlena.park@novapay.example | Direct: 646-555-0789\", \"metadata\": {\"name\": \"Fintech wrong transaction amounts triggering compliance flag\", \"scenario_type\": \"A\", \"customer_name\": \"Alex Navarro\", \"rubric_weights\": {\"A1_specific_impact\": 0.2, \"A2_accountability\": 0.15, \"A3_concrete_action\": 0.15, \"A4_retention_gesture\": 0.15, \"A5_next_steps\": 0.1, \"A6_tone\": 0.15, \"A7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"blames engineering / vendor / infrastructure / unexpected circumstances\", \"promises 'will never happen again' or absolute promise\", \"uses phrase 'sorry you feel that way' or 'sorry you experienced'\", \"ignores the customer's specific quantified impact\", \"asks for feedback / NPS / survey in a complaint email\", \"uses 'unfortunately' more than once\"], \"baseline_score\": null}}"}
{"id": "B1", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Samantha Reed, solo practitioner (2-person law firm)\nPlan: Pro tier ($149/month)\nRequest: downgrade to Starter tier ($49/month) mid-cycle and receive a prorated refund for the unused portion.\nPolicy: prorated refunds on tier downgrades within a month are standard and automatic when processed within 30 days.\n\nTheir inbound email (verbatim):\n\"Hi \u2014 I upgraded to Pro about two weeks ago to handle a case matter that has since wrapped up. I'd like to move back down to Starter and get a prorated refund for the remaining two weeks. Can you process that?\"\n\nDraft a response email to Samantha. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Your tier change and prorated refund\\n\\nHi Samantha,\\n\\nHappy to take care of this. I've moved your account back to the Starter tier effective today, and you'll see a prorated refund of $71.60 back to the card on file within 3 to 5 business days. That covers the unused 14 days of your Pro subscription.\\n\\nNothing else on your end \\u2014 your matter history and documents stay exactly where they are, and all of your existing integrations keep working. You'll see the lower Starter rate on your next billing cycle on May 3.\\n\\nIf you need Pro again down the line for another matter, you can upgrade at any time from your account settings, and we'll pick up where we left off.\\n\\nLet me know if you need anything else.\\n\\nJordan Bates\\nCustomer Care Team\\njordan.bates@reedlaw.example\", \"metadata\": {\"name\": \"Prorated refund after mid-month tier downgrade\", \"scenario_type\": \"B\", \"customer_name\": \"Samantha Reed\", \"rubric_weights\": {\"B1_clear_confirmation\": 0.25, \"B2_warm_not_grovelling\": 0.15, \"B3_timing_and_mechanism\": 0.15, \"B4_next_interaction_clear\": 0.1, \"B5_no_upsell\": 0.1, \"B6_personalization\": 0.15, \"B7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"over-apologizes for a routine granted request\", \"asks for NPS / survey / feedback in the email\", \"attempts upsell or cross-sell\", \"implies the customer is unusual for making this request\", \"uses corporate hedging like 'as a one-time exception' when it is not\"], \"baseline_score\": null}}"}
{"id": "B2", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Northpeak Construction Management (mid-market, 80 seats)\nPrimary contact: Marcus Whitfield, COO\nSituation: Their scheduled onboarding implementation call with our solutions engineer was canceled by us (SE had a family emergency). We rescheduled, but the customer was already onsite with their team for the session.\nRequest: asking for a credit to cover the lost hour for their team.\nPolicy: a one-time goodwill credit up to $500 is within CS discretion for service-delivery issues.\n\nTheir inbound email (verbatim):\n\"We had six people in a conference room ready for this morning's implementation call and got the cancellation note fifteen minutes before. I'm glad to reschedule but that was an hour of six people's time. Is there anything you can do on your side?\"\n\nDraft a response email to Marcus. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: This morning's canceled session \\u2014 credit on the way\\n\\nMarcus,\\n\\nThanks for flagging this directly. Cancelling fifteen minutes before with six of your team already in the room is a real cost, and I want to make it right.\\n\\nI've applied a $500 service credit to your account \\u2014 it will show on your June 1 invoice. You don't need to do anything to redeem it.\\n\\nOn rescheduling: our SE Priya will be back on deck Thursday, and she's already blocked Friday 9am-11am and Monday 1pm-3pm as options. Pick whichever works for your team and I'll lock it in, or send me two other windows if neither fits.\\n\\nSorry for the scramble today. Please pass along the reschedule preference when you have a moment.\\n\\nTomas Rivera\\nImplementation Customer Success\\ntomas.rivera@northpeakcm.example\", \"metadata\": {\"name\": \"Goodwill credit for canceled implementation call\", \"scenario_type\": \"B\", \"customer_name\": \"Marcus Whitfield\", \"rubric_weights\": {\"B1_clear_confirmation\": 0.25, \"B2_warm_not_grovelling\": 0.15, \"B3_timing_and_mechanism\": 0.15, \"B4_next_interaction_clear\": 0.1, \"B5_no_upsell\": 0.1, \"B6_personalization\": 0.15, \"B7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"over-apologizes for a routine granted request\", \"asks for NPS / survey / feedback in the email\", \"attempts upsell or cross-sell\", \"implies the customer is unusual for making this request\", \"uses corporate hedging like 'as a one-time exception' when it is not\"], \"baseline_score\": null}}"}
{"id": "B3", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Hiroko Tanaka, individual consultant\nPlan: Pro Annual ($1,188 prepaid, day 18 of use)\nRequest: full refund \u2014 signed up for an annual plan, realized within a couple of weeks the product doesn't fit her workflow.\nPolicy: full refund within the 30-day money-back guarantee. Automatic approval.\n\nTheir inbound email (verbatim):\n\"Hello. I signed up for the annual Pro plan on the 12th but I've realized over the last two weeks that my workflow relies on features that are on your roadmap but not live yet. I'd like to cancel and receive a refund if that's possible under your 30-day guarantee. Thank you.\"\n\nDraft a response email to Hiroko. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Your refund is on the way\\n\\nHi Hiroko,\\n\\nYes \\u2014 you're well within the 30-day window and I've processed a full refund of $1,188 back to the card on file. You'll see it land in 5 to 7 business days depending on your bank.\\n\\nI've also closed your account as of today. Your data is retained for 90 days in case you want it exported \\u2014 just reply here if you want me to set that up.\\n\\nIf the features you were looking for ship later this year, I'll make sure you hear about it from me directly rather than through marketing. Just let me know if you'd like that.\\n\\nThanks for giving us a shot, and sorry we didn't quite fit this time.\\n\\nDevon Ashby\\nCustomer Care\\ndevon.ashby@product.example\", \"metadata\": {\"name\": \"Refund within 30-day trial window\", \"scenario_type\": \"B\", \"customer_name\": \"Hiroko Tanaka\", \"rubric_weights\": {\"B1_clear_confirmation\": 0.25, \"B2_warm_not_grovelling\": 0.15, \"B3_timing_and_mechanism\": 0.15, \"B4_next_interaction_clear\": 0.1, \"B5_no_upsell\": 0.1, \"B6_personalization\": 0.15, \"B7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"over-apologizes for a routine granted request\", \"asks for NPS / survey / feedback in the email\", \"attempts upsell or cross-sell\", \"implies the customer is unusual for making this request\", \"uses corporate hedging like 'as a one-time exception' when it is not\"], \"baseline_score\": null}}"}
{"id": "B4", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Horizon Biotech (research company, 200 employees)\nPrimary contact: Rahul Khanna, Director of IT\nPlan: 14-day free trial, currently on day 10\nRequest: 14 additional trial days to finish a proof-of-concept with their scientific computing group.\nPolicy: sales-assisted trials can be extended up to 30 additional days at CS/AE discretion for enterprise evaluations.\n\nTheir inbound email (verbatim):\n\"We started the trial ten days ago specifically to validate whether your platform can handle our GPU cluster workload. Our HPC team hit some scheduling conflicts and only started real testing two days ago. Would it be possible to get another two weeks so we can finish the proof-of-concept before making a purchase recommendation?\"\n\nDraft a response email to Rahul. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Trial extended through May 12 \\u2014 run your PoC\\n\\nRahul,\\n\\nYes \\u2014 I've extended your trial by 14 days, running through May 12. Nothing you need to do on your end; the same accounts and workspaces stay active, and any outputs you've generated so far carry forward.\\n\\nA couple of things that might save your HPC team time in the next two weeks: our head solutions engineer, Anya Lin, worked on a similar GPU scheduling PoC with a Horizon peer last quarter and can walk through the specific config choices if useful. She has two hours this Thursday and three on Friday that she's happy to give you. Say the word and I'll put a hold on calendars.\\n\\nOnce you wrap the PoC, let me know what you need from my side to support the purchase recommendation internally \\u2014 reference architecture docs, case studies, contract templates, whatever. Happy to get those over.\\n\\nGood luck with the testing.\\n\\nElena Voss\\nEnterprise Sales Engineering\\nelena.voss@horizonbio.example\", \"metadata\": {\"name\": \"Extended trial for proof-of-concept\", \"scenario_type\": \"B\", \"customer_name\": \"Rahul Khanna\", \"rubric_weights\": {\"B1_clear_confirmation\": 0.25, \"B2_warm_not_grovelling\": 0.15, \"B3_timing_and_mechanism\": 0.15, \"B4_next_interaction_clear\": 0.1, \"B5_no_upsell\": 0.1, \"B6_personalization\": 0.15, \"B7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"over-apologizes for a routine granted request\", \"asks for NPS / survey / feedback in the email\", \"attempts upsell or cross-sell\", \"implies the customer is unusual for making this request\", \"uses corporate hedging like 'as a one-time exception' when it is not\"], \"baseline_score\": null}}"}
{"id": "B5", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Seabright Marketing (agency, Team tier, 25 seats)\nPrimary contact: Andrea Ch\u00e1vez, Office Manager\nRequest: Their head of content left the company. They want to transfer the unused portion of that seat's month (18 days) to their new replacement hire joining in two weeks.\nPolicy: prorated seat credits can be transferred to a new user within the same billing cycle.\n\nTheir inbound email (verbatim):\n\"Hi \u2014 our head of content Leo Park left the agency on Friday, so his seat is unused starting today. We have a replacement hire starting in two weeks. Is there a way to transfer the unused portion of Leo's seat onto the new hire when she starts, or do we need to just eat the cost? Thanks.\"\n\nDraft a response email to Andrea. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Transferring Leo's unused seat to your new hire\\n\\nHi Andrea,\\n\\nYes \\u2014 happy to transfer the unused portion of Leo's seat. I've deactivated Leo's account today and credited your account $42.80 (the prorated 18 unused days). When your new hire starts in two weeks, the credit will be applied automatically to her first month's seat charge.\\n\\nWhen she's ready to onboard, just send her email address here and I'll provision her seat myself so you don't have to chase it. She'll get the standard onboarding flow and her seat will pick up the credit in the background \\u2014 nothing extra to do on your side.\\n\\nIf you need Leo's account exported for archival or handoff purposes, reply here and I'll set that up before the 90-day retention window closes.\\n\\nIngrid Martin\\nCustomer Success\\ningrid.martin@seabrightmarketing.example\", \"metadata\": {\"name\": \"Transfer unused seat credits after user offboarding\", \"scenario_type\": \"B\", \"customer_name\": \"Andrea Ch\\u00e1vez\", \"rubric_weights\": {\"B1_clear_confirmation\": 0.25, \"B2_warm_not_grovelling\": 0.15, \"B3_timing_and_mechanism\": 0.15, \"B4_next_interaction_clear\": 0.1, \"B5_no_upsell\": 0.1, \"B6_personalization\": 0.15, \"B7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"over-apologizes for a routine granted request\", \"asks for NPS / survey / feedback in the email\", \"attempts upsell or cross-sell\", \"implies the customer is unusual for making this request\", \"uses corporate hedging like 'as a one-time exception' when it is not\"], \"baseline_score\": null}}"}
{"id": "C1", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Verity Analytics (20-person shop)\nPrimary contact: Nathan Brooks, Co-founder\nSituation: They have used the product actively for 6 months (logins, invoices, feature use). They recently pivoted their business strategy and no longer need the platform.\nRequest: full refund of the 6 months they've paid ($4,470).\nPolicy: no refunds beyond the initial 30-day guarantee for actively-used accounts. We can stop billing going forward and offer export support, but we cannot retroactively refund active use.\n\nTheir inbound email (verbatim):\n\"We've decided to pivot and your platform isn't part of our new direction. I'd like a full refund of what we've paid so far. We're a small company, every dollar matters, and it feels fair given we're not going to keep using you.\"\n\nDraft a response email to Nathan. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Your cancellation and what I can help with\\n\\nNathan,\\n\\nGood luck with the pivot \\u2014 that's a real reset and I'm glad you reached out directly.\\n\\nI can't refund the six months of active use \\u2014 our refund window is the first 30 days, and beyond that we don't retroactively refund subscriptions that have been used in the ordinary course. I'd love to dress that up differently, but I don't want to waste your time.\\n\\nHere's what I CAN do, which I think actually lands closer to what you need:\\n\\n1. I'll cancel your account effective immediately so you stop being billed going forward. You won't see another charge.\\n2. Your data is retained for 90 days. I can schedule a full export of everything you have in the platform \\u2014 reports, saved queries, uploaded datasets \\u2014 and send it to you as a download. Just say go and I'll start it today.\\n3. If your pivot lands you in a space where our platform fits again in the future, come back through me directly and I'll personally onboard you and we'll credit you up to a month to re-ramp. That's the realistic door I can leave open.\\n\\nIf you'd like me to process the export, reply here and I'll kick it off today. Otherwise just let me know if there's anything else I can do as you close this out.\\n\\nBest of luck.\\n\\nRay Ibarra\\nCustomer Success\\nray.ibarra@verityanalytics.example\", \"metadata\": {\"name\": \"Full refund after 6 months of active use\", \"scenario_type\": \"C\", \"customer_name\": \"Nathan Brooks\", \"rubric_weights\": {\"C1_clear_early_no\": 0.2, \"C2_rationale_no_jargon\": 0.15, \"C3_alternatives_in_power\": 0.2, \"C4_empathetic_not_dismissive\": 0.15, \"C5_no_over_apologizing\": 0.1, \"C6_door_open_appropriately\": 0.1, \"C7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"hides behind policy jargon or legalese instead of explaining\", \"dismisses the customer's goal\", \"uses 'unfortunately' more than twice\", \"makes a firm 'no' sound like a 'maybe' to avoid conflict\", \"implies the customer misunderstood their own request\", \"ends with a hard door-slam / 'do not contact us about this'\"], \"baseline_score\": null}}"}
{"id": "C2", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Cedar & Co Interior Design Studio (4 seats)\nPrimary contact: Vanessa Orellana, Principal\nSituation: They're currently on our Team tier ($299/month). We deprecated our 'Boutique' tier (4 seats for $129/month) 18 months ago. Current customers who were on it got grandfathered but no new signups. Vanessa heard about it from a peer.\nRequest: move to the Boutique tier since they would qualify for it if it still existed.\nPolicy: the deprecated tier cannot be reopened for new customers. We do offer a 10% annual-prepay discount on Team tier that we can honor.\n\nTheir inbound email (verbatim):\n\"A friend of mine who runs a similar-sized studio told me you have a 'Boutique' plan for small firms at $129 per month. I'm paying $299 on Team tier right now and that's materially more than I can justify. Can you put me on the Boutique plan? I'm a four-person studio which sounds like exactly what it's for.\"\n\nDraft a response email to Vanessa. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Boutique tier and what I can do instead\\n\\nVanessa,\\n\\nI can't move you to the Boutique tier \\u2014 it's a closed program. We retired it for new signups a while back and we only honor it for studios who were already on it at that point. Your friend happens to have been one of them. I know that's not the answer you were hoping to hear.\\n\\nHere's what I CAN do:\\n\\n1. If you prepay annually, I can drop your Team rate by 10% \\u2014 that's $269/month effective rate instead of $299, which saves you roughly $360 over the year.\\n2. If your usage is really concentrated on two or three of the Team features, it's worth us getting on a 15-minute call to see whether Starter tier (2 seats) plus an add-on makes more sense for your actual workflow. Sometimes it does, sometimes it doesn't \\u2014 I'd rather we figure that out honestly than have you paying for seats you don't use.\\n3. If you'd like, I can put you on the list to hear first if we ever reopen a small-firm plan. I can't promise that will happen, but you'd hear about it from me directly.\\n\\nLet me know if either of the first two sounds worth exploring and I'll send calendar times or the annual-prepay paperwork, whichever.\\n\\nSofia Malik\\nCustomer Success\\nsofia.malik@cedarstudio.example\", \"metadata\": {\"name\": \"Request to restore deprecated pricing tier\", \"scenario_type\": \"C\", \"customer_name\": \"Vanessa Orellana\", \"rubric_weights\": {\"C1_clear_early_no\": 0.2, \"C2_rationale_no_jargon\": 0.15, \"C3_alternatives_in_power\": 0.2, \"C4_empathetic_not_dismissive\": 0.15, \"C5_no_over_apologizing\": 0.1, \"C6_door_open_appropriately\": 0.1, \"C7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"hides behind policy jargon or legalese instead of explaining\", \"dismisses the customer's goal\", \"uses 'unfortunately' more than twice\", \"makes a firm 'no' sound like a 'maybe' to avoid conflict\", \"implies the customer misunderstood their own request\", \"ends with a hard door-slam / 'do not contact us about this'\"], \"baseline_score\": null}}"}
{"id": "C3", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Arrowhead Ventures (small VC firm)\nPrimary contact: Gregory Tan, Operating Partner\nSituation: They're migrating to a specific competitor's CRM (Relay CRM) that has a proprietary import format. They want us to export their data in Relay's native format.\nRequest: native Relay CRM export.\nPolicy: we provide exports in CSV, JSON, and a documented XML schema. We do not build or maintain export adapters for specific competitor formats.\n\nTheir inbound email (verbatim):\n\"We're migrating to Relay CRM next month. Their import is easiest from their native format. Can your team export our data in Relay's native format so we don't have to do mapping work on our side? Their docs say the format is publicly available.\"\n\nDraft a response email to Gregory. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Your migration export \\u2014 what we provide\\n\\nGregory,\\n\\nI can't export in Relay's native format. We stick to CSV, JSON, and our documented XML schema as our export formats \\u2014 building and maintaining adapters for specific third-party tools isn't something we do, and I don't want to half-commit to a one-off that would leave you stuck in the middle of the migration.\\n\\nHere's what I can do that should get you close to the same end state:\\n\\n1. I'll generate a complete export of your account in all three formats we support (CSV, JSON, and our XML schema) and drop it in a secure share this week. You get to pick whichever shape your internal team or a contractor can most easily reshape into Relay's format.\\n2. Relay's public docs list a couple of migration-partner consultancies who specialize in exactly this kind of mapping. I'm happy to pass along the two we've seen other customers get good results from, so you're not scouting vendors cold.\\n3. If your team does the mapping in-house and hits a specific field question about our JSON structure, reply here directly and I'll answer within the business day. I'd rather get you unblocked quickly than have this drag out.\\n\\nLet me know which export format you want first and whether you'd like the consultancy list, and I'll start on it today.\\n\\nHassan El-Sayed\\nCustomer Success\\nhassan.elsayed@arrowheadventures.example\", \"metadata\": {\"name\": \"Data export to an unsupported competitor format\", \"scenario_type\": \"C\", \"customer_name\": \"Gregory Tan\", \"rubric_weights\": {\"C1_clear_early_no\": 0.2, \"C2_rationale_no_jargon\": 0.15, \"C3_alternatives_in_power\": 0.2, \"C4_empathetic_not_dismissive\": 0.15, \"C5_no_over_apologizing\": 0.1, \"C6_door_open_appropriately\": 0.1, \"C7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"hides behind policy jargon or legalese instead of explaining\", \"dismisses the customer's goal\", \"uses 'unfortunately' more than twice\", \"makes a firm 'no' sound like a 'maybe' to avoid conflict\", \"implies the customer misunderstood their own request\", \"ends with a hard door-slam / 'do not contact us about this'\"], \"baseline_score\": null}}"}
{"id": "C4", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: OrionTech Industrial IoT (mid-market)\nPrimary contact: Daniela Krause, Director of Product Integration\nRequest: a custom feature (bidirectional sync with a specific legacy PLC protocol) guaranteed shipped by Q3 so they can include it in their customer-facing SLA.\nPolicy: we don't externally commit to specific feature delivery dates in contracts. Roadmap influence is possible via our partner-advisory program, which gives visibility and early access but not guarantees.\n\nTheir inbound email (verbatim):\n\"We're drafting our own SLA with one of our enterprise customers and we need bidirectional sync for the Allen-Bradley CompactLogix PLC protocol by end of Q3. Can you commit, in our contract, to shipping that by September 30? If so we'll sign a three-year deal this month. If not, we'll have to look at alternatives.\"\n\nDraft a response email to Daniela. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Your PLC sync request \\u2014 honest answer\\n\\nDaniela,\\n\\nI can't put a specific feature delivery date for the Allen-Bradley sync into our contract. We don't externally commit to dated feature deliveries in customer SLAs \\u2014 partly because our roadmap shifts on engineering realities, and partly because I'd rather not have you relying on a promise I can't guarantee will hold. I know that is not the three-year-deal-unlocking answer.\\n\\nHere's what I CAN offer, which I think actually lands closer to what your customer conversation needs:\\n\\n1. I can get you into our Partner Advisory Program. That puts you in monthly calls with our product leadership, gives you visibility into dated roadmap items at our internal specificity, and lets your request weight inform sequencing. You won't get a contractual commitment, but you will get the most accurate signal we can share.\\n2. I can introduce you to two existing customers who integrate our platform with CompactLogix via our generic sync plus a light adapter. It's not what you asked for but it's been in production for about a year at both, and they can tell you what it actually takes.\\n3. If you need a formal letter of intent regarding our investment direction in industrial protocols (not a delivery date), I can get that signed by our CTO. Some customers have successfully used that in their own contracts.\\n\\nIf either of the first two helps, I'll set up a 30-minute call with our Head of Product so we can talk through what a realistic picture looks like. Just say the word.\\n\\nKenji Oyola\\nEnterprise Account Director\\nkenji.oyola@oriontech.example\", \"metadata\": {\"name\": \"Custom feature with guaranteed delivery date\", \"scenario_type\": \"C\", \"customer_name\": \"Daniela Krause\", \"rubric_weights\": {\"C1_clear_early_no\": 0.2, \"C2_rationale_no_jargon\": 0.15, \"C3_alternatives_in_power\": 0.2, \"C4_empathetic_not_dismissive\": 0.15, \"C5_no_over_apologizing\": 0.1, \"C6_door_open_appropriately\": 0.1, \"C7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"hides behind policy jargon or legalese instead of explaining\", \"dismisses the customer's goal\", \"uses 'unfortunately' more than twice\", \"makes a firm 'no' sound like a 'maybe' to avoid conflict\", \"implies the customer misunderstood their own request\", \"ends with a hard door-slam / 'do not contact us about this'\"], \"baseline_score\": null}}"}
{"id": "C5", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Oakhurst Manufacturing (Team plan, 15 seats)\nRequester: Marco Bellanti, Operations Manager at Oakhurst\nSituation: Marco is NOT the current account owner. The current account owner is their IT admin (Tim Brennan), who Marco says is on medical leave and unreachable. Marco wants us to transfer account ownership to himself without Tim's approval so he can manage the platform in Tim's absence.\nPolicy: account ownership changes require verification from the current owner OR, if that's impossible, from a documented secondary admin, OR via a formal written request from a corporate authority with supporting documentation. We don't bypass owner verification on a requester's word alone.\n\nTheir inbound email (verbatim):\n\"Our IT admin Tim Brennan is out on medical leave and we don't know when he's back. I need ownership of our account transferred to me so I can manage billing and user access while he's out. Please make me the admin. This is urgent \u2014 we have users who need access changes today.\"\n\nDraft a response email to Marco. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Account ownership transfer \\u2014 what I can do\\n\\nMarco,\\n\\nI can't just switch the account owner to you on request. Owner changes go through a verification path on purpose \\u2014 mostly because \\\"move the admin rights to me\\\" is exactly what the wrong kind of request looks like too, and we'd be failing Tim and your company if we didn't verify it. I know that's not a convenient answer with users needing changes today.\\n\\nHere are the paths that CAN work, in order of how fast they usually move:\\n\\n1. If Oakhurst set up a secondary admin, I can authorize that person to make the user-access changes you need today and act as owner delegate until Tim is back. Check your admin console or reply here and I'll look up who that is on our side.\\n2. If there's no secondary admin, we can accept a formal request from a corporate authority \\u2014 typically your CFO, COO, or General Counsel \\u2014 on company letterhead asking for a temporary ownership transfer to you, along with a note on Tim's leave. I can turn that around within 24 hours of receiving it.\\n3. As a stopgap right now, I can personally help with urgent user-access changes on the account as a support action \\u2014 deactivating, reactivating, or moving seats \\u2014 if you tell me what needs to happen today. I can't change billing or ownership but I can keep your team unblocked on access while the ownership path resolves.\\n\\nTell me which of those is easiest and I'll move on it immediately. If any of the users need access changes today, send me the specifics and I'll handle them while the ownership path is sorted.\\n\\nHope Tim recovers soon.\\n\\nPriya Desai\\nCustomer Security & Account Support\\npriya.desai@oakhurstmfg.example\", \"metadata\": {\"name\": \"Bypass IT admin for account ownership change\", \"scenario_type\": \"C\", \"customer_name\": \"Marco Bellanti\", \"rubric_weights\": {\"C1_clear_early_no\": 0.2, \"C2_rationale_no_jargon\": 0.15, \"C3_alternatives_in_power\": 0.2, \"C4_empathetic_not_dismissive\": 0.15, \"C5_no_over_apologizing\": 0.1, \"C6_door_open_appropriately\": 0.1, \"C7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"hides behind policy jargon or legalese instead of explaining\", \"dismisses the customer's goal\", \"uses 'unfortunately' more than twice\", \"makes a firm 'no' sound like a 'maybe' to avoid conflict\", \"implies the customer misunderstood their own request\", \"ends with a hard door-slam / 'do not contact us about this'\"], \"baseline_score\": null}}"}
{"id": "D1", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Hannah Cortez, solo consultant (Pro plan, 1 seat)\nSituation: On April 1 her normal monthly charge of $49 posted. On April 18 she upgraded to the Pro Plus plan ($99/month). She was charged a pro-rated amount of $21.00 on April 18 for the remaining 12 days of the billing cycle at the upgraded rate. She believes this $21 charge is a double-billing error.\nReality: the charge is a legitimate pro-rated upgrade charge.\n\nTheir inbound email (verbatim):\n\"I was charged $21.00 on April 18 on top of my regular $49 charge on April 1. Why am I being double-charged? I only have one account. Please refund the $21 charge and explain what went wrong.\"\n\nDraft a response email to Hannah. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: The $21 charge \\u2014 here's what it was\\n\\nHi Hannah,\\n\\nGood news: you weren't double-charged. The $21 on April 18 is a pro-rated upgrade charge, not a duplicate of your April 1 bill. Here's exactly what happened:\\n\\n- April 1: regular Pro plan charge of $49 for the month.\\n- April 18: you upgraded from Pro to Pro Plus. Pro Plus is $99/month. Since there were 12 days left in your billing cycle, you were charged 12/30 of the $99/$49 difference, which works out to $20.00, plus a $1.00 prorate rounding \\u2014 hence $21.00.\\n- Going forward: you'll see the full $99/month Pro Plus rate on May 1, with no additional pro-rations.\\n\\nIf you want to double-check on your end, your billing history is in account settings \\u2192 Billing. You'll see both charges itemized with their descriptions. If the upgrade on April 18 wasn't intentional, I can reverse it today and refund the $21 \\u2014 just reply and let me know.\\n\\nLet me know if that makes sense or if you want me to walk through it differently.\\n\\nCassius Byrd\\nCustomer Care\\ncassius.byrd@product.example\", \"metadata\": {\"name\": \"Thinks they were double-charged (actually pro-rated upgrade)\", \"scenario_type\": \"D\", \"customer_name\": \"Hannah Cortez\", \"rubric_weights\": {\"D1_explicit_correction\": 0.2, \"D2_customer_frame\": 0.15, \"D3_no_condescension\": 0.2, \"D4_evidence_or_verify_path\": 0.1, \"D5_confirms_shared_understanding\": 0.1, \"D6_constructive_next_step\": 0.15, \"D7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"uses 'actually' dismissively\", \"uses 'as I explained' / 'as already stated' / 'per our earlier'\", \"implies the customer did not read the docs / onboarding / terms\", \"uses jargon without plain-language translation\", \"tells the customer they 'misunderstood'\", \"pure info-dump with no conversational close\"], \"baseline_score\": null}}"}
{"id": "D2", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Omar Abdullah, marketing manager at a regional bank\nPlan: Team tier\nSituation: In last week's release, our 'Campaign Scheduler' feature moved from the top-level navigation into the 'Automation' menu. It's still fully available, just one click deeper. Release notes went out but Omar didn't see them.\nReality: feature is alive and well, just in a different menu.\n\nTheir inbound email (verbatim):\n\"Where did Campaign Scheduler go? I used it every week and now I can't find it in the main nav. Did you remove it? We specifically bought Team tier for this feature and if it's gone I need to talk to my account manager about canceling.\"\n\nDraft a response email to Omar. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Campaign Scheduler \\u2014 same feature, new home\\n\\nHi Omar,\\n\\nCampaign Scheduler is still there \\u2014 we moved it, we didn't remove it. As of last week's release it lives inside the 'Automation' menu in the left nav. So instead of being a top-level item, it's one click deeper: Automation \\u2192 Campaign Scheduler. Your saved campaigns, templates, and schedule history are all exactly where you left them.\\n\\nOpen the Automation menu and you should see Campaign Scheduler as the first item. If you'd rather not hunt for it, you can star it inside the Automation menu and it'll show up in your sidebar shortcuts \\u2014 that's the closest thing to how it used to feel.\\n\\nI'm sorry the move wasn't more obvious. We sent release notes but I realize those aren't always the first thing you see. If you want, I can also get you on a short list of users who see navigation changes called out inside the product the week of a release.\\n\\nTry the Automation menu and reply here if you hit anything else that feels off.\\n\\nTara Lindgren\\nCustomer Success\\ntara.lindgren@product.example\", \"metadata\": {\"name\": \"Thinks a feature was removed (it was moved)\", \"scenario_type\": \"D\", \"customer_name\": \"Omar Abdullah\", \"rubric_weights\": {\"D1_explicit_correction\": 0.2, \"D2_customer_frame\": 0.15, \"D3_no_condescension\": 0.2, \"D4_evidence_or_verify_path\": 0.1, \"D5_confirms_shared_understanding\": 0.1, \"D6_constructive_next_step\": 0.15, \"D7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"uses 'actually' dismissively\", \"uses 'as I explained' / 'as already stated' / 'per our earlier'\", \"implies the customer did not read the docs / onboarding / terms\", \"uses jargon without plain-language translation\", \"tells the customer they 'misunderstood'\", \"pure info-dump with no conversational close\"], \"baseline_score\": null}}"}
{"id": "D3", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Felipe Ramos, photographer (freelancer, canceled a month ago)\nSituation: He canceled his account 32 days ago. He's now realized he needs one of the project folders he had stored with us. He believes his data is gone forever.\nReality: our retention policy keeps canceled-account data available for 90 days before final deletion. His data is retrievable \u2014 he's at day 32 of 90.\n\nTheir inbound email (verbatim):\n\"I canceled my account about a month ago and I now realize I need the project files from the 'Patagonia 2025' folder. I know it's my fault for not exporting before canceling but is there any possible way to recover those files? I assume everything's deleted at this point but thought I'd ask in case there's anything you can do.\"\n\nDraft a response email to Felipe. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Good news \\u2014 your files aren't gone\\n\\nHi Felipe,\\n\\nYour files aren't deleted. We keep canceled-account data available for 90 days before final deletion, and you canceled about 32 days ago \\u2014 so you've still got around 58 days of window. The 'Patagonia 2025' folder is sitting there waiting for you.\\n\\nHere's the fastest way to get it:\\n\\n1. Reply here and I'll reinstate your account in read-only mode for 7 days at no charge. That gives you access to download everything via your normal browser.\\n2. If you'd rather not reactivate, I can package the Patagonia 2025 folder as a direct download link and send it to this email address within a day. I'll need your account email as the one you canceled under \\u2014 probably this same address, but worth confirming.\\n\\nTell me which one you prefer and I'll set it up today. Don't worry about the 90-day window for now \\u2014 I'll flag your account so it doesn't auto-purge while we're working on this.\\n\\nYuki Ostrowski\\nCustomer Care\\nyuki.ostrowski@product.example\", \"metadata\": {\"name\": \"Thinks data was deleted (retained 90 days and recoverable)\", \"scenario_type\": \"D\", \"customer_name\": \"Felipe Ramos\", \"rubric_weights\": {\"D1_explicit_correction\": 0.2, \"D2_customer_frame\": 0.15, \"D3_no_condescension\": 0.2, \"D4_evidence_or_verify_path\": 0.1, \"D5_confirms_shared_understanding\": 0.1, \"D6_constructive_next_step\": 0.15, \"D7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"uses 'actually' dismissively\", \"uses 'as I explained' / 'as already stated' / 'per our earlier'\", \"implies the customer did not read the docs / onboarding / terms\", \"uses jargon without plain-language translation\", \"tells the customer they 'misunderstood'\", \"pure info-dump with no conversational close\"], \"baseline_score\": null}}"}
{"id": "D4", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Aisha Thomas, COO at a 30-person nonprofit (Team plan, currently 18 of 30 seats used)\nSituation: She's trying to invite two new users and the 'Invite User' button appears grayed out. Our records show her plan has 12 open seats. The grayed-out button is a known browser cache issue on Safari when the user's session has been open more than 48 hours \u2014 a hard refresh resolves it.\nReality: she CAN invite users \u2014 it's a browser cache issue.\n\nTheir inbound email (verbatim):\n\"I'm trying to invite two new hires and the 'Invite User' button is grayed out. Have I hit my seat limit on Team tier? Our records show I should have 12 seats left. Do I need to upgrade just to add two people?\"\n\nDraft a response email to Aisha. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: The grayed-out invite button \\u2014 easy fix\\n\\nHi Aisha,\\n\\nYou haven't hit your seat limit. You have 12 open seats on Team tier, and adding two users is well inside that. The grayed-out 'Invite User' button is a known browser display issue we see on Safari specifically when a session has been open for more than about 48 hours.\\n\\nThe fix should take you 10 seconds:\\n\\n1. Hold Shift and click the reload button in Safari (or press Cmd+Shift+R). That forces a hard refresh.\\n2. The Invite User button should come back active. Try inviting one of your new hires to confirm.\\n\\nIf a hard refresh doesn't fix it, log out and back in \\u2014 that always resolves it. If after that you're still seeing it grayed out, reply here with a screenshot and I'll dig in from our side.\\n\\nYou don't need to upgrade. Please let me know once the invites go through, or if anything else pops up.\\n\\nMaya Jordan\\nCustomer Care\\nmaya.jordan@nonprofit.example\", \"metadata\": {\"name\": \"Thinks they can't invite users (actually a browser issue)\", \"scenario_type\": \"D\", \"customer_name\": \"Aisha Thomas\", \"rubric_weights\": {\"D1_explicit_correction\": 0.2, \"D2_customer_frame\": 0.15, \"D3_no_condescension\": 0.2, \"D4_evidence_or_verify_path\": 0.1, \"D5_confirms_shared_understanding\": 0.1, \"D6_constructive_next_step\": 0.15, \"D7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"uses 'actually' dismissively\", \"uses 'as I explained' / 'as already stated' / 'per our earlier'\", \"implies the customer did not read the docs / onboarding / terms\", \"uses jargon without plain-language translation\", \"tells the customer they 'misunderstood'\", \"pure info-dump with no conversational close\"], \"baseline_score\": null}}"}
{"id": "D5", "input": "You are drafting a customer email response. Here is the context:\n\nCustomer: Henry Okwuosa, owner of a boutique consulting firm\nPlan: Pro tier, MONTHLY billing at $49/month, active for 14 months\nSituation: He is disputing his April $49 charge because he believes he signed up for annual billing last year and shouldn't see monthly charges.\nReality: His records show he signed up for monthly. He might be thinking of a different service he uses. His billing history consistently shows $49/month for 14 months.\n\nTheir inbound email (verbatim):\n\"I was just charged $49 for this month. I signed up for annual billing when I started last year specifically so I wouldn't have monthly charges. Why am I seeing a monthly charge? Please refund this and make sure it doesn't happen again.\"\n\nDraft a response email to Henry. Output only the email content (subject line + body). No commentary.", "ground_truth": "{\"output\": \"Subject: Your billing \\u2014 here's what's on file\\n\\nHi Henry,\\n\\nI pulled up your account and your billing has been monthly since you signed up 14 months ago \\u2014 $49 every month. That's matched across every invoice in your history. I can't find any record of an annual signup on your account, so the April $49 charge is consistent with what you've been billed all along rather than a change.\\n\\nA couple of things that might be going on:\\n\\n- You may be thinking of a different service you signed up for around the same time. That happens surprisingly often and is worth a quick check against your other subscriptions.\\n- You may have intended to sign up for annual and hit monthly by accident 14 months ago. In which case, I'd love to help you switch now if it makes sense \\u2014 annual works out to $470/year instead of $588/year on monthly, which saves you about $118.\\n\\nIf you want, I can send over your full invoice history as a PDF so you can see the pattern. I can also switch you to annual effective your next renewal if that's what you actually want. Reply with whichever is most useful.\\n\\nI realize this isn't quite the refund answer you were expecting, and I don't want to just bat it back \\u2014 tell me which of those two is closer to the outcome you're after and I'll make it happen.\\n\\nLucia Feinberg\\nCustomer Care\\nlucia.feinberg@product.example\", \"metadata\": {\"name\": \"Thinks they're on annual billing (they're on monthly)\", \"scenario_type\": \"D\", \"customer_name\": \"Henry Okwuosa\", \"rubric_weights\": {\"D1_explicit_correction\": 0.2, \"D2_customer_frame\": 0.15, \"D3_no_condescension\": 0.2, \"D4_evidence_or_verify_path\": 0.1, \"D5_confirms_shared_understanding\": 0.1, \"D6_constructive_next_step\": 0.15, \"D7_voice_and_length\": 0.1}, \"prohibited_moves\": [\"uses 'actually' dismissively\", \"uses 'as I explained' / 'as already stated' / 'per our earlier'\", \"implies the customer did not read the docs / onboarding / terms\", \"uses jargon without plain-language translation\", \"tells the customer they 'misunderstood'\", \"pure info-dump with no conversational close\"], \"baseline_score\": null}}"}