Custom virtual reception rollout for legal practices

Start with one reception journey

Do not begin by recreating practice groups, partners, and rooms. Select one high-value journey for the pilot: a new-client discovery request, an existing-client support question, a partner referral, or an event follow-up. Describe the first two minutes:

1. Where does the visitor find the branded link? 2. What does the visitor understand the reception can help with? 3. Which identity, company, and purpose details are needed for a useful handoff? 4. Who owns the request when someone is available?

Write an arrival message accurate for the firm's coverage. It can explain that an AI receptionist answers approved general questions, collects context, and helps connect visitors with an available team member. It should not promise immediate advice, acceptance of an engagement, or a response time the firm has not staffed.

Create a reception brief before configuring the map

Make a short brief that partners, operations, and client-facing staff can review. Include:

• audiences the pilot accepts, such as prospects, clients, referrers, or media; • purposes the visitor can choose or describe; • the minimum context needed to identify an owner; • approved general answers and the person responsible for reviewing them; • a primary and backup owner for each purpose; • conversation modes the team can actually cover; • destinations that require an employee decision; • the honest offline and follow-up path.

Keep intake focused. Name, organization, role when useful, purpose, and a short description are often enough for the first routing decision. A firm may ask for a matter or project reference when it changes ownership, but should not request passwords, secrets, confidential client files, or sensitive personal information in an open reception. Explain why each field is requested.

Design the map as orientation, not decoration

Kiguri's spatial model can represent reception, desks, meeting rooms, and social spaces. For a legal pilot, use labels visitors understand, such as "New client conversation," "Existing client support," "Partner referral," or "Private consultation." Avoid exposing an internal organizational chart or every partner's private room.

Offer a direct way to state a question even when the visitor does not want to explore a map. Keep destinations legible, expose only approved public areas, and keep private rooms controlled until a staff member accepts the handoff.

Preview the journey as an external visitor. Check the first message, labels, mobile layout, and the transition after a staff member joins. The visitor access boundaries guide explains how a welcoming public arrival can remain separate from private employee space.

Prepare bounded AI answers

Build the initial answer set from stable, public information: what the firm does, which purposes the reception accepts, what information is safe to provide, how a human handoff works, and where current plan or contact details live. Assign an owner and review date to every answer that can change.

The AI receptionist can clarify a vague purpose, answer approved general questions, and collect a missing detail. It should not provide legal, tax, medical, financial, or other professional advice; determine conflicts; approve an engagement; promise confidentiality beyond the firm's actual policy; or invent a fee, deadline, credential, or result. If a question depends on a client's matter, contract, jurisdiction, or account, the AI should say that a qualified person must review it and preserve the visitor's context for handoff.

Test incomplete questions, unapproved discounts, private documents, professional opinions, or another person's room. A useful boundary response explains the reception's limits and gives a human path.

Define presence and ownership before promotion

Assign purpose-based owners: new-business requests to a business-development or partner owner, existing-client matters to the account team, technical questions to the relevant practice, and partner referrals to a named relationship owner. These are firm policies, not automatic Kiguri classifications.

Agree on primary and backup coverage. An employee may be available for chat but not a browser phone call, or available for a scheduled video conversation rather than an immediate call. Name presence states in a way the team can apply consistently. Presence helps indicate whether a live handoff is plausible; it does not create a service-level guarantee.

The response queue should preserve the visitor's name, organization, purpose, and summary. An owner can acknowledge what was already said instead of restarting discovery. If an inquiry is reassigned, record the reason in the firm's normal process and explain the next step to the visitor.

Roll out in three stages

Stage one: internal rehearsal

Invite a partner, administrator, associate, and someone outside the project to act as visitors. Test a general question, new-client request, existing-client issue, referral, and after-hours arrival. Confirm AI wording, queue ownership, destinations, and context at handoff.

Include uncomfortable cases: no organization, confidential advice, a private employee request, or a pasted secret. Verify a safe explanation and no exposure of another visitor or private room. Test signed out and on a small screen.

Stage two: narrow client or referral pilot

Share the link with one client group, event list, or referral channel. Keep the map and intake stable while the team learns. Review missing context, reassignment reasons, repeated questions, unanswered AI prompts, and whether visitors understood what information was appropriate to submit.

Judge the pilot by the quality of handoffs, not by clicks alone. Have the receiving employees read a sample of conversations and identify fields or wording that would improve the next response.

Stage three: controlled expansion

Add a practice area or destination only when a named owner and backup can cover it. Introduce browser phone, video, screen sharing, or a private room when the firm has a purpose and staff for that mode. Keep a change log for reception copy, map labels, AI answers, and pricing references.

Rollout checklist

Before broad promotion, confirm that:

1. The branded visitor link and firm identity are recognizable. 2. The pilot has one clear journey, owner, and backup. 3. Intake requests only context needed for routing. 4. Approved AI answers have a reviewer and review date. 5. Professional advice and engagement decisions remain with qualified staff. 6. Presence states match real coverage. 7. The queue preserves the visitor's original explanation. 8. Private rooms and employee destinations are not public accidentally. 9. Richer channels are offered only when staffed. 10. The offline path tells visitors what happens next.

Rollout guardrails for a legal practice

Start with operational requests the team can describe accurately. Approve reception copy, intake questions, handoff language, and access boundaries before promotion. Do not claim that Kiguri gives legal advice, guarantees outcomes, creates privilege, or satisfies confidentiality, security, or regulatory duties. Review retention and access settings with the practice's own responsible owner.

Frequently asked questions

Does a custom reception replace a receptionist or partner?

No. Kiguri supports arrival, approved answers, intake, and a route to an available employee. Staff remain responsible for professional judgment, engagement decisions, advice, and client commitments.

How much customization should the pilot include?

Start with a journey, focused map and intake, reviewed answers, and named coverage. Add practice groups or rooms after the first workflow is understood by visitors and employees.

Can the AI determine whether a firm has a conflict?

Do not assume that. Conflict checks and acceptance decisions should follow the firm's verified process and qualified review. The reception can collect context for that process.

What plan should a larger firm evaluate?

Public materials describe Free at $0 for up to 8 members, Business at $12 per user per month with AI reception, response queue and handoff, and Custom volume pricing. Confirm current limits before selecting a plan.

What happens outside coverage hours?

Show an honest offline state, collect the minimum useful context, and explain the actual follow-up path. Remove live-call wording when nobody can accept a live conversation.

Sources and further reading

• [Kiguri home page](/) • Kiguri workflow • Kiguri pricing • Kiguri guides

Sources and further reading

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