Customer inquiry routing for legal practices
Learn how Kiguri helps legal practices route prospective-client, existing-client, and partner inquiries with careful intake, human ownership, and controlled conversations.
Why a general inbox is not enough
A shared inbox can show that a message arrived, but it may not show whether the visitor is a prospective client, an existing client, a referral source, or a general contact. It may also encourage visitors to include facts that should be collected only through an approved confidential process.
A routing workflow starts with a clear reception and a small purpose question. “Request an introductory conversation,” “Contact an existing matter team,” “Reach the practice as a referral partner,” and “Ask a general office question” are easier for visitors than internal practice-group names. The response queue then gives the practice a place to assign ownership without making the visitor choose an attorney blindly.
Kiguri is an operating workflow, not a legal-intake or conflicts system. The practice must decide what information it may collect, who reviews it, and what process follows.
A four-stage Kiguri routing model
Plan customer inquiry routing in four stages:
1. **Public arrival:** the visitor opens a branded reception link and sees what the practice can help with. 2. **Limited intake:** the AI receptionist collects a name, organization context when appropriate, and purpose without requesting secrets or case details. 3. **Human ownership:** the inquiry enters a response queue and an available role can accept or reassign it. 4. **Approved continuation:** the conversation stays in chat or moves to browser phone, video, screen sharing, or a private consultation according to practice policy.
The visitor's explanation remains attached to the handoff so they do not have to repeat it when another coordinator or lawyer joins. Start with the [Kiguri customer reception](/) and review the Kiguri guides.
Collect routing context without inviting legal advice requests
Ask only what helps determine the next step. A name, organization, relationship to the practice, and general purpose may be enough to route a visitor to an intake coordinator or existing matter team. Do not ask for a detailed statement of facts, privileged communications, confidential documents, or information about adverse parties in an open reception.
The AI may explain that the reception is a starting point and that submitting an inquiry does not create an attorney-client relationship or guarantee a response. The practice should review and approve this language. The AI must not analyze a visitor's legal problem, suggest a legal strategy, predict an outcome, or imply that a lawyer has reviewed the matter.
If a visitor begins sharing sensitive facts, interrupt with the practice's approved instruction for secure communication and route to a human. The public intake should not be treated as a conflicts check or a substitute for the practice's established process.
Route by purpose, role, and availability
Define ownership around visitor needs rather than exposing every practice group. A prospective-client introduction may go to a designated intake coordinator. An existing client may need a client-service host or matter team. A referral partner may need a relationship contact. A general office question can use a shared queue.
Kiguri includes employee roles, member presence or status, and a shared response queue. Use those signals to decide whether someone can accept a live handoff. An online status does not mean a lawyer is available to advise, and routing does not replace conflicts, engagement, or authorization checks.
When nobody is available, acknowledge the inquiry and explain the follow-up process. Avoid promising an immediate response, legal review, or representation. Preserve the visitor's non-sensitive context so the next owner can decide what additional information may be requested through an approved channel.
Choose a controlled destination
Chat may be enough for a general office direction. Browser phone or video can support an introductory conversation when practice policy permits. A private consultation room can hold a conversation after the practice has handled identity, authorization, and confidential communication requirements through its own process.
Kiguri supports reception-only entry, approved visitor destinations, visitor access rules, and private consultation rooms. Use the Kiguri map preview to separate the public reception from internal practice areas. Do not describe a private room as proof of privilege, confidentiality, security, or regulatory compliance. Those claims require practice-specific review.
Review routing with intake staff
Test the flow with a prospective client, current client, referral partner, and general visitor. Check whether the reception asks only approved questions, whether the queue shows enough context, and whether the visitor understands that an inquiry may be queued. Ask intake staff whether the next owner can tell what the visitor needs without inviting unnecessary facts.
Review real threads after launch. If visitors repeatedly choose a confusing purpose, rewrite it. If staff need a missing non-sensitive detail, add one focused prompt. If a conversation should remain in a secure practice system, make the handoff message clearer. Do not claim better matter outcomes, response times, confidentiality, security, or compliance without practice-approved evidence.
Keep an explicit boundary in the visitor message: an inquiry is received for routing, not automatically accepted as a matter. Let the practice decide when to request additional facts, run its own checks, and authorize a confidential conversation. That distinction helps visitors and intake staff understand what the queue can and cannot do.
Confirm current Kiguri pricing, visitor access, and workspace limits before publishing a plan or capability commitment.
FAQ
Is Kiguri a legal intake or conflicts-checking system?
No. Kiguri provides reception, bounded intake, employee routing, and controlled destinations. The practice remains responsible for legal intake, conflicts, engagement, confidentiality, and records.
Can the AI answer a visitor's legal question?
Use only approved general information about the practice and reception. Route legal questions and matter-specific facts to an authorized human through the practice's process.
Can prospective and existing clients use one reception?
Yes. Use visitor-friendly purposes and relationship context to route each inquiry while keeping one recognizable public arrival.
What happens when no lawyer or coordinator is available?
The inquiry can enter a response queue with an honest follow-up message. Do not promise representation or immediate legal review.
Route carefully from the first message
Legal practices need a front door that is accessible without encouraging visitors to disclose more than the practice can safely handle there. Kiguri combines branded arrival, limited AI-assisted intake, role-aware routing, presence, and controlled follow-up while leaving legal responsibility with the practice.
[Explore Kiguri](/) and design a routing workflow that helps your intake team own the next step without turning a public reception into legal advice.
Sources and further reading
• [Kiguri customer reception](/) • Kiguri pricing and plan overview • Kiguri map preview • Kiguri guides
Sources and further reading
Kiguri product overview, Kiguri pricing, security information, and Kiguri guides.