Members get answers at 2am, with the clause
A chatbot answers members from your published policies and bylaws, shows the clause it used, and hands unsupported questions to your team.
"If I miss my renewal, how long before my membership lapses?"
Membership lapses if a renewal invoice is not paid within 60 days of the due date, after which a new application is required.
The same questions come back weekly
Member services email is a tax on the team's time. The same handful of questions come back every week, and answering them again teaches nobody anything new.
Some of the answers are wrong, because the policy book is long and the index has not kept pace with changes. A member gets a confident answer that turns out to be out of date.
From policies to a live chatbot
Certant reads your policy library, bylaws and published guidance.
It works out how the policies, member types and rules relate to each other.
A chatbot in your branding goes on your member portal or website.
Open the clause behind the answer
A member asks about a membership rule and the reply links to the clause. One click opens the bylaws at that page, so the member can read the wording for themselves.
"If I miss my renewal, how long before my membership lapses?"
Your membership lapses if the renewal invoice isn't paid within 60 days of the due date. After that you'd need to submit a new application.
Membership Bylaws 2025.pdf · page 14
§5.2 Membership lapses if a renewal invoice is not paid within 60 days of the due date, after which a new application is required.
Unsupported questions go to your team
When the policies don't cover a question, the chatbot says so and passes it to member services with the conversation attached. It doesn't guess, and it doesn't advise a member about their own circumstances beyond what the documents say.
"Can you waive my late fee this year?"
Your policies don't cover fee waivers for individual members, so I can't answer that. I've passed your question to the member services team, who will reply by email.
What setup involves
You load the documents you already publish to members. The chatbot answers from those and nothing else.
| Area | What to expect |
|---|---|
| Sources | Answers come from the policies, bylaws and guidance you approve. |
| Member records | The chatbot doesn't see a member's record. That needs a connection to your membership system, confirmed for your deployment. |
| Hand-off | You choose where unsupported questions go and which topics always go to a person. |
What changes
- Members get a cited answer whenever they ask, not only during office hours.
- The team stops repeating itself and spends the time on the questions only a person can answer.
- Every answer points at the clause it came from, so nobody has to take the chatbot's word for it.
Related use cases
HR policy self-service
Answers from the handbook, enterprise agreement and benefits policy, with exceptions sent to HR.
See the use caseIT helpdesk self-service
Answers from your runbooks, with a hand-off to the service desk.
See the use caseDocument intake routing
A proposed category and destination team for each incoming document.
See the use caseSee it answer from your policies
Send us a few of your policy documents and we'll show you the answers and the clauses behind them. Or start free and load them yourself.