Contact us
Live demo

AI-powered support for Real Insurance

Lorikeet is an AI customer support agent built for regulated industries like insurance. This demo runs on Real Insurance's real product portfolio. The same agent handles outbound Quick Quote callbacks, inbound voice, and inbound chat — with a clean handoff to a human specialist whenever judgement is needed. Pick a customer below and the agent will ring your phone within seconds.

Have the agent call you

Pick a customer scenario, enter your mobile, and the AI agent will ring you to follow up on their Quick Quote.

Helen Marsh — Happy path
Life Insurance · $400,000
Submitted a Life Insurance Quick Quote three days ago — $400,000 cover, NSW, non-smoker. She's at home and ready to chat. Easy transfer.
Role-play: confirm "yeah I've got a minute" when the agent recaps your quote.
Tom O'Brien — Doesn't remember
Funeral Cover · $15,000
Submitted a Guaranteed Funeral Cover quote five days ago — $15,000, VIC. Half-forgot about it. Agent needs to recap the inquiry cleanly without sounding pushy.
Role-play: ask "wait — what's this about?" and see if the agent jogs your memory before pushing transfer.
Mark Henderson — Price objection
Income Protection · $5k/mo
Submitted an Income Protection quote two days ago — $5,000 a month, QLD. Got cold feet on the price. Agent must acknowledge price honestly, never defend or quote specifics, and still offer the specialist.
Role-play: push back with "it's more than I want to pay" and see how the agent handles it.
Jess Walker — Not a good time
Life Insurance · $750,000
Submitted a Life quote yesterday — $750,000 cover, WA. School pick-up. Agent must capture a callback window without pushing for a transfer.
Role-play: say "I'm driving, can't chat" and give a window like "tomorrow afternoon after 2pm".

How it works

  1. Pick one of the four customer scenarios above and enter your mobile number.
  2. You'll get a call from a Lorikeet-powered AI agent within a few seconds — Australian voice (Emma).
  3. The agent opens with a real Quick Quote recap (for example: "hi, calling from Real Insurance about the $400,000 Life cover you put in three days ago"), then handles the scenario you've picked.
  4. Behind the scenes a Lorikeet conversation flow runs the call — looking the customer up, checking specialist availability, transferring to Genesys, and logging the outcome.

Or chat with the agent — it works inbound too

The same agent that runs the outbound callback also handles inbound questions on chat or voice — existing-policy servicing, claims intake, FAQs, and the conversational version of the Quick Quote form. Click any prompt below to drop it into the chat widget, or ring the voice line.

Click any prompt to copy it.

Type anything you like — the agent rolls with whatever name, policy, or details you give it.

Call +61 7 4802 7084

What the agent handles for Real Insurance

Three categories, mapped to Real Insurance's existing Genesys queues. The agent confirms details before any write and routes anything that needs human judgement back to the right specialist with full context.

Sales — quotes inbound and outbound

The agent runs the Quick Quote intake conversationally on inbound voice or chat — same fields, same order as your web form. On outbound, it calls customers who didn't complete sign-up, recaps the exact cover amount they picked, handles standard objections, and warm-transfers to a Sales specialist in Genesys.

Self-service for existing policy holders

The everyday admin that doesn't need a specialist — updating contact details, swapping a card or bank account, resending an annual statement or policy schedule, or rescheduling the next premium debit within the 14-day policy rule. Spell-confirmed, masked where it matters, written back across every active policy in one tool call.

Warm handoff to a specialist

Anything that needs human judgement — a new claim, beneficiary change (signed form), cancellation, or a customer in distress — gets a calm, structured intake then a warm transfer to the right Genesys queue (Sales, Service, or Claims) with full context. The agent never makes a claim decision, quotes a payout, or pretends to action a regulated change live.

How we built this

Four steps. Grounded in Real Insurance's public website and the conversations a regulated-insurance support team has every day.

1

Walked the real site

Scraped realinsurance.com.au and walked through every Quick Quote form (Life, Funeral, Income Protection) on the live site. Each agent reply is grounded in Real Insurance's actual products, policies, and contact-centre queue structure.

2

Wrote the conversation flows

Nine plain-English conversation flows — one per topic — plus a knowledge-base fallback. Each one repeats key details back to the customer before saving anything, and follows Real Insurance's product structure.

3

Stubbed the system calls

Eleven mock backend calls stand in for the real integrations — looking up a customer, writing a contact-detail change, transferring to a Genesys queue, capturing a claim, logging an outbound call outcome. The Quick Quote payload is real enough that the outbound recap names the actual cover amount the customer picked.

4

Stress-tested it

Sixteen conversation scenarios — outbound sales, inbound servicing, claims, beneficiary change, cancellation, FAQ, and a crisis path — re-run five times each. The same suite runs every time the conversation flow changes, so regressions get caught before any real customer hears them.

What's next

Where this would go in production — same agent, plugged into Real Insurance's real systems.

1

Connect to the real systems

Replace the mock backend calls with real integrations — the policy admin platform, Genesys Cloud queues, and the Quick Quote form pipeline. Read-only access first, so the agent can look things up before it can change anything.

2

Phase 1 — read-only outbound

Run the outbound Quick Quote callback on real customer records. Auto-tagged transcripts and conversion outcomes feed Power BI directly — no per-call manual review.

3

Phase 2 — inbound write-back servicing

Switch on the inbound self-service flows (contact details, direct debit, document resend, premium reschedule). Every write is gated by a spell-confirm and a guardrail check. Beneficiary, claims, and cancellations stay warm-handoff to a human specialist.

4

Scale across the Greenstone portfolio

Same platform, same simulation suite, same reporting — extended to Australian Seniors, Buddy, Choosi, Guardian, Kogan, and the Canada expansion. One change tested across the whole portfolio in minutes.

Built for regulated financial services

Lorikeet was built for regulated industries — insurance, financial services, healthcare — where privacy, residency, and conversational safety are non-negotiable.

Multi-region data residency

Lorikeet runs in Australian, American, and European data regions. Australian customer data can stay in Australia. The same agent setup serves the Canada expansion from the American region.

No personal financial advice

A guardrail blocks the agent from recommending a cover amount, comparing competitors on suitability, or steering customers to a specific product. Every advice question routes warmly to a human specialist.

Calm under crisis

If a customer shows signs of distress, the agent surfaces the right local crisis support resources and routes immediately to a human team member, skipping any routine flow.

Simulation-driven safe changes

Every change to the agent's behaviour automatically re-runs sixteen conversation scenarios. Regressions are caught before any real customer hears the new version — no need to pause production to fix a prompt.

Structured call outcomes for reporting

Every conversation ends with a structured outcome — transferred, callback, declined, objection categories. Power BI and Datadog get clean events. Quality reviewers focus on exceptions instead of listening to every call.

Genesys-native handoff

Lorikeet drops the conversation into the right Genesys queue (Sales, Service, or Claims, by product) with structured context. The human specialist picks up where the agent left off — the customer doesn't repeat themselves.

Want to see this on real data?

Happy to walk through the simulation suite, the Genesys integration, and how this would land in production.

Talk to the team