Inquiry intake forms for financial advisors

Start with the advisor’s first useful question

Ask advisors what they need to know before acknowledging a request. In many firms, the useful starting context is the visitor’s name, organization or household label, relationship to the firm, and purpose of the inquiry. That information helps distinguish a new introduction from an existing-client service request without asking for account numbers or detailed financial facts.

Write fields in visitor language. “How are you connected to our firm?” is clearer than “relationship classification.” “What would you like help with today?” is more welcoming than “service category.” Offer “I am not sure” when a visitor cannot tell whether they need an advisor, client-service associate, or operations contact.

Keep the first intake proportional to the request. A prospective client asking how to arrange an introduction does not need to complete a full risk-profile questionnaire. An existing client who needs a meeting with their service team may need only a short description and a preferred conversation mode. The intake should prepare a human response, not attempt to complete a financial planning process.

A practical core field set

Most advisory firms can begin with five fields:

• **Name:** so the first response can address the visitor naturally. • **Organization or household label:** enough context to recognize the relationship, without unnecessary account detail. • **Relationship:** prospective client, existing client, referral partner, professional contact, event guest, vendor, or another visitor. • **Purpose:** request an introduction, ask a general firm question, arrange a service conversation, or follow up on an existing relationship. • **Additional context:** optional free text in the visitor’s own words.

Only request a contact detail when your follow-up process uses it. If the visitor can continue in the Kiguri conversation, do not add a second field simply because it appears on a typical lead form. If you do ask for an email or phone number for offline follow-up, explain why and what the visitor should expect next.

Avoid requesting passwords, full account numbers, tax records, detailed holdings, or sensitive personal information in an open reception flow. The form is for routing and context. A qualified employee can explain the appropriate channel for any later discussion that requires narrower handling.

Route by relationship and purpose

Define a routing policy that advisors and service staff can follow:

• A **prospective client** goes to the designated introduction or business-development host. • An **existing client** goes to the relationship owner or client-service team. • A **referral partner** goes to the partnerships or professional-relations owner. • An **event guest** goes to the event host or general reception owner. • A **vendor or operational contact** goes to the operations owner. • An **uncertain visitor** goes to a reception host who can clarify the request.

These categories are your firm’s policy, not automatic Kiguri classifications. Kiguri can capture what the visitor says and display it in the response queue. A host can accept or reassign the conversation while preserving the original context. The customer inquiry routing guide has examples of routing by purpose and keeping handoff notes useful.

Do not label a route with a promise such as “personalized investment advice.” Use neutral language such as “request a conversation with an advisor.” A visitor can then explain their situation to an appropriate person, who decides what discussion is suitable.

Keep approved AI answers narrow

The AI receptionist can answer stable, approved questions about the firm’s public introduction, reception process, visitor destinations, and how to request a host. Assign an owner to review those answers when office hours, service descriptions, event details, or team responsibilities change.

The AI should route questions that require professional judgment or client-specific context. Examples include requests for a recommendation, a prediction about returns, an interpretation of a tax or regulatory issue, a suitability question, a fee exception, or a discussion of a private account. It should not infer a risk profile or present a general answer as advice.

A useful boundary message is: “I can help route your question, but an advisor must discuss personal or account-specific matters with you.” This is a workflow statement, not a legal disclaimer. Have your own specialists approve the wording and the underlying process.

Connect the form to a response queue

An intake form needs an owner after submission. Kiguri’s response queue presents the visitor’s identity, organization, relationship, purpose, and description to employees who can accept or reassign the inquiry. Decide who watches the queue during published hours and what happens when the firm is offline.

Use the same labels in the queue and in the form. If the form says “existing client,” the queue should not obscure that context behind a generic “support lead” label. Include the visitor’s free-text message so the first response can acknowledge the actual request.

When an employee is available, Kiguri supports a live handoff through chat, browser phone, video, or screen sharing. A private consultation room can be the next step when an advisor accepts a conversation that should move out of general reception. Tell the visitor what mode is being offered and avoid suggesting that an availability indicator guarantees immediate advice or an appointment.

Design the offline path before launch

Financial advisory inquiries often arrive outside the firm’s preferred hours. Write an offline message that confirms the inquiry was received, explains who reviews it or when it is reviewed, and tells the visitor what context is helpful for follow-up. Do not promise a response time unless the firm can consistently meet it.

Test the offline path with a prospective client and an existing client. Can they tell whether they need to wait, add context, or use another approved contact method? Can the assigned employee understand the request without asking the visitor to submit sensitive information again?

Pilot with realistic scenarios

Run at least five walkthroughs: a prospective client requesting an introduction, an existing client needing service help, a referral partner asking about collaboration, an event guest looking for the host, and a visitor with an account-specific question. Check whether the form asks only useful questions, whether the queue shows the right context, and whether the handoff language avoids advice or outcome promises.

Ask advisors to read the handoff as if they had never seen the original visitor link. If they still need to ask who the visitor represents or what they wanted, refine the form. If visitors ask the AI to make a recommendation, improve the routing boundary rather than expanding the AI answer.

For related workflow ideas, read human handoff workflow, shared response queue, and employee presence and availability. Confirm current Kiguri plans at the [pricing page](https://kiguri.com/#pricing).

Frequently asked questions

What should an inquiry form for financial advisors ask?

Start with name, organization or household label, relationship to the firm, purpose of the inquiry, and optional free-text context. Add a field only when it changes routing or the next human step.

Should the form collect account numbers or holdings?

Not for an open reception intake. Keep the first request limited to routing context. A qualified employee can explain the appropriate channel for any later account-specific conversation.

Can Kiguri provide investment advice through the AI receptionist?

No. Kiguri can support approved general reception answers and route a visitor to an employee. It does not provide financial advice, recommendations, performance claims, or suitability decisions.

Can the same form route clients and referral partners?

Yes. Use relationship and purpose choices that your team understands, then define the host or backup for each. Kiguri’s response queue supports acceptance and reassignment while preserving the visitor’s context.

Does the form guarantee a compliant or private workflow?

No. Kiguri features support visitor intake and handoff. Your firm must review its own legal, privacy, security, and regulatory requirements and configure the process accordingly.

Sources and further reading

• [Kiguri virtual reception](https://kiguri.com/) • [Kiguri pricing](https://kiguri.com/#pricing) • [Kiguri customer inquiry routing guide](https://kiguri.com/blog/customer-inquiry-routing-for-saas-support-teams) • [Kiguri human handoff workflow guide](https://kiguri.com/blog/human-handoff-workflow-for-saas-support-teams) • [Kiguri shared response queue for financial advisors](https://kiguri.com/blog/shared-response-queue-for-financial-advisors) • [Kiguri employee presence and availability for financial advisors](https://kiguri.com/blog/employee-presence-and-availability-for-financial-advisors)

Sources and further reading

Kiguri product overview, Kiguri pricing, security information, and Kiguri guides.