Interactive demo · For Monday

Two AI agents, one shared GemHub line

An outbound agent that confirms event attendance and dietary requirements, and an after-hours agent that answers basic questions and books a callback. Both disclose they're AI upfront — built specifically with the over-50 cohort in mind.

Try it yourself

Pick a path — we call you, or you call us

Left side mimics the manual events confirmation calls (Phase 1). Right side mimics an after-hours call to GemHub (the inbound use case).

Outbound · we call you

Event registration confirmation

Pick a registrant. The AI rings you, opens by saying it's an AI assistant from the GemLife events team, and runs the same script the events team does today — attendance, dietary, +1 guests.

Margaret Thompson

Highlands Discovery Day · Saturday 10am

Solo registrant, no dietary on file. Cleanest happy path.

John & Patricia Wilson

Pacific Paradise Open Day · Sunday 11am

Patricia is gluten-free. Bring a +1 (daughter) — tests dietary + guest capture.

David Chen

Maroochy Quays Information Evening · Thursday 6:30pm

Conflict has come up. Tests reschedule + offering a morning callback.

Your phone number

Inbound · you call us

After-hours GemHub line

After 6pm calls go to voicemail today. Instead, give this number a ring. The AI answers, says it's AI, helps with the easy stuff, and books a callback for first thing in the morning.

Dial this number

+61 468 056 580

0468 056 580 from within Australia

Try saying:

"What's the deal with GemLife, is it like a retirement village?"
"What's the starting price at Pacific Paradise?"
"Can I book a tour for next weekend?"
"Am I talking to a person or a robot?"

What each agent does

Tight scope on both sides

Manuel's brief on the call was clear — keep the scope narrow, lean on the handoff to humans, don't try to do everything. That's what this is.

Outbound · event confirmation

Replaces the manual all-day call session the events team does today.

"Hi Margaret, this is the GemLife events team — just a quick AI-assisted call to confirm your registration for the Highlands Discovery Day on Saturday. Is now a good moment?"

Confirms attendance · captures dietary · captures guests
Discloses AI upfront, again if asked
If they want to reschedule or talk to a person → books a morning callback
Logs everything to the ticket for the events team in the morning

Inbound · after-hours support

Replaces the voicemail-then-call-back-at-7:30am loop.

"Hi, thanks for calling GemLife. The GemHub team has clocked off — I'm GemLife's AI assistant covering after-hours calls. I can answer general questions and book you a callback for the morning. What can I help with?"

Handles general questions about GemLife · defers pricing & availability to the team
Collects name, what it's about, best callback number & time
For complaints or anything urgent → flags it and tells them to call 000 if safety-related
Promises a callback first thing — warm handoff, no cold voicemail

A few things we'd want to confirm with you before going live

Which resorts & events should the agent know about by name? We've used Highlands, Pacific Paradise and Maroochy Quays as placeholders.
Should the agent disclose AI upfront on every call, or only when asked? (Manuel leaned upfront — we've gone with that.)
What does the GemHub team want logged on the ticket for the morning callback list? (Right now: name, topic, callback number, preferred time, urgency.)
For voicemail and "not a good time" — should we retry, or leave it for the events team to follow up manually?
Salesforce campaign linkage — happy to wire this to the live registrants for the pilot, or keep mocked for the first round?