The stakes in financial advisory are different from most professions. A poorly configured AI that says the wrong thing to a prospect — about investment performance, market conditions, or specific product recommendations — creates regulatory exposure, not just a bad first impression.
The difference between a generic AI voice receptionist and one trained on a financial advisor's knowledge base comes down to what it can actually answer. A generic system handles calls professionally but cannot tell a prospect what the firm's minimum investment threshold is, what the onboarding process looks like, or how the practice is structured.
A knowledge base changes that: it means populating the AI with your firm's specific information — services offered, minimum investment levels, client onboarding process, and the questions prospects ask most often — so every inbound call is handled accurately and consistently, within defined compliance boundaries.
What makes this different from configuring an AI receptionist for almost any other profession is the compliance dimension. Every piece of information added to the knowledge base, and every boundary drawn around what the AI will and will not say, needs to be reviewed through a compliance lens before the system goes live.
This guide is for independent RIAs, solo advisors, and small advisory teams evaluating how to configure an AI voice receptionist to represent their practice accurately — including what information to include, what to exclude, and where to draw the compliance boundary.
According to ncontracts.com's 2026 RIA AI analysis, 40% of investment adviser firms have implemented AI tools internally — but 44% of those firms have no formal testing or validation of their outputs. For financial advisors deploying an AI voice receptionist, the knowledge base configuration is exactly where that validation needs to happen.
OnceHub's AI Phone Receptionist's launch is built around scheduling as the primary outcome, with a knowledge base layer that allows advisors to populate the AI with their firm's specific information. This article walks through how to build that knowledge base well.
What a knowledge base is: A knowledge base is the structured body of information that an AI voice receptionist draws on when responding to caller questions. Rather than relying on generic AI responses, the system answers using the specific information the advisor has provided — their firm's services, their minimum investment requirements, their onboarding process, their fee structure, their geographic focus, and the common questions their prospects ask.
What a knowledge base is not: A knowledge base for an AI voice receptionist is not a source of investment advice. It is not a place to store market commentary, portfolio recommendations, or performance projections. The information it contains should be factual, firm-specific, and bounded — answering the questions a well-trained human receptionist would answer, not the questions that require the advisor's professional judgement.
Why this distinction is especially important in financial advisory: In most professions, an AI that gives an imprecise answer to a caller question creates a minor inconvenience. In financial advisory, an AI that makes an unauthorised statement about investment performance, risk, or suitability creates a potential regulatory event. The knowledge base configuration is where the boundary between helpful information and regulated advice is drawn — and that boundary must be reviewed by the firm's compliance officer before the system goes live.
A well-configured knowledge base enables three things:
Why this comes before everything else: The compliance boundary determines what the AI is allowed to say. Building the knowledge base before defining the boundary means some of what is built will need to be removed — or worse, will go live and create regulatory exposure.
The SEC's 2026 Examination Priorities specifically identify AI tool usage as a key examination focus area. The expectation is explicit: firms using AI in client-facing workflows must have governance policies that define what the AI does and does not do, reviewed and approved before deployment.
What the AI voice receptionist should be configured to answer — within compliance boundaries:
What the AI voice receptionist should be explicitly configured NOT to answer:
The practical compliance step: Before any knowledge base content goes live, the list of questions the AI will answer — and the answers it will give — should be reviewed and approved by the firm's compliance officer. Document this review. The SEC's 2026 Examination Priorities make clear that AI governance documentation is now an examination expectation, not a best practice.
Additionally, ask the OnceHub team about current options for keeping the knowledge base aligned with your compliance-approved website copy — such as fee schedules or your ADV — so the information stays current without manual re-entry each time compliance approves an update. Confirm exact capabilities and setup requirements before relying on this for a regulated content workflow.
The structure that works best: organise the knowledge base around the six questions a first-time prospect is most likely to ask when they call a financial advisory practice for the first time. These are the questions a well-trained receptionist would answer — factual, firm-specific, and within defined compliance boundaries.
This is the first thing a prospect wants to understand. The AI should be able to give a clear, accurate description of the firm's service model and client profile — without overpromising or making claims that require verification.
What to include:
What to avoid:
For practices with defined minimums, this is one of the most commercially important pieces of knowledge base content — it allows the AI to screen prospects before they reach the advisor's calendar.
What to include:
Compliance note: Minimum investment thresholds are factual disclosures — they do not constitute investment advice and are appropriate for knowledge base inclusion after compliance review.
OnceHub's AI Phone Receptionist integration: When a caller's responses indicate they do not meet the firm's minimum criteria, the AI uses this knowledge base content to handle the redirection professionally — not by abruptly ending the call, but by acknowledging the situation and directing the caller to an appropriate resource.
Prospects who are genuinely evaluating an advisor want to understand what the relationship looks like. A clear, accurate description of the onboarding process answers this question before it is asked — and signals professionalism.
What to include:
Fee transparency is one of the most common prospect questions — and one of the most sensitive from a compliance perspective. The knowledge base should address this at a general level without providing specific quotes that require individual suitability assessment.
What to include:
What to avoid:
Beyond the structured categories above, the knowledge base should include answers to the specific questions the advisor or their team receives most frequently from new prospects. These are practice-specific — they vary by niche, service model, and client profile.
Common examples across advisory practices:
How to build this list: Ask the advisor — or their existing team — what questions come up most frequently in first conversations with prospects. The answers to those questions, reviewed for compliance appropriateness, become the FAQ layer of the knowledge base.
OnceHub's AI Phone Receptionist draws on this FAQ layer when responding to questions outside the structured qualification flow — allowing the AI to give accurate, firm-specific answers to common prospect questions rather than defaulting to generic responses or routing every question to the advisor.
The knowledge base should include explicit instructions for what the AI should say when a caller asks something outside its configured scope. This is as important as the information included — and is the configuration step most commonly skipped.
What to configure:
Why qualification matters as much as the knowledge base: The knowledge base determines what the AI knows. The qualification flow determines who gets access to the advisor's calendar. For a solo RIA or small advisory team, protecting calendar time from unqualified prospects is as operationally important as answering common questions accurately.
The principle: three to five qualification questions, delivered conversationally. Each question serves the dual purpose of gathering qualification information and signalling to the prospect that this is a thoughtful, professional practice.
What these capture: nature of the trigger event, investable assets as a qualification signal, current advisor situation, urgency, and referral source.
What these capture: presenting need, planning experience and expectations, life stage, urgency, and referral source.
What these capture: business context, specific planning need, existing professional relationships, urgency, and referral source.
OnceHub's AI Phone Receptionist handles this qualification flow natively — the questions, their sequence, and the routing logic that follows are all configured within the same system that checks availability and confirms the booking. No third-party qualification tool required.
Caller meets the investment minimum, expresses a clear planning need, and has a defined timeline. The AI offers a discovery meeting slot from the advisor's live calendar. The booking is confirmed during the call. The advisor receives a notification with the prospect's qualification responses already captured.
Workflow: Inbound call → greeting → qualification questions → meets criteria → availability checked natively → slot offered → booking confirmed → advisor notified with context → Meeting Coordinator takes over for attendance confirmation and no-show recovery (confirm current release status with the OnceHub team).
OnceHub's AI Phone Receptionist confirms this booking within its native scheduling engine — the slot offered reflects accurate, live availability at the moment it is offered. No third-party calendar API in the booking step. Qualification data pushed to connected CRM automatically.
Caller expresses interest but does not clearly meet the qualification criteria — assets are below the minimum, timeline is vague, or the presenting need is outside the firm's specialism. The AI should not book a full discovery meeting but should handle the caller professionally.
Options:
Caller is clearly outside the firm's client profile — or asks a question that falls outside the knowledge base boundary. The AI handles this professionally, using the explicit boundary language configured in Category 6 of the knowledge base.
The key principle: never improvise outside the knowledge base. If the AI does not have a configured answer to a question, it should say so and offer to connect the caller with the advisor — not attempt an answer that may be inaccurate or non-compliant.
If a call needs to be escalated to the advisor directly while still in progress, confirm with the OnceHub team what live-call escalation options are available on your plan before relying on this for high-stakes calls.
Without a configured AI voice receptionist: A prospect referred by a significant existing client calls at 2:15 PM on a Thursday. The advisor is in a portfolio review. The call goes to voicemail. The prospect — a high-net-worth individual evaluating advisors — does not leave a message. By the time a callback happens Friday afternoon, the prospect has already spoken with another firm that answered immediately.
With OnceHub's AI Phone Receptionist: The same call arrives at 2:15 PM. The AI answers with a professional greeting that reflects the firm's brand. It works through the qualification questions — the prospect's situation, investable assets, current advisor relationship, and timeline. The prospect qualifies. The AI checks live availability within OnceHub's native scheduling engine and offers two discovery meeting slots for the following week. The prospect selects Thursday at 9:00 AM. A calendar confirmation lands in their inbox within seconds.
The advisor finishes the portfolio review to a booking notification — prospect's qualification responses, approximate AUM range, referral source, and stated timeline already captured. The discovery meeting begins with context already established.
Without a configured AI voice receptionist: A business owner evaluating advisors for a business transition calls at 7:30 PM after their own workday ends. The call goes to voicemail. The advisor's voicemail box is full. The prospect moves on.
With OnceHub's AI Phone Receptionist: The call is answered immediately. The AI works through the qualification flow, identifies the business transition context, and routes appropriately. If the prospect qualifies, a discovery meeting is confirmed on the original call — the advisor's availability enforced natively without the advisor being present. The prospect leaves with a confirmed appointment at 7:34 PM.
The advisor wakes up the following morning to a new booking notification — context captured, CRM updated, calendar confirmed.
Without a configured AI voice receptionist: An existing client calls with a common question — what documents do they need for their annual review? The advisor is with another client. The client is placed on hold, then leaves a message. The advisor returns the call two hours later. The client feels the friction.
With OnceHub's AI Phone Receptionist: The existing client calls. The AI recognises the nature of the enquiry — an annual review preparation question. The answer is in the knowledge base — the firm's standard document checklist for annual reviews. The AI provides the answer accurately and professionally, handles the call to completion, and logs the interaction. The advisor is not interrupted.
When the question falls outside the knowledge base — account balances, transaction queries, investment questions — the AI routes immediately to the advisor with context captured, rather than attempting an answer it was not configured to give.
Most AI voice receptionists are built as general-purpose tools and adapted for financial services after the fact. OnceHub's approach starts from the opposite direction: scheduling, qualification, and knowledge base configuration all live inside the same native system, rather than being stitched together across a calendar integration, a separate AI vendor, and a third-party CRM connector.
For a financial advisory practice specifically, that matters in three concrete ways.
First, because the scheduling engine is native rather than API-dependent, the discovery meeting slot a prospect books during the call reflects the advisor's actual live availability, there is no separate sync step where a slot could go stale between the call and the confirmation.
Second, the qualification flow and the knowledge base sit in the same configuration layer, so a prospect's investable-asset range, current advisor status, and timeline are captured automatically alongside the booking, rather than requiring a separate intake form.
Third, the compliance-first framing built into the knowledge base setup — explicit boundaries for what the AI will and will not answer — maps directly onto what the SEC's 2026 Examination Priorities are asking firms to document, rather than requiring the advisor to bolt compliance controls on afterward.
None of this replaces the advisor's own compliance review, and current feature availability, release status, and documentation should always be confirmed directly with the OnceHub team before deployment. But for a solo RIA or small advisory team evaluating where to start, having scheduling, qualification, and knowledge base configuration in one native system — rather than three separately managed tools — is the practical advantage worth weighing most heavily.
A knowledge base for an AI voice receptionist is the structured body of firm-specific information the AI draws on when responding to caller questions. Rather than relying on generic AI responses, the system answers using information the advisor has provided — their services, minimum investment thresholds, onboarding process, fee structure, and common prospect questions — reviewed and approved for compliance appropriateness before deployment. It is not a source of investment advice. It is the factual, firm-specific information a well-trained human receptionist would use to answer common questions accurately and consistently.
The knowledge base should include: a description of the firm's services and client profile; minimum investment thresholds if applicable; a general description of the onboarding process; general information about fee structure without specific rate quotes; answers to common prospect questions; and explicit instructions for what the AI should say when a caller asks something outside its configured scope. All content should be reviewed by the firm's compliance officer before going live.
The knowledge base should not include: specific investment recommendations or portfolio strategies; market commentary or performance projections; specific fee quotes or rate comparisons; account balance information or transaction-related content; any statement touching on suitability, risk tolerance, or specific product recommendations. The boundary between helpful firm information and regulated investment advice should be drawn explicitly — and reviewed by a compliance officer — before any knowledge base content goes live.
The SEC's 2026 Examination Priorities identify AI tool usage as a key examination focus area. Examiners are asking for AI governance documentation — including written policies defining what AI tools are permitted to do, vendor oversight documentation, and evidence of compliance review before deployment. A financial advisor deploying an AI voice receptionist should maintain a written record of what the system is configured to answer, what it is configured not to answer, and who reviewed and approved the configuration. This documentation should be maintained in the firm's compliance files alongside other AI governance records.
A well-configured AI voice receptionist recognises when a caller asks something outside its configured scope and routes gracefully to the advisor — capturing what it could from the conversation first. The system should never improvise an answer to a question it was not configured to handle. In OnceHub's AI Phone Receptionist, the boundary instructions are configured explicitly — defining the standard response for out-of-scope questions and the routing logic that follows.
Before going live: have the knowledge base content reviewed and approved by the firm's compliance officer; configure explicit boundary instructions for investment advice questions and account-related queries; confirm call recording consent handling for all states where the firm serves clients; obtain written data handling and retention documentation from the vendor for the Reg S-P vendor oversight file; complete a written AI governance record documenting what the system is configured to do and who approved it; and complete test calls covering both standard qualification scenarios and out-of-scope boundary scenarios.
OnceHub's AI Phone Receptionist — launching August 13, 2026 — allows financial advisors to populate a knowledge base with their firm's specific information, which the AI draws on when responding to caller questions. The knowledge base operates within the same system that handles the qualification flow and booking confirmation — so the AI can answer a prospect's question about the firm's services and then immediately offer a discovery meeting slot from the advisor's live calendar, all within a single call. Confirm current knowledge base capabilities and compliance documentation with the OnceHub team directly before deployment. See oncehub.com/pricing for current plan details.