Your clients' staff stop phoning you about dental maximums.
Paige answers plan members from their own class's booklet, in the language they ask in. Set it up once per client and the questions stop reaching your inbox.
Every answer cites the booklet page it came from — hence the name. The web chatbot wears your branding and you can rename it. In Slack, Teams and WhatsApp it stays Paige, because those apps are shared by every plan sponsor.
The questions are simple. Finding the answer is not.
It is in the booklet
Forty pages of carrier legalese, where orthodontics hides under a different maximum from ordinary dental.
So they ask HR
Who has the same forty pages, a day job, and several coverage classes to tell apart.
Then they ask you
A question worth no revenue, arriving at 4:40pm. Multiply by every client you hold.
A link, their own chat tool, or WhatsApp.
Most clients want the link: about a minute, nothing to install. WhatsApp reaches staff who never sit at a screen.
A link you send
Start hereSend it to HR; they post it on the intranet or in the onboarding pack. It also sits on every page of the client's benefits microsite.
- Cites the booklet page for every answer
- Answers in 13 languages
- Hands off to you, or quotes and enrols optional Blue Cross Life critical illness cover
- Anonymous — not even the employer sees who asked
- You choose which booklets each group can reach
Inside the client's Slack or Microsoft Teams
Their IT admin installs Paige into their own workspace. Same booklet, same guardrails, asked in place.
- Direct messages by default; one channel per coverage class
- English only, with no page citations
- Critical illness quotes work here; enrolment opens on a private link
- The workspace is the employer's, so it is less private — members are told first
On WhatsApp, on their own phone
For staff with no desk or work email. You publish a joining link per booklet, the employer puts it on a poster, and an employee taps it and presses send.
- No install and no work account — and the employer cannot see it
- One link per booklet, so a split plan stays split
- Messages travel through Meta, outside Canada; the booklet stays stored here. Members are told first
- We keep a scrambled code, never the phone number. It only ever replies, and one word stops it
The questions you already get.
“Is Invisalign covered, or just regular braces?”
“How much physio do I get in a year?”
“My wife has a plan too — which one do we claim from first?”
“Is my son still covered now he is at university?”
And you see what they ask. The chatbot usage report shows how many conversations each employer's staff start and which topics come up, with a 12-month breakdown per client you can export as a PDF.
The limits are the product.
It does not adjudicate
It explains what the plan says and never promises a claim will be paid. If the booklet is silent, it says so.
It does not see claims
No claims history, no medical information, nobody else's anything. Just the booklet.
It does not discuss pricing
Premiums and renewals are plan-sponsor business; members are pointed to their benefits team.
It does not give medical advice
It will say the plan covers a psychologist. It will not say whether to see one.
Nothing you would have to explain away.
Questions are not kept — no transcript, ours or yours. We record only that a conversation happened: when, where, which booklet, and a topic like “dental”. Never a name, never the text.
One exception: in Slack and Teams the last few messages are held for about 30 minutes so a follow-up works, then cleared. On the web the conversation lives in the member's own browser.
Members are told this before their first question, in their own language. You are the controller; we process on your instructions under the Data Processing Agreement. The exact notice is published at /legal/assistant.
Turn it on for one client and see what they ask.
If nobody uses it you have lost a minute. If they do, you learn what their staff have been quietly not understanding.