What Changes for Brokers When Verisk Loss Costs Live Inside Copilot, Claude and Amazon Quick?

Updated Nov 1, 2026 — added the free chat-number challenge card, slow-the-number pack, and copilot feed file downloads to this guide.

Short answer: your underwriters just got a faster front door to the same Verisk data they’ve always used. On October 28, 2026, Verisk announced new integrations with Amazon Quick and Microsoft Copilot, plus expanded offerings inside Claude by Anthropic, so authorized insurers can pull ISO Loss Costs, PAAS content, and property-level weather history through plain-language questions inside the AI tools already on their desks. Brokers don’t get a login out of this announcement. What you get is a counterpart who can surface the number behind an indication in seconds — and that changes the conversation you’re walking into.

What exactly did Verisk announce?

Three things, all in one October 28, 2026 release. First, a new Amazon Quick integration giving eligible customers access to ISO Loss Costs and Premium Audit Advisory Service (PAAS) content. Second, a new Microsoft Copilot integration with the same Loss Costs and PAAS access for eligible customers. Third, an expansion inside Claude: Verisk Underwriting Intelligence in Claude — which launched earlier this year with ISO Loss Costs — now adds PAAS resources, plus a new Verisk Benchmark connector that gives controlled, permissioned access to property-level hail and wind history.

Same content, new front door. Verisk was explicit that existing content entitlements, permissions and governance controls continue to apply. Nobody got data they weren’t already paying for. They got it inside a chat window instead of a separate lookup. As Saurabh Khemka, president of Verisk Underwriting Solutions, put it in the release, the point is helping professionals “get relevant, reliable information when they need it” — and Verisk’s stated goal is cutting research time so insurers make decisions faster.

As a broker, do I get access to any of this?

No — not directly, and that’s the part of this announcement most likely to get misread. The release is written to insurers throughout: “authorized insurers,” “eligible customers,” access governed by the entitlements an insurer already holds. There is no broker tier, no agency login, no retail version in anything Verisk announced.

You will feel it secondhand, through carrier underwriters. When the person across the table can ask Copilot or Claude for the loss cost, the audit classification guidance, or a property’s hail and wind history mid-conversation, the pace and the precision of that conversation change. You’ll hear Verisk numbers quoted earlier, faster, and with more confidence. Your job becomes pressure-testing those numbers, not waiting on them.

What are ISO Loss Costs and PAAS, in plain terms?

Quick grounding, because these two data sets now sit at the center of the AI conversation. ISO Loss Costs are advisory expected-loss figures — the loss component of a rate, built from pooled industry data for a given class and territory — that many carriers use as the starting point for pricing before adding their own expenses, judgment and account-specific adjustments. PAAS — the Premium Audit Advisory Service — is Verisk’s premium audit reference content: classification and audit guidance carriers use to check that an account’s actual exposures (payroll, sales, operations) match how it was classified and rated.

Neither one is an account-specific answer. Loss costs are class-level statistics. PAAS is guidance for verifying exposures. Both are inputs to a decision a human underwriter still makes. That’s worth remembering when the number comes out of a chat window sounding final.

What changes in a submission or renewal conversation?

Three practical things. Speed. Verisk says the goal is reducing research time, and a natural-language lookup is genuinely faster than a manual one. Expect indications and follow-up questions to come back quicker, especially on routine commercial lines accounts.

Property weather history enters the room. The Benchmark connector puts property-level hail and wind history into Claude for authorized users. On property renewals, expect underwriters to raise specific storm history for the specific address earlier than you’re used to — which means your roof documentation, updates and mitigation story need to be in the submission up front, not produced after the first objection. (For the other Verisk number brokers have been living with lately, see our piece on Verisk’s October 2026 price list update and what it does to claims settlements.)

The underwriter’s view of your submission sharpens. Faster data access means sloppy submissions get spotted faster too — mismatched classifications, stale loss runs, exposures that don’t line up with PAAS guidance. If you haven’t read it, our breakdown of what underwriters actually see when they look at your submissions is the right homework before your next renewal cycle.

The number came out of a chat window. What should you ask before you rely on it?

This is the broker skill this announcement actually creates. A chat answer feels finished. Your job is to pull it apart before it reaches a client. Four questions cover most of the risk:

1. Which content, and which version? Loss costs change on effective dates. Ask which loss cost and what effective date sits behind the indication — and before you repeat any figure to an insured, confirm it against the source, not the summary.
2. Is that the class number or the account number? An assistant surfaces the class-level data it’s entitled to surface. Your account’s loss history, credits and debits are applied by the underwriter. If those two get blended in conversation, separate them out loud.
3. Can I get that in writing? A chat answer is not a quote. Anything you’re going to act on — an indication, a classification call, a weather-history flag — get it in the file in a form you can point to later.
4. What’s your governance on this? Verisk says its permissioning and governance controls carry into the AI integrations, and carriers are already answering to regulators on AI underwriting — the landscape we mapped in AI governance in insurance and the 2026 regulatory reckoning. Asking your carrier how it validates AI-surfaced data is a fair, professional question now, not a confrontational one.

And document your own side of it. The policy check has long been the E&O front line in an agency — our piece on the policy-check agent and the E&O front line makes that case in detail — and AI-surfaced figures extend the same principle: if you relied on it, the file should show what you relied on and what you did to verify it.

What doesn’t change?

The decision. Verisk’s own framing, through both Khemka and Steven Kauderer, president of Verisk Claims Solutions, is that AI here makes trusted information “more immediate and useful” — it does not make the judgment call. Loss costs still can’t see your client’s specific operation. PAAS guidance still doesn’t settle a classification dispute. A hail history still doesn’t price the roof that’s been replaced since. The data got faster. The judgment layer — challenging a number against an account’s real loss history, knowing what the file should say when the assistant and the underwriter disagree, documenting reliance so it holds up — is still human work, and for brokers it’s the work clients actually pay for.

FAQ

Can brokers or agencies access Verisk data through Copilot, Claude or Amazon Quick themselves? Not under this announcement. Access is for eligible, authorized insurers under their existing Verisk entitlements. Brokers experience it through carrier underwriters.

Which Verisk data is in which platform? Amazon Quick and Microsoft Copilot: ISO Loss Costs and PAAS content. Claude: Verisk Underwriting Intelligence (ISO Loss Costs, now with PAAS added) plus a new Benchmark connector for property-level hail and wind history.

Is this available right now? Verisk announced the integrations on October 28, 2026. Whether a given carrier’s underwriters have it switched on depends on that carrier’s entitlements and its own rollout — ask your carriers rather than assuming.

Does the AI change the loss costs themselves? No. Per Verisk, it’s the same proprietary content under the same entitlements, permissions and governance — delivered through a conversational interface instead of a traditional lookup.

What’s the single most useful thing a broker can do differently? Slow the number down before you repeat it. Ask which loss cost, which effective date, class or account — and get it in writing. The data now moves at chat speed; your verification habit is the brake that keeps it accurate.

Source: Verisk Analytics, Inc., “Verisk Brings Its Proprietary Insurance Intelligence to Amazon and Microsoft AI Platforms, Expands Offerings within Claude,” GlobeNewswire, October 28, 2026. Platform capabilities, eligibility and quotes are Verisk’s, as stated in that release.

Informational only. This article explains an industry announcement for insurance professionals; it is not legal, compliance or coverage advice, and it does not describe any specific carrier’s systems or any specific account’s pricing.