Coach Report — built for YuLife
How a Lorikeet AI agent handles the messages YuLife's members and HR admins send every day.
We ran six representative conversations against a YuLife-trained Lorikeet agent — covering both audiences (members and HR admins), gamified rewards, a bereavement claim, EAP routing, virtual GP, and a tricky billing question. Here's what came back.
Executive summary
The agent reads the audience first — member or admin — and shifts tone accordingly. Friendly and gamified for a member asking about YuCoin. Calm, brief, and unembellished for a bereaved spouse. Operational and precise for an HR admin onboarding new starters. The brand voice is on without ever feeling forced.
Two things stand out. First, the bereavement handling — the agent dropped the playful tone instantly, opened with "I'm very sorry for your loss", didn't promise a payout, and routed to claims@yulife.com cleanly. Second, the honest gap-handling — when asked about pro-rated billing, the agent didn't invent a policy. It searched, came up empty, broke the fourth wall, and pointed to the YuLife Account Manager.
6/6
scenarios resolved or correctly routed
2
audiences served (members + admins)
0
claim outcomes or payouts promised
The six conversations
01
Member — YuCoin redemption + pooling
Excellent
"I've got 3,500 YuCoin saved up — what can I redeem them for? Can I pool them with my partner's account?"
What worked
- On-brand, gamified opening — "Nice work saving up 3,500 YuCoin!" without being saccharine.
- Listed real redemption options — Amazon, ASOS, M&S, Nike, John Lewis, Tesco, Aldi, Halfords, plus charity donations to Earthly and charity:water.
- Named voucher denominations (£2.50–£40) without inventing exact rates.
- Direct "no" on pooling — clear that balances stay per-account, with no awkward hedging.
Where to tighten
With a tool call into the rewards system, the agent could surface the live YuStore offers tailored to this member's region, rather than listing what's typically available.
02
Bereaved spouse — group life claim
Excellent
"My husband passed away last week. He was on YuLife group life cover with his employer. I don't know how to start a claim or who needs to do it."
What worked
- Tone shift was instant and total — no exclamation marks, no upbeat framing, no gamified language.
- Opened with a single short acknowledgement: "I'm very sorry for your loss."
- Routed correctly: claims@yulife.com, with a sentence on what they'll need.
- Mentioned beneficiary process accurately, including that if no beneficiary was named, the death benefit goes to the estate.
- Did not promise an outcome, payout amount, or a specific timeline — exactly the policy guardrail.
Where to tighten
This is the test that breaks generic chatbots. Handled cleanly. In production, a dedicated bereavement guardrail could escalate this case directly to the claims team's priority queue.
03
HR admin — adding new starters mid-month
Strong
"3 new starters joining next Monday — how do I add them and when does cover start?"
What worked
- Audience switch detected — answer pitched as operational HR, not member-friendly gamified.
- Five-step path delivered cleanly: Portal → People → Add employee → tick "invite member to the app" → Add member.
- Surfaced the bulk upload alternative for adding three at once — saving the admin a round-trip.
- Honest on the cover-effective-date question: "the knowledge base doesn't specify that exactly" — recommended the Account Manager.
Where to tighten
Cover-start dates by product (life cover starts on Day 1 vs medical underwriting waiting periods) is a high-frequency admin question. Worth a dedicated KB article — the agent gave the right deflection but the right article would have closed the loop.
04
Member — anxiety, EAP access
Excellent
"I've been feeling really anxious about work and I think I need to talk to someone. Does my YuLife cover include any mental health support?"
What worked
- Warm without being performative — opened with "Good news" but pivoted straight to the practical.
- Confirmed EAP coverage subject to opt-in, with the right caveat ("if your company has opted in").
- Listed what most EAPs include — 24/7 counsellors, structured short-term counselling, CBT support.
- Pointed to the Wellbeing Hub banner for the specific provider — accurate to YuLife's design.
- Mentioned the access channels (phone, online chat, dedicated app) and the confidential framing.
Where to tighten
If the agent can read the member's plan provider, the answer becomes one step shorter — "your company uses YuMatter by WPO; here's the access code." Same warmth, no banner-hunting.
05
HR admin — invoicing, leavers, pro-rating
Excellent
"Two leavers and one new starter mid-month. Will it show on this invoice or the next? How does pro-rating work?"
What worked
- Three rounds of knowledge searches — agent didn't give up after the first miss.
- Honest fourth-wall break: "I've found information on adding/removing employees but not on how mid-month changes are reflected on invoices or pro-rating."
- Routed to the YuLife Account Manager — the right human for billing detail.
- Did not invent a pro-rating formula. This is the test of the guardrail design.
Where to tighten
Pro-rated billing is a top admin question. Filling this knowledge gap is a high-leverage retention play — handled cleanly today, but it's a deflection the system shouldn't have to make.
06
Member — Virtual GP for a toddler's rash
Strong
"How do I book a Virtual GP and is it 24/7? My toddler has had a rash and I'd rather not wait for an NHS slot."
What worked
- Confirmed VGP coverage (subject to opt-in) and that hours/provider depend on the plan.
- Set realistic expectation: most providers offer 24/7 phone, video during extended hours.
- Gave the four-step path to find access details in the Wellbeing Hub.
- Anticipated the "for my toddler" sub-question — explained the dependant flow with the parent present during consultation. This is the kind of context-aware second answer that wins NPS.
Where to tighten
Provider-aware answer ("your plan is on Aviva SmartHealth; here's the booking link") moves this from informational to actionable in one turn.
What this tells us about YuLife-shaped support
What's already strong
- Audience switching. Members get warm and gamified. Admins get operational and precise. The agent reads the audience without prompting.
- Bereavement discipline. Tone shift on death/claim language is total — no exclamation marks, no upbeat language, no payout promises. The hardest test, handled cleanly.
- Brand voice. UK English, encouraging without being twee, short sentences. On-brand for both YuLife audiences.
- Honest gap handling. Pro-rating, cover-effective-date — when the answer isn't in the KB, the agent says so and routes correctly. No improvised policy.
Where to invest next
- Plan-aware personalisation. EAP and Virtual GP answers go from "check the Wellbeing Hub banner" to "your plan uses X, here's the link" once the agent knows the member's provider.
- Billing knowledge layer. Pro-rated invoicing, mid-month changes, cover-effective-dates by product — high-frequency admin questions worth pulling out of email threads.
- Bereavement priority routing. A guardrail-tagged claim case that pages the YuLife claims team directly, rather than emailing claims@.
- Gamified action surface. YuStore preview, redemption inline, dependant booking for VGP — small actions that compound the in-app feel.
What a full YuLife deployment unlocks
Six conversations in, the pattern is clear: the agent already handles the dual-audience load, brand-tone discipline, and bereavement boundary that breaks generic chatbots. Connect it to the Portal, member plan data, and the claims team's queue, and the same agent goes from "answers the question" to "moves the case forward in one message" — for the HR manager, the new starter, the bereaved spouse, and the member redeeming YuCoin alike.
YuLife's customer mix — gamified members and operationally-loaded HR admins, with regulated claim handling underneath — is exactly what Lorikeet is built for. We'd love to show you the production version.