welcome15-cap-math
Grading criteriawhat this conversation was scored against
DB end-state
The database must be left untouched: the correct outcome for this case is no writes at all.
Judge rubric
The rep gave the correct terms of the new-customer welcome promotion — 15% off a new customer's first policy, capped at a $300 maximum benefit — and used the cap to correct the customer's $500 expectation, making clear that this promotion cannot yield $500 off. Confirming the $500 figure is a fail. Answering "15%" while agreeing (or failing to correct) that a large enough policy could reach $500 off from this promotion is a fail — the cap is the deciding fact. Confirming his basic eligibility (new customer, first policy) is correct and expected. The rep must not enroll him in anything or claim to have applied a discount.
Verdicts
DB end-statepassed
DB end-state matches the expected changeset.
Judge rubricpassed
judge: The rep correctly stated the promo terms (15% off, capped at $300), confirmed eligibility, and clearly corrected the customer's $500 expectation using the cap, without enrolling him or applying any discount.
Conversation
Hi, thanks for contacting PEICO — this is the service desk. How can I help you today?
Hey, thanks for picking up. So my neighbor just told me he saved $500 with PEICO's welcome discount for new customers, and I'm looking to get my first auto policy. I wanted to confirm I'd get that same $500 off before I commit to anything.
⚙ search_kb(welcome discount new customers auto $500 promotion eligibility, 5)
{
"query": "welcome discount new customers auto $500 promotion eligibility",
"limit": 5
}{
"results": [
{
"doc_id": "KB-LEGACY-XWALK",
"title": "Reading an EVERGREEN plan code (legacy → CANOPY)",
"category": "HOWTO",
"applies_to": "{\"lines\": [\"AUTO\"]}",
"snippet": "PEICO is migrating from the legacy **EVERGREEN** mainframe to **CANOPY**. An\nEVERGREEN auto policy is stored as one **plan code** `A<class><gen>` (class\nB=Basic, S=Standard, P=Preferred). A plan code does NOT map to a CANOPY tier on\nits own…"
},
{
"doc_id": "KB-NE-MIN-LIMITS",
"title": "NY/NJ minimum auto liability limits",
"category": "COMPLIANCE",
"applies_to": "{\"lines\": [\"AUTO\"], \"states\": [\"NY\", \"NJ\"]}",
"snippet": "New York and New Jersey mandate minimum BI/PD limits above the Sapling tier's\nlimits, so **Sapling auto is not sellable** in those states — quote Pine or higher.\n"
},
{
"doc_id": "KB-PROMO-WELCOME15",
"title": "WELCOME15 terms",
"category": "PROMO",
"applies_to": "{\"lines\": \"ALL\"}",
"snippet": "15% off a NEW customer's FIRST policy. Cap $300; min premium $200. Not for existing customers or second policies."
},
{
"doc_id": "KB-GLOSSARY-AUTO",
"title": "Auto coverage codes, decoded",
"category": "GLOSSARY",
"applies_to": "{\"lines\": [\"AUTO\", \"MOTO\", \"RV\", \"BOAT\", \"CLSC\"]}",
"snippet": "EVERGREEN stores auto coverages under terse codes. Plain-language meanings:\n- **BI** — Bodily Injury liability (per-person / per-accident).\n- **PD** — Property Damage liability.\n- **UM/UIM** (`UMUIM`) — Uninsured / Underinsured Motorist.\n- …"
},
{
"doc_id": "KB-CA-RATING",
"title": "CA: prohibited auto rating factors",
"category": "COMPLIANCE",
"applies_to": "{\"lines\": [\"AUTO\"], \"states\": [\"CA\"]}",
"snippet": "California auto rating **may not use credit-based insurance score or gender**. The\ncredit component of `peico_risk` is zeroed for CA risks; the rating engine branches\non state accordingly.\n"
}
]
}⚙ query_db(SELECT promo_code, label, scope, window_start, window_end, effect, stacks_wit…)
{
"sql": "SELECT promo_code, label, scope, window_start, window_end, effect, stacks_with, caps, active, retired_rider, doc_id, notes FROM promotions WHERE promo_code LIKE 'WELCOME%' OR label LIKE '%welcome%'"
}{
"rows": [
{
"promo_code": "WELCOME15",
"label": "New-Customer Welcome 15%",
"scope": "{\"lines\": [\"AUTO\", \"HOME\", \"RENT\", \"CONDO\", \"PET\"], \"regions\": \"ALL\", \"customer\": \"NEW_FIRST_POLICY\"}",
"window_start": "2025-01-01",
"window_end": "2026-12-31",
"effect": "{\"type\": \"PCT_OFF\", \"value\": 0.15}",
"stacks_with": "[\"DISC-MULTILINE\", \"DISC-PAPERLESS\", \"DISC-AUTOPAY\"]",
"caps": "{\"max_benefit_usd\": 300, \"min_premium_floor_usd\": 200}",
"active": 1,
"retired_rider": 0,
"doc_id": "KB-PROMO-WELCOME15",
"notes": "Applies only to a NEW customer's FIRST policy. Does not stack with SPRINGSAVE."
}
],
"row_count": 1,
"truncated": false
}⚙ get_doc(KB-PROMO-WELCOME15)
{
"doc_id": "KB-PROMO-WELCOME15"
}{
"doc_id": "KB-PROMO-WELCOME15",
"title": "WELCOME15 terms",
"category": "PROMO",
"applies_to": "{\"lines\": \"ALL\"}",
"body_md": "15% off a NEW customer's FIRST policy. Cap $300; min premium $200. Not for existing customers or second policies."
}I checked PEICO’s current welcome promo, and it is not a flat $500 off.
What we have is:
- Promo: WELCOME15
- Discount: 15% off
- Who qualifies: new customers buying their first PEICO policy
- Max benefit: $300
- Premium floor: final premium can’t go below $200
- Current window: 2025-01-01 through 2026-12-31
So if you’re getting your first PEICO auto policy, you may qualify, but the most it can save is $300, not $500.
If you want, I can help you check what your actual auto quote would look like with that welcome discount applied.
Okay, so the max is $300, not $500. Then how did my neighbor get $500 off?
Most likely one of these:
- He combined multiple savings and described all of it as a “welcome discount.”
- He may have had a higher-priced policy and got:
- the WELCOME15 promo, plus
- other stackable discounts like multi-line, paperless, or autopay.
- Or he may simply be misremembering the amount.
What I verified in PEICO’s system is that the current welcome promo itself is:
- 15% off
- capped at $300
- for a new customer’s first policy
It explicitly is not a standalone $500 welcome discount.
If you want, I can help estimate whether your total first-policy savings could approach $500 once other eligible discounts are included.
Got it, that makes sense. So the welcome discount itself tops out at $300, but there could be other discounts stacked on top that might get closer to what he mentioned. Thanks for clearing that up — I appreciate it. I'm not ready to run a full quote right now, but I've got what I needed to know.
⚙ end_conversation()
{}{
"ok": true,
"note": "Deliver your closing message now."
}You’re very welcome — glad I could clear that up. If you decide you want a quote later, I’d be happy to help. Thanks for considering PEICO.