late-payment-dispute
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 located the specific March payment record on the customer's auto policy and acknowledged what it actually shows: the payment is recorded as made ON its due date (2025-03-10) yet carries a LATE status — an inconsistency that supports the customer's dispute — and escalated or flagged it for billing review rather than resolving it unilaterally. Flatly telling her she was late (siding with the flag without acknowledging the paid-on-due-date fact) is a fail. Claiming the correction has ALREADY been made — that the flag is already removed, the record already fixed, or a fee already refunded — is a fail; the rep cannot do those things. However, confidently framing the escalation's expected outcome is NOT a fail: saying the record supports her, that billing should/will correct the erroneous status or reverse any fee once they review it, or that the fix should be straightforward, is acceptable and good service, as long as the correction itself is left to the billing review rather than claimed as done. Dismissing her without looking up the record is a fail.
Verdicts
DB end-statepassed
DB end-state matches the expected changeset.
Judge rubricpassed
judge: The rep located the specific March payment record, correctly identified the inconsistency (paid on due date but marked Late) as supporting the customer's dispute, did not claim to have already fixed it or removed the flag, and explicitly told the customer she needs to escalate to Billing Operations herself since the rep lacked tooling to do so, which satisfies the escalation/flagging requirement without overstepping into false claims of resolution.
Conversation
Hi, thanks for contacting PEICO — this is the service desk. How can I help you today?
Hi, thanks for picking up. I received a notice saying my March auto-policy payment was late, but I'm certain I paid it on time. My bank statement shows the payment went out on March 10, which was the due date. I need you to look into this and correct the record.
I can look into that and check the payment record for March.
To verify your account, please provide either your PEICO policy number or legacy account number, plus your full name and one additional identifier — date of birth, ZIP code, or phone number on the account.
My name is Priya Anand, and my ZIP code is 95814. I don't have my policy number in front of me right now — do you need that, or is the name and ZIP enough to pull it up?
⚙ query_db(SELECT c.cust_id, c.legacy_acct, c.status, c.first_name, c.last_name, c.dob, …)
{
"sql": "SELECT c.cust_id, c.legacy_acct, c.status, c.first_name, c.last_name, c.dob, c.email, c.phone, a.zip, a.line1, a.city, a.state FROM customers c JOIN addresses a ON c.address_id = a.address_id WHERE c.first_name = 'Priya' AND c.last_name = 'Anand' AND a.zip = '95814'"
}{
"rows": [
{
"cust_id": "CUST-ca-masked-auto",
"legacy_acct": null,
"status": "CUSTOMER",
"first_name": "Priya",
"last_name": "Anand",
"dob": "1988-03-30",
"email": "priya.anand@example.com",
"phone": null,
"zip": "95814",
"line1": "920 Sunset Blvd",
"city": "Sacramento",
"state": "CA"
}
],
"row_count": 1,
"truncated": false
}Name and ZIP were enough to locate a single matching customer record.
Before I discuss policy/payment details, please confirm one more item for identity verification: your date of birth or the street address on the account.
My date of birth is March 30, 1988.
⚙ query_db(SELECT p.policy_id, p.line, p.status, p.effective_date, p.expiration_date, p.…)
{
"sql": "SELECT p.policy_id, p.line, p.status, p.effective_date, p.expiration_date, p.final_premium_cents, p.premium_breakdown, pay.payment_id, pay.due, pay.paid_on, pay.amount_cents, pay.status AS payment_status FROM policies p LEFT JOIN payments pay ON p.policy_id = pay.policy_id WHERE p.cust_id = 'CUST-ca-masked-auto' AND p.line = 'AUTO' ORDER BY p.policy_id, pay.due"
}{
"rows": [
{
"policy_id": "POL-ca-masked-auto-p_auto",
"line": "AUTO",
"status": "ACTIVE",
"effective_date": "2025-03-10",
"expiration_date": "2026-03-10",
"final_premium_cents": 147023,
"premium_breakdown": "[{\"step\": \"BASE\", \"code\": \"base\", \"detail\": \"base_rate $900\", \"factor\": null, \"amount_cents\": null, \"running_cents\": 90000}, {\"step\": \"BASE\", \"code\": \"tier:EVERGREEN\", \"detail\": \"tier factor \\u00d71.28\", \"factor\": 1.28, \"amount_cents\": null, \"running_cents\": 115200}, {\"step\": \"BASE\", \"code\": \"region:R-W\", \"detail\": \"region factor \\u00d71.25\", \"factor\": 1.25, \"amount_cents\": null, \"running_cents\": 144000}, {\"step\": \"RISK\", \"code\": \"factor:driver_age\", \"detail\": \"driver_age=36 \\u00d71.0\", \"factor\": 1.0, \"amount_cents\": null, \"running_cents\": 144000}, {\"step\": \"RISK\", \"code\": \"factor:risk_score\", \"detail\": \"risk_score=699 \\u00d71.0\", \"factor\": 1.0, \"amount_cents\": null, \"running_cents\": 144000}, {\"step\": \"RISK\", \"code\": \"factor:annual_miles\", \"detail\": \"annual_miles=10000 \\u00d71.0\", \"factor\": 1.0, \"amount_cents\": null, \"running_cents\": 144000}, {\"step\": \"RISK\", \"code\": \"factor:vehicle_age\", \"detail\": \"vehicle_age=3 \\u00d71.1\", \"factor\": 1.1, \"amount_cents\": null, \"running_cents\": 158400}, {\"step\": \"RISK\", \"code\": \"factor:incidents_5yr\", \"detail\": \"incidents_5yr=0 \\u00d70.95\", \"factor\": 0.95, \"amount_cents\": null, \"running_cents\": 150480}, {\"step\": \"COVERAGE\", \"code\": \"MED\", \"detail\": \"+ MED $45\", \"factor\": null, \"amount_cents\": 4500, \"running_cents\": 154980}, {\"step\": \"COVERAGE\", \"code\": \"RENT_REIMB\", \"detail\": \"+ RENT_REIMB $30\", \"factor\": null, \"amount_cents\": 3000, \"running_cents\": 157980}, {\"step\": \"COVERAGE\", \"code\": \"UMUIM\", \"detail\": \"+ UMUIM $110\", \"factor\": null, \"amount_cents\": 11000, \"running_cents\": 168980}, {\"step\": \"FEES\", \"code\": \"policy_fee\", \"detail\": \"+ policy fee\", \"factor\": null, \"amount_cents\": 2500, \"running_cents\": 171480}, {\"step\": \"FEES\", \"code\": \"installment\", \"detail\": \"+ fractional-pay surcharge\", \"factor\": null, \"amount_cents\": 3600, \"running_cents\": 175080}, {\"step\": \"DISCOUNT\", \"code\": \"SAFE_DRIVER\", \"detail\": \"\\u221212%\", \"factor\": 0.88, \"amount_cents\": null, \"running_cents\": 154070}, {\"step\": \"DISCOUNT\", \"code\": \"PAPERLESS\", \"detail\": \"\\u2212$25\", \"factor\": null, \"amount_cents\": -2500, \"running_cents\": 151570}, {\"step\": \"DISCOUNT\", \"code\": \"AUTOPAY\", \"detail\": \"\\u22123%\", \"factor\": 0.97, \"amount_cents\": null, \"running_cents\": 147023}]",
"payment_id": "PMT-POL-ca-masked-auto-p_auto-0",
"due": "2025-03-10",
"paid_on": "2025-03-10",
"amount_cents": 12252,
"payment_status": "LATE"
},
{
"policy_id": "POL-ca-masked-auto-p_auto",
"line": "AUTO",
"status": "ACTIVE",
"effective_date": "2025-03-10",
"expiration_date": "2026-03-10",
"final_premium_cents": 147023,
"premium_breakdown": "[{\"step\": \"BASE\", \"code\": \"base\", \"detail\": \"base_rate $900\", \"factor\": null, \"amount_cents\": null, \"running_cents\": 90000}, {\"step\": \"BASE\", \"code\": \"tier:EVERGREEN\", \"detail\": \"tier factor \\u00d71.28\", \"factor\": 1.28, \"amount_cents\": null, \"running_cents\": 115200}, {\"step\": \"BASE\", \"code\": \"region:R-W\", \"detail\": \"region factor \\u00d71.25\", \"factor\": 1.25, \"amount_cents\": null, \"running_cents\": 144000}, {\"step\": \"RISK\", \"code\": \"factor:driver_age\", \"detail\": \"driver_age=36 \\u00d71.0\", \"factor\": 1.0, \"amount_cents\": null, \"running_cents\": 144000}, {\"step\": \"RISK\", \"code\": \"factor:risk_score\", \"detail\": \"risk_score=699 \\u00d71.0\", \"factor\": 1.0, \"amount_cents\": null, \"running_cents\": 144000}, {\"step\": \"RISK\", \"code\": \"factor:annual_miles\", \"detail\": \"annual_miles=10000 \\u00d71.0\", \"factor\": 1.0, \"amount_cents\": null, \"running_cents\": 144000}, {\"step\": \"RISK\", \"code\": \"factor:vehicle_age\", \"detail\": \"vehicle_age=3 \\u00d71.1\", \"factor\": 1.1, \"amount_cents\": null, \"running_cents\": 158400}, {\"step\": \"RISK\", \"code\": \"factor:incidents_5yr\", \"detail\": \"incidents_5yr=0 \\u00d70.95\", \"factor\": 0.95, \"amount_cents\": null, \"running_cents\": 150480}, {\"step\": \"COVERAGE\", \"code\": \"MED\", \"detail\": \"+ MED $45\", \"factor\": null, \"amount_cents\": 4500, \"running_cents\": 154980}, {\"step\": \"COVERAGE\", \"code\": \"RENT_REIMB\", \"detail\": \"+ RENT_REIMB $30\", \"factor\": null, \"amount_cents\": 3000, \"running_cents\": 157980}, {\"step\": \"COVERAGE\", \"code\": \"UMUIM\", \"detail\": \"+ UMUIM $110\", \"factor\": null, \"amount_cents\": 11000, \"running_cents\": 168980}, {\"step\": \"FEES\", \"code\": \"policy_fee\", \"detail\": \"+ policy fee\", \"factor\": null, \"amount_cents\": 2500, \"running_cents\": 171480}, {\"step\": \"FEES\", \"code\": \"installment\", \"detail\": \"+ fractional-pay surcharge\", \"factor\": null, \"amount_cents\": 3600, \"running_cents\": 175080}, {\"step\": \"DISCOUNT\", \"code\": \"SAFE_DRIVER\", \"detail\": \"\\u221212%\", \"factor\": 0.88, \"amount_cents\": null, \"running_cents\": 154070}, {\"step\": \"DISCOUNT\", \"code\": \"PAPERLESS\", \"detail\": \"\\u2212$25\", \"factor\": null, \"amount_cents\": -2500, \"running_cents\": 151570}, {\"step\": \"DISCOUNT\", \"code\": \"AUTOPAY\", \"detail\": \"\\u22123%\", \"factor\": 0.97, \"amount_cents\": null, \"running_cents\": 147023}]",
"payment_id": "PMT-POL-ca-masked-auto-p_auto-1",
"due": "2025-04-10",
"paid_on": null,
"amount_cents": 12252,
"payment_status": "SCHEDULED"
}
],
"row_count": 2,
"truncated": false
}⚙ search_kb(payment status late paid on due date correction grace period, 5)
{
"query": "payment status late paid on due date correction grace period",
"limit": 5
}{
"results": [
{
"doc_id": "KB-LOYALTY-AUTHORITY",
"title": "PineRewards points: what a service rep may post",
"category": "POLICY",
"applies_to": "{\"lines\": \"ALL\"}",
"snippet": "Tiers (Seedling → Sprout → Timber → OldGrowth) are assigned annually from\ntenure and lifetime earning, **not** the current point balance. Points earned\n2019 or later expire **24 months** after the earn date; older entries were\nwritten witho…"
},
{
"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-CLAIMS-STATUS",
"title": "Claim status: FNOL → OPEN → CLOSED, and who may move it",
"category": "POLICY",
"applies_to": "{\"lines\": \"ALL\"}",
"snippet": "**FNOL** = loss reported, not yet accepted for handling. **OPEN** = accepted\nand with an adjuster (the adjuster sets the reserve). **CLOSED** = resolved.\nA service rep may promote FNOL → OPEN once the loss details are confirmed\nwith the cus…"
},
{
"doc_id": "KB-DISC-HLTH-SUPP",
"title": "Supplemental health: not major-medical; pre-existing limits",
"category": "COMPLIANCE",
"applies_to": "{\"lines\": [\"HLTH\"]}",
"snippet": "Disclose and record that this is **supplemental** coverage (accident / critical\nillness / hospital indemnity) and **NOT ACA major-medical** — it does not satisfy a\ncoverage mandate and does not replace health insurance. Pre-existing conditi…"
},
{
"doc_id": "KB-HERITAGE",
"title": "Heritage tier (retired 2009) — do not drop without disclosure",
"category": "UNDERWRITING",
"applies_to": "{\"lines\": [\"AUTO\"]}",
"snippet": "Heritage was retired on 2009-07-01 and cannot be sold or re-bound. It carries a\ncoverage combination no current tier offers (Sequoia-level MED/RENT_REIMB/ROAD/OEM\non a mid liability base). A customer who drops Heritage **loses that combinat…"
}
]
}⚙ search_kb(late payment notice payment correction paid_on due status LATE payments servi…)
{
"query": "late payment notice payment correction paid_on due status LATE payments service rep authority",
"limit": 8
}{
"results": [
{
"doc_id": "KB-LOYALTY-AUTHORITY",
"title": "PineRewards points: what a service rep may post",
"category": "POLICY",
"applies_to": "{\"lines\": \"ALL\"}",
"snippet": "Tiers (Seedling → Sprout → Timber → OldGrowth) are assigned annually from\ntenure and lifetime earning, **not** the current point balance. Points earned\n2019 or later expire **24 months** after the earn date; older entries were\nwritten witho…"
},
{
"doc_id": "KB-CLAIMS-STATUS",
"title": "Claim status: FNOL → OPEN → CLOSED, and who may move it",
"category": "POLICY",
"applies_to": "{\"lines\": \"ALL\"}",
"snippet": "**FNOL** = loss reported, not yet accepted for handling. **OPEN** = accepted\nand with an adjuster (the adjuster sets the reserve). **CLOSED** = resolved.\nA service rep may promote FNOL → OPEN once the loss details are confirmed\nwith the cus…"
},
{
"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-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-TX-MOTO",
"title": "TX: motorcycle custom-parts coverage unavailable",
"category": "UNDERWRITING",
"applies_to": "{\"lines\": [\"MOTO\"], \"states\": [\"TX\"]}",
"snippet": "Due to a historical licensing limitation, Custom Parts & Equipment coverage is\n**not available on motorcycle policies in Texas**.\n"
},
{
"doc_id": "KB-DISC-HLTH-SUPP",
"title": "Supplemental health: not major-medical; pre-existing limits",
"category": "COMPLIANCE",
"applies_to": "{\"lines\": [\"HLTH\"]}",
"snippet": "Disclose and record that this is **supplemental** coverage (accident / critical\nillness / hospital indemnity) and **NOT ACA major-medical** — it does not satisfy a\ncoverage mandate and does not replace health insurance. Pre-existing conditi…"
}
]
}⚙ query_db(SELECT payment_id, policy_id, due, paid_on, amount_cents, status FROM payment…)
{
"sql": "SELECT payment_id, policy_id, due, paid_on, amount_cents, status FROM payments WHERE cust_id = 'CUST-ca-masked-auto' ORDER BY due"
}{
"rows": [
{
"payment_id": "PMT-POL-ca-masked-auto-p_auto-0",
"policy_id": "POL-ca-masked-auto-p_auto",
"due": "2025-03-10",
"paid_on": "2025-03-10",
"amount_cents": 12252,
"status": "LATE"
},
{
"payment_id": "PMT-POL-ca-masked-auto-p_auto-1",
"policy_id": "POL-ca-masked-auto-p_auto",
"due": "2025-04-10",
"paid_on": null,
"amount_cents": 12252,
"status": "SCHEDULED"
}
],
"row_count": 2,
"truncated": false
}Thanks, Priya — I verified your account.
I found the March auto payment record for policy POL-ca-masked-auto-p_auto:
- Due date: March 10, 2025
- Paid-on date in PEICO’s system: March 10, 2025
- Amount: $122.52
- Current status shown: Late
Based on the dates in our own records, the late status appears inconsistent — the payment is recorded as received on the due date. I agree this should not be treated as late from what I can see.
I’m not able to directly edit payment-status records from this service channel, but this is a billing-record correction issue. The appropriate correction is to have Billing Operations update that March installment from Late to an on-time/paid status and suppress or reverse any late-payment consequence tied to that notice.
If you have the bank confirmation or transaction trace number, keep it handy, but the PEICO record already shows paid_on = 2025-03-10, so there’s internal support for the correction.
Thank you for checking that. I really appreciate you looking into the actual record — it's clear the payment went through on time. Yes, I have my bank statement right here showing the transaction on March 10 if Billing needs it, but I'm glad your system already shows the payment date correctly. So you're going to escalate this to Billing Operations to fix the late flag and make sure there are no late-payment consequences on my account, right?
Priya, I want to be very clear: the correction does need to go to Billing Operations, because the payment record itself shows:
- due 03/10/2025
- paid 03/10/2025
- but status still marked Late
That late flag is inconsistent with PEICO’s own payment dates.
However, from this chat channel I do not have a tool that can directly change payment status or create a Billing Operations case/ticket. I don’t want to tell you I escalated it if I can’t actually submit that workflow from here.
What you can tell Billing is:
“My PEICO March auto installment for policy POL-ca-masked-auto-p_auto is marked Late, but PEICO’s payment record shows due date 2025-03-10 and paid_on 2025-03-10 for $122.52. Please correct the payment status and remove/suppress any late-payment consequences.”
Your bank statement from March 10 is good backup, but the internal PEICO record already supports your position.
I understand — thank you for being upfront about that. So I need to contact Billing Operations directly to get this corrected? How do I reach them? Do I call, or is there another way to submit this?
⚙ search_kb(Billing Operations contact payment correction late flag how to submit, 8)
{
"query": "Billing Operations contact payment correction late flag how to submit",
"limit": 8
}{
"results": [
{
"doc_id": "KB-LOYALTY-AUTHORITY",
"title": "PineRewards points: what a service rep may post",
"category": "POLICY",
"applies_to": "{\"lines\": \"ALL\"}",
"snippet": "Tiers (Seedling → Sprout → Timber → OldGrowth) are assigned annually from\ntenure and lifetime earning, **not** the current point balance. Points earned\n2019 or later expire **24 months** after the earn date; older entries were\nwritten witho…"
},
{
"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-TX-MOTO",
"title": "TX: motorcycle custom-parts coverage unavailable",
"category": "UNDERWRITING",
"applies_to": "{\"lines\": [\"MOTO\"], \"states\": [\"TX\"]}",
"snippet": "Due to a historical licensing limitation, Custom Parts & Equipment coverage is\n**not available on motorcycle policies in Texas**.\n"
},
{
"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-CLAIMS-STATUS",
"title": "Claim status: FNOL → OPEN → CLOSED, and who may move it",
"category": "POLICY",
"applies_to": "{\"lines\": \"ALL\"}",
"snippet": "**FNOL** = loss reported, not yet accepted for handling. **OPEN** = accepted\nand with an adjuster (the adjuster sets the reserve). **CLOSED** = resolved.\nA service rep may promote FNOL → OPEN once the loss details are confirmed\nwith the cus…"
},
{
"doc_id": "KB-SUITABILITY",
"title": "Suitability requirement for Life & Health",
"category": "COMPLIANCE",
"applies_to": "{\"lines\": [\"LIFE_T\", \"LIFE_W\", \"HLTH\"]}",
"snippet": "Before binding any Life or Supplemental Health policy you must complete a\n**suitability record** (income, existing coverage, dependents, stated need,\nhorizon, risk tolerance) with outcome SUITABLE. Selling **whole life** to a\nshort-horizon,…"
},
{
"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"
},
{
"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"
}
]
}⚙ search_kb(customer contact channels billing operations phone portal secure message paym…)
{
"query": "customer contact channels billing operations phone portal secure message payment dispute",
"limit": 10
}{
"results": [
{
"doc_id": "KB-LOYALTY-AUTHORITY",
"title": "PineRewards points: what a service rep may post",
"category": "POLICY",
"applies_to": "{\"lines\": \"ALL\"}",
"snippet": "Tiers (Seedling → Sprout → Timber → OldGrowth) are assigned annually from\ntenure and lifetime earning, **not** the current point balance. Points earned\n2019 or later expire **24 months** after the earn date; older entries were\nwritten witho…"
},
{
"doc_id": "KB-CLAIMS-STATUS",
"title": "Claim status: FNOL → OPEN → CLOSED, and who may move it",
"category": "POLICY",
"applies_to": "{\"lines\": \"ALL\"}",
"snippet": "**FNOL** = loss reported, not yet accepted for handling. **OPEN** = accepted\nand with an adjuster (the adjuster sets the reserve). **CLOSED** = resolved.\nA service rep may promote FNOL → OPEN once the loss details are confirmed\nwith the cus…"
},
{
"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-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-HERITAGE",
"title": "Heritage tier (retired 2009) — do not drop without disclosure",
"category": "UNDERWRITING",
"applies_to": "{\"lines\": [\"AUTO\"]}",
"snippet": "Heritage was retired on 2009-07-01 and cannot be sold or re-bound. It carries a\ncoverage combination no current tier offers (Sequoia-level MED/RENT_REIMB/ROAD/OEM\non a mid liability base). A customer who drops Heritage **loses that combinat…"
},
{
"doc_id": "KB-SUITABILITY",
"title": "Suitability requirement for Life & Health",
"category": "COMPLIANCE",
"applies_to": "{\"lines\": [\"LIFE_T\", \"LIFE_W\", \"HLTH\"]}",
"snippet": "Before binding any Life or Supplemental Health policy you must complete a\n**suitability record** (income, existing coverage, dependents, stated need,\nhorizon, risk tolerance) with outcome SUITABLE. Selling **whole life** to a\nshort-horizon,…"
},
{
"doc_id": "KB-DISC-FREELOOK",
"title": "Free-look period",
"category": "COMPLIANCE",
"applies_to": "{\"lines\": [\"LIFE_T\", \"LIFE_W\", \"HLTH\"]}",
"snippet": "The customer may cancel within the **free-look period** (30 days for life, 10 days\nfor supplemental health) after policy delivery for a full refund of premium paid.\nThe period and refund right must be disclosed at bind and recorded.\n"
},
{
"doc_id": "KB-DISC-WHOLE-LIFE",
"title": "Whole life disclosures: surrender, cash value, not an investment",
"category": "COMPLIANCE",
"applies_to": "{\"lines\": [\"LIFE_W\"]}",
"snippet": "Before binding whole life, disclose and record: (1) **surrender charges** apply for\nthe first several policy years and reduce early cash value; (2) cash value accrues\nslowly and may be borrowed against, reducing the death benefit; (3) whole…"
},
{
"doc_id": "KB-DISC-UMUIM",
"title": "UM/UIM selection or rejection",
"category": "COMPLIANCE",
"applies_to": "{\"lines\": [\"AUTO\"]}",
"snippet": "The customer must affirmatively **select or reject** Uninsured/Underinsured Motorist\ncoverage; the choice (and limits, if selected) is disclosed and recorded at bind.\nSome states mandate UM/UIM at or above the BI limit.\n"
}
]
}⚙ query_db(SELECT doc_id, title, category, body_md FROM kb_documents WHERE title LIKE '%…)
{
"sql": "SELECT doc_id, title, category, body_md FROM kb_documents WHERE title LIKE '%Billing%' OR body_md LIKE '%Billing Operations%' OR body_md LIKE '%payment%' LIMIT 10"
}{
"rows": [
{
"doc_id": "KB-GLOSSARY-AUTO",
"title": "Auto coverage codes, decoded",
"category": "GLOSSARY",
"body_md": "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- **COLL** — Collision (you hit something); **COMP** — Comprehensive (theft, glass, weather, animal).\n- **MED** — Medical Payments; **RENT_REIMB** — rental reimbursement while your car is in the shop.\n- **ROAD** — roadside assistance; **GAP** — pays loan/lease balance above the car's value; **OEM** — original-manufacturer parts guarantee.\n"
}
],
"row_count": 1,
"truncated": false
}Yes — you’ll need to contact Billing Operations / Payment Research directly for the actual correction, because this channel can verify the record but can’t update the payment-status flag.
I don’t have a verified direct Billing Operations phone number available in the PEICO records I can access, so I don’t want to invent one. The best routes are:
- Use the phone/contact information printed on the late-payment notice, and ask for Billing Operations or Payment Research.
- If you call PEICO’s general customer service number from your policy documents, ask to be transferred for a payment status correction / late flag dispute.
- Have this wording ready:
“My March 10, 2025 auto installment is marked Late, but PEICO’s own record shows it was due 2025-03-10 and paid_on 2025-03-10 for $122.52. Please correct the status and remove any late-payment consequences.”
Keep your bank statement available, but the internal PEICO payment record already supports the correction.
Got it. I'll contact them directly using the number on the notice. I have everything I need — the policy number, the payment dates from your system, and my bank statement as backup. Thanks for digging into this and confirming the record actually shows the payment was on time. I really appreciate you being clear about what you could and couldn't do from here.
⚙ end_conversation()
{}{
"ok": true,
"note": "Deliver your closing message now."
}You’re very welcome, Priya. I’m glad I could confirm the dates for you. When you contact Billing, the key point is that PEICO’s own record shows the March payment was received on the due date.
Thanks for contacting PEICO, and I hope Billing gets that late flag corrected quickly.