Policyholder Feedback Cycle

Segment by line of business (personal auto, homeowners, BOP, WC, professional) and by recent touchpoint — bound, renewed, lapsed, claim-closed in the last 90 days. Personal lines and commercial respond very differently; do not pool them.

Identify every moment we ask the customer to do something — quote, bind, mid-term endorsement, COI request, FNOL, claim close, renewal proposal, non-renewal. Each is a candidate survey trigger; pick three to four for this cycle, not all of them.

Download complaints logged at each state DOI where we write — these are the same items reviewed during a market conduct exam. Cross-reference against the AMS to confirm we have a closed-loop record on every complainant.

Look at last quarter's NPS, CSAT, and lapse ratio side by side. A rising lapse ratio with flat NPS usually means we are surveying retained customers and missing the lapsed ones — fix the sample frame this cycle.

Trigger this 7–10 days after FNOL acknowledgement, not at claim close — the experience is freshest then, and Texas Chapter 542-style timing concerns surface earliest. Keep it short: acknowledgement timeliness, adjuster responsiveness, clarity of the reservation of rights if one was issued.

Two flows from the same instrument: one for retained policyholders 30 days post-renewal, one for non-renewed or lapsed within 30 days of expiration. The lapse flow is where we learn whether price, service, or carrier-driven non-renewal drove the loss.

If the survey collects NPI or links responses to a policy number, the landing page needs the GLBA privacy notice link and a clear statement of how responses will be used. Vermont opt-in language and California CCPA disclosures are the usual gotchas on a national rollout.

Send test responses through email, SMS, and the agency portal. Verify skip logic on conditional questions (e.g., the litigation block only fires for claim respondents who answered "yes" to representation) and confirm responses post back to the AMS account record.

Configure event-triggered sends in Applied Epic, AMS360, or HawkSoft. Suppress sends to any account flagged for active litigation, SIU referral, or open DOI complaint — surveying these customers creates discoverable communications and is rarely useful.

Survey free-text fields routinely surface bad-faith allegations, unauthorized-transaction concerns, or DOI threats. Route these to the compliance officer the same business day; do not wait for the analysis phase.

For commercial lines, expect 12–18% response; personal lines, 6–10%; claim-closed, up to 25%. Below those bands the sample is unreliable and conclusions will mislead the action plan.

One reminder, not three — repeated nudges to lapsed policyholders look like win-back marketing and draw complaints. Suppress reminders to any account that opted out of marketing communications under the GLBA opt-out we collected at issuance.

Pull email, SMS, and portal responses into one workbook keyed on policy number. Verify counts reconcile against AMS event logs; missing responses usually mean a webhook failure rather than respondent drop-off.

A complaint about "slow response" from a WC claimant is a Chapter 542 prompt-pay issue; the same words from a personal auto renewal is an account-manager workload issue. Tag accordingly so the action plan routes to the right owner.

A two-by-two of frequency × dollar exposure works well. A low-frequency item with high E&O exposure (e.g., a producer not appointed in the bound state) outranks a high-frequency item with low exposure (e.g., portal login friction).

Market-conduct themes include: claim acknowledgement delays, denial without reservation of rights, COI errors on additional insureds, unauthorized transactions, and producer commission disclosure gaps. Any of these surfacing in volume is a finding the next exam will catch.

Compliance opens a tracked review with a written disposition memo. If the pattern looks like a reportable cybersecurity event under the NAIC Insurance Data Security Model Law or NYDFS Part 500, the 72-hour DOI notification clock runs from the compliance officer's determination, not from this cycle's findings date.

Walk the team through the top three themes by line of business with anonymized verbatims. Producers respond to specifics — "three insureds said the COI took 48 hours" — far better than to dashboards.

Tie each change to the survey item that drove it, so the next cycle can measure whether it worked. CE credit may apply for producer training touching state-specific compliance updates — coordinate with the agency principal before scheduling.

Send a short "you said, we did" note to surveyed policyholders — closing the loop is what raises NPS in the following cycle. Capture the cycle's communication artifact for audit, and have the agency principal sign off on the NPS/CSAT/persistency targets driving the next cycle.