The challenge
A student halfway through the qualification, working out which pathway now applies to her. A practicing member checking what this CPE cycle requires of him, and whether the course he just booked counts. An employer verifying a credential before an offer goes out.
None of them knows the term the body files that answer under, because a national body publishes for the record. Its material is organized the way a regulator organizes things rather than the way a member searches. The answer is published, it is right, and it still generates an email to the team.
The solution
The evaluation was run out of IT rather than marketing, with the digital experience team alongside it. That shaped the criteria, because the people judging the assistant were the ones who would carry the consequences of a wrong answer.
- Answer only from published material. When a question touches CPE obligations or eligibility for a practicing certificate, a confident wrong answer becomes a compliance problem with the member’s name on it. Honest refusal was a stated requirement, tested on the content with consequences before anything easier.
- One corpus, four audiences. A prospective member, a student mid-qualification, an employer checking a credential and a practicing member chasing a technical point all arrive at the same site. One assistant handles all four, with no login between them and a published answer.
- Hold the advice boundary. A professional body can tell you what its requirements say. It cannot tell you what to do about your client. Own-content-only retrieval keeps the assistant on the first side of that line by construction.
- Run it without a project team. No integration program, no standing internal headcount, no rebuild at renewal. A small IT function owns it alongside everything else it does.
The capability that decided it
A national body’s authority is partly a matter of language, a register that took decades to establish. Hand it to a vendor template and the assistant stops sounding like the institution within a sentence.
So the persona is written inside the product by the body’s own staff and has been revised 34 times since launch: lead with the direct answer, cite the source, say plainly when the published material does not cover the question. When the tone needs to change, it changes that afternoon, with no engineering ticket and no vendor in the loop.
The results
| Measure | To Date |
| Year-on-year growth in questions asked, matched periods | +50% |
| Current weekly volume against its own six-month baseline | +24% |
| Questions answered to date | 7,351 |
| Satisfied answer rate, latest quarter | 96.6% |
| Arriving through live chat | 85% |
Set the most recent run of months against the same months a year earlier and questions asked are up 50%, with current weekly volume a quarter above the six-month average. Most deployments peak in their first weeks and decay. This one has done the opposite, and nobody campaigned for it. At its busiest stretch a question arrived every day for twelve consecutive weeks.
Behind that sits the number that makes it possible. Where the body’s own material covers the question, 96.6% of the answers land well. Traffic only compounds when the answers hold up.
Two terms are complete and a third is in motion, with no relaunch, no migration and no second procurement.
Why it worked
- Grounding suited to a regulator’s content. Own-content-only retrieval with honest refusal. Where content carries obligations, a model that declines to guess beats one that is usually right.
- A voice the institution controls. The persona is written and revised by the body’s own team, in the product, without an engineering ticket.
- Placed where the questions already arrive. Live chat on the open site, in the moment somebody is stuck, rather than a search box on a page nobody visits.
- It keeps running without being rebuilt. A small IT function owns it outright, which is why there is a third term rather than a fresh evaluation.