The challenge
A customer at eleven at night, working out whether a certificate renews on its own or whether she has to do something. A small-business owner comparing two business checking accounts on a Sunday, deciding which one to open in the morning. Somebody who cannot get into online banking and does not want to wait until Monday to ask why.
The bank has the answer to all three, published and approved, sitting on its own website. The problem is that the website was built to present products rather than to answer questions, so finding the answer means knowing which page it lives on. The questions were arriving, and the site was replying with a navigation menu.
The solution
- It answers, and it does not advise. A bank can tell you what a product does and what its terms say. It cannot tell you what to do with your money. Retrieval limited to published material keeps the assistant on the right side of that line by construction, rather than by hoping a general model stays there.
- Rates and terms are current, or absent. A rate quoted from last quarter is worse than no rate at all, so the corpus tracks what the bank has actually published and the assistant declines when the published answer is not there.
- Safe in front of anyone. A public assistant on a bank’s website takes every question, including ones about specific accounts it must never attempt to answer. The refusal behavior matters as much as the answers.
- Marketing runs it. The persona has been rewritten 58 times by the bank’s digital marketing team since launch. A community bank has no engineers sitting idle, so if changing the wording needs a ticket and a release, the wording stops being changed and the assistant drifts out of date.
The capability that changed it
An assistant that only replies is a better FAQ. The change came when actions were switched on, so a question could end somewhere useful: the right product page, the right application, the right branch.
Roughly one automated action now fires for every question asked. For a bank, that is the difference between deflecting a call and starting an account opening at eleven at night.
The results
| Measure | To Date |
| Consecutive days with a question answered | 330 |
| Questions this year against the year before | 5.6× |
| Questions asked, raw | 15,013 |
| Satisfied answer rate, latest quarter | 96.5% |
| Support tickets raised in two years | 0 |
Set the last twelve months against the twelve before and the assistant handled 5.6 times as many questions, climbing from under 200 a month to over 1,000. Nothing was relaunched and no campaign ran behind it. People used it, came back, and told others it was there.
The streak is what makes that credible. A question has been answered every day for 330 days and counting, weekends and holidays included, with nine in ten resolved from the bank’s own published material.
Then the number nobody asks for: zero support tickets across two years of continuous operation. The bank has renewed on enterprise terms and is into its second enterprise term.
Why it worked
- Grounding that suits a regulated balance sheet. Own-content-only retrieval with honest refusal. A bank needs an assistant that declines cleanly more than one that always has something to say.
- A marketing team can run it alone. Fifty-eight persona rewrites by the people who own the brand voice, with nothing between a decision and the live site.
- The answer leads somewhere. Roughly one automated action per question, routing customers into the right application instead of stopping at a paragraph.
- It keeps working without being looked after. Two years, 600 active days, zero support tickets, no migration, no rebuild.