Inquiry intake forms for legal practices
Design a focused Kiguri inquiry intake form for legal practices that captures visitor context and routes prospects, clients, and referral partners responsibly.
Start with the host’s first useful question
Ask intake staff what they need to know before acknowledging a request. Usually it is the visitor’s name, organization, relationship to the practice, purpose of the visit, and a short description. Those facts distinguish a new introduction from an existing client service request without requiring a full matter history.
Use visitor language. “How are you connected to our practice?” is clearer than “engagement classification.” “What would you like help with today?” is more welcoming than “matter type.” Offer “I am not sure” when a visitor cannot identify a practice group or does not know whether the request belongs to intake or client service.
The first form should prepare a human response, not attempt to provide legal triage or a complete consultation. Remove fields that do not change routing or the immediate next step.
A practical core field set
Most legal practices can begin with five fields:
• **Name:** so the first response can address the visitor naturally. • **Organization:** enough context to recognize a firm, business, or referral relationship. • **Relationship:** prospective client, existing client, referral partner, event guest, vendor, or another visitor. • **Purpose:** request an intake conversation, reach a matter team, ask a general practice question, or find an event host. • **Additional context:** optional free text in the visitor’s own words.
Ask for a contact detail only when the firm’s follow-up process actually uses it. Explain why it is requested and what happens next. If a visitor can continue in the Kiguri conversation, do not add a second contact field merely because it is common on lead forms.
Do not ask for a complete chronology, legal documents, passwords, detailed confidential facts, or sensitive information in an open reception flow. The form helps route the request; a qualified person can explain what information is appropriate for any later conversation.
Route by relationship and purpose
Create a routing policy that intake staff can follow:
• **Prospective client:** designated intake host or practice lead. • **Existing client:** matter team or client-service contact. • **Referral partner:** professional-relations owner. • **Event guest:** event or reception host. • **Vendor or operations request:** operations owner. • **Uncertain request:** general intake host who can clarify and reassign.
These are your firm’s policies, not automatic Kiguri classifications. Kiguri can display the visitor’s answers in the response queue, where an employee accepts or reassigns the inquiry while keeping the original context. The customer inquiry routing guide describes how to preserve context during handoff.
Use neutral route labels. “Request an intake conversation” is more accurate than “get your case evaluated.” Let a qualified person explain conflicts, scope, fees, deadlines, and next steps through the firm’s approved process.
Ask one useful purpose question
“How can we help?” is friendly but often produces vague messages. Pair it with a few concrete options and an optional explanation: request an introduction, reach an existing matter team, ask a general practice question, discuss a referral, or find an event. Keep “something else” available.
If a visitor chooses an existing client request, ask only the detail that changes routing, such as a matter-team name or broad service need. Do not turn the initial form into a full discovery interview. The host can ask any follow-up questions after accepting the handoff.
Give the AI a narrow boundary
The AI receptionist can answer stable, approved questions about the practice’s public introduction, reception process, visitor destinations, and how to request a host. Assign an owner to review answers when practice descriptions, office hours, event details, or intake contacts change.
Route requests that require legal judgment or matter-specific context to a person. The AI should not interpret a statute, recommend a legal strategy, assess a claim, predict an outcome, determine whether a conflict exists, or imply that a visitor has received legal advice. It should not ask for detailed privileged or confidential facts just to complete routing.
A clear boundary might say, “I can help route your inquiry, but a member of the practice must discuss legal questions and next steps with you.” Have the firm approve the exact wording and escalation process. An honest limit is more useful than a polished answer that creates a wrong expectation.
Connect the form to the response queue
An intake form needs a visible 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 conversation. Decide who watches the queue during published hours and what happens when the practice is offline.
Use consistent labels. If the form says “existing client,” the queue should not hide that context behind a generic “new inquiry” label. Include the free-text description so the first response can acknowledge the visitor’s actual request.
When a host is available, Kiguri supports chat, browser phone, video, screen sharing, and private consultation rooms. Offer the format the host can accept and explain the transition. A private room is a workflow option after a host accepts; it does not itself establish privilege, confidentiality, or compliance.
Write an honest offline path
Legal inquiries may arrive outside office hours or when the relevant practice group is in court, a meeting, or another matter. 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 helps follow-up. Do not promise a deadline review or immediate attorney response unless the firm has an approved process that can provide it.
Test the offline state with a prospective client and an existing client. Can each person tell what happens next? Can the assigned host understand the request without asking the visitor to submit sensitive information again? If not, improve the copy or the routing rule before adding more fields.
Pilot with real practice scenarios
Run five walkthroughs: a prospective client requesting an intake conversation, an existing client looking for a matter contact, a referral partner, an event guest, and a visitor who asks a matter-specific legal question. Ask testers to complete the form without coaching.
Read each handoff as if you had never seen the original visitor link. Can you tell who the visitor is, what relationship they have, why they came, and what should happen next? If not, refine the questions. If the AI tries to answer a legal question, strengthen the human boundary rather than expanding the AI content.
Review accepted, reassigned, and offline inquiries after launch. Ask intake staff whether the form reduced repeated opening questions and whether visitors understood the next step. The goal is a clear, responsible human handoff, not an automation-rate claim.
For related patterns, read virtual front desk for legal practices, branded visitor links, and human handoff workflow. Confirm current plan details at the [Kiguri pricing page](https://kiguri.com/#pricing).
Frequently asked questions
What should a legal-practice inquiry form ask first?
Start with name, organization, relationship to the practice, purpose, and optional context. Add a field only when it changes routing or the next human step.
Should the form collect confidential matter details?
Keep the initial intake limited to routing context. Do not request detailed confidential facts or documents merely to start a conversation; let a qualified person explain the appropriate channel.
Can the AI provide legal advice?
No. It can answer approved general reception questions and route matter-specific requests to a person. It should not interpret law, recommend a strategy, predict an outcome, or imply legal advice.
Does submitting the form create an attorney-client relationship?
No. Submission does not itself create a relationship, establish privilege, complete a conflict check, or guarantee that an attorney will respond. Use the firm’s approved intake process.
Does the form guarantee confidentiality or compliance?
No. Kiguri supports visitor intake and handoff features. Your practice must review its own legal, privacy, security, professional-responsibility, and regulatory requirements.
Sources and further reading
• [Kiguri virtual reception](https://kiguri.com/) • [Kiguri pricing](https://kiguri.com/#pricing) • [Kiguri virtual front desk for legal practices](https://kiguri.com/blog/virtual-front-desk-for-legal-practices) • [Kiguri branded visitor links for legal practices](https://kiguri.com/blog/branded-visitor-links-for-legal-practices) • [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)
Sources and further reading
Kiguri product overview, Kiguri pricing, security information, and Kiguri guides.