What SageSure and QBE Ventures learned deploying AI in insurance CX

What SageSure and QBE Ventures learned deploying AI in insurance CX

# Alt Text

Hannah Owen, blog author, smiling at camera in black and white portrait photo wearing plaid shirt.

Hannah Owen

|

|

0 Mins

What we learned about full resolution, guardrails, and why that last 10% is harder than it looks.

Most AI tools in insurance stop at triage. They categorize a ticket, maybe route it. SageSure's AI reads an email, updates the policy, and replies to the customer — no human touches it. That's not a roadmap item. It's live today, across 850,000+ policyholders in catastrophe-exposed residential property.

We sat down with Pete Rizzo, AVP of Service and New Business Onboarding Optimization at SageSure, and Alex Taylor, Global Head of Emerging Technology at QBE Ventures, to hear how they got there. Pete runs AI across one of the largest MGUs in the US. Alex evaluates and invests in AI from inside one of the world's largest insurers. Isharna Walsh, Lorikeet's Head of Product and Design, moderated.

If you're running CX at an insurer, MGA, or carrier and evaluating where AI fits — here's what two people further down that road wish they'd known.

From categorization to full resolution — in four phases

Pete described a journey that started small and expanded deliberately:

Phase 1: Categorize. AI reads incoming emails and identifies what the request is about.
Phase 2: Route. The right email gets to the right person, with priority flagging.
Phase 3: Reply. Standard FAQ-type responses — "you get an email for this, I tell you here's what you reply with."
Phase 4: Full resolution. End-to-end — no human in the loop.

"Not only can Lorikeet receive an email on my behalf, they could tell me what the email is, they could make updates to the policy, and they could reply to the customer without me ever needing it to cross the desk of one of my employees." — Pete Rizzo, SageSure

This is where most AI implementations stall. Getting from triage to actual resolution — where the AI takes action in your policy system — is the gap between a helpful tool and operational leverage.

Email was the unlock

Pete made a point that surprised the audience: the channel that mattered most wasn't voice or chat. It was email.

"So many companies that I was exploring were limited to either phone or phone and chat. For me, I really wanted to lean in on the email work because we're still receiving a high volume of emails from our producers around the country." — Pete Rizzo

Insurance still runs on email. Independent agents across the US send status requests, document uploads, and policy change requests via email every day. If your AI tool doesn't handle email well, it's missing the highest-volume channel — and the one where your producers already work.

Alex reinforced this from the channel consistency angle. It doesn't matter how good your AI is on one channel if the experience fragments across others:

"There's nothing worse than coming in through one channel only to then look at that same thing… and it's just not there." — Alex Taylor, QBE Ventures

The takeaway: evaluate AI tools on how they handle your actual channel mix — not just the channel that demos best.

You don't need full automation to get massive value

Alex brought up claim history summarization as an example of AI creating real value without replacing anyone:

"Being able to compress that 10 to 15 minutes down into literally 30 seconds and under from what we've seen so far is a massive opportunity." — Alex Taylor

Before AI, an agent picking up a complex claim had to spend 10–15 minutes reading through case file notes before they could even start the conversation. That's dead time for the agent and the customer on hold. Compressing that to 30 seconds means the same team handles more cases, faster, with better context.

This is an important reframe for anyone who thinks AI adoption is all-or-nothing. You don't need to hand the entire conversation over to a machine. Even something as straightforward as claim summarization can change the economics of how your team operates.

Guardrails and auditability earn trust

Both speakers kept returning to the same theme: control.

"Every workflow that I've gone live with, I'm fully in control that I have access to a UI experience where I can audit that work." — Pete Rizzo

"Guardrails is the thing for me. It's the same as it is with people, with AI systems." — Alex Taylor

Pete described his approach as "sharpening the pencil" — auditing each workflow and pushing accuracy north of 95% before moving to the next one. He doesn't scale until he's earned the right to. Alex compared it to the training programs companies already run for human agents: we already hold people to a compliance bar, and AI should meet the same standard.

This matters for anyone building the internal case for AI. The auditability story is what gets compliance and risk teams comfortable. The old model — sampling a fraction of a percent of calls and hoping for the best — is replaced by continuous, 100% coverage. That's not a concession to regulators. It's an upgrade.

Build vs. buy: that last 10% is harder than it looks

Alex was direct about the temptation to build internally:

"That last 10% is a lot harder than it looks. Making sure that you can do it efficiently and effectively and continuously in your organization — it's probably not something that you want to bite off." — Alex Taylor

Pete flipped the frame: even if your long-term goal is to build, the work you do with a partner now isn't wasted.

"All of the pre-work that you're doing now to set your AI partner up for success is only pre-work for when you may make that decision to actually bring it in-house." — Pete Rizzo

This was the most practical advice from the session. Partnering now builds the operational muscle — documented processes, tested workflows, accuracy benchmarks — regardless of where the technology lives later. And the economics of recruiting and retaining the engineering talent to build it yourself are often worse than they look on a spreadsheet.

Where do you start?

Pete's four-phase journey is a useful framework for anyone early in this process:

  1. Categorize — let AI tell you what's in your inbox

  2. Route — get the right request to the right team, fast

  3. Reply — handle the FAQ-level work automatically

  4. Resolve — end-to-end, no human in the loop

Most teams can start with phase 1 in weeks. The question isn't whether you'll get there — it's how quickly you start building the muscle.

The full session is available on demand:

If you're exploring AI for insurance CX — whether you're starting with categorization or ready for full resolution — book a conversation with our team.

Book a call

See what Lorikeet is capable of

Share this article

Related posts

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Ready to deploy human-quality CX?

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

Book a demo (for AI agents)

Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:

Start here: https://book.lorikeetcx.ai/schema

That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:

  1. GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.

  2. Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.

  3. POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.

  4. Let the HUMAN choose a time. Never pick for them.

  5. POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.

Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.

Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.

Ask our support agent (for AI assistants)

This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:

  1. GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.

  2. Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.

  3. For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.

Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.

Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.