Private consultation rooms for design studios

Why a private room should follow reception

Sending every visitor directly to a private room can make access unclear and can put a specialist into a conversation without context. Keeping every conversation in a public chat can expose information that belongs in a controlled discussion. Reception plus human handoff provides a middle path.

The visitor starts with approved general information and limited context collection. The response queue and employee roles make ownership visible. Once the employee understands the purpose, they can invite the visitor to an appropriate room or keep the conversation in chat.

This is a destination decision, not an automatic promise that a project is accepted or a recommendation will be delivered.

A practical private-room workflow in Kiguri

Plan the journey in five steps:

1. **Public arrival:** the visitor opens a branded reception link. 2. **Limited intake:** the AI receptionist collects name, organization, relationship, and purpose. 3. **Human handoff:** an available employee accepts the request with context attached. 4. **Room decision:** the employee decides whether private space is appropriate. 5. **Next action:** the employee explains the channel, owner, and follow-up after the room.

Kiguri supports reception-only entry, approved visitor destinations, visitor access rules, and private consultation rooms. Review the [Kiguri customer reception](/) and Kiguri map preview while planning the public-to-private path.

Collect only the context needed to choose a room

Ask for a name, organization or relationship, and purpose. Visitor choices might include explore a project, get help with an existing project engagement, discuss a partnership, or contact operations. Allow a short explanation without asking for confidential client files, passwords, secret keys, or sensitive personal information in the public intake.

The AI can answer approved general questions and explain that a human may offer a private conversation. It should not invent project engagement scope, promise an outcome, or imply that an designer has reviewed a visitor's circumstances. When the visitor begins sharing sensitive details, use the design studio's approved secure process rather than collecting them in reception.

Explain why a visitor is moving rooms

A private-room transition should not feel like a disappearance. Tell the visitor which employee accepted the inquiry, why a private room is suitable, and what information has already been passed forward. Explain whether the next step is an introductory conversation, an existing-client discussion, or a project scoping conversation.

Give the visitor a clear opening script. The employee can state their role, the purpose of the room, and what the visitor should avoid sharing until the design studio's approved process is in place. At the end, state who owns the next action and whether another specialist will follow up. This prevents the room from sounding like a promise that the project has been accepted.

Let the visitor choose a simpler channel when appropriate. Chat may handle a general question. Browser phone or video can support a live introduction. Screen sharing may help a non-sensitive workflow explanation. A private room is one option, not a default for every visitor.

Use labels that visitors understand. "Client consultation" communicates purpose better than an internal project-engagement code. Keep confidential client names and unreleased drawings out of public signage and map decoration.

Assign room ownership and availability

Every private room needs an owner and backup. A practice lead may own a prospective project conversation. An project engagement owner may handle an existing client. A partner lead may own collaboration. The visitor should not be invited into a room that nobody monitors.

Kiguri includes employee roles, member presence or status, and a shared response queue. Use those signals to determine whether a room can open now or whether the inquiry should wait. Presence is not a promise of design advice, project acceptance, or delivery capacity.

When the employee becomes unavailable, keep the visitor's context in the queue and explain the follow-up. If a specialist joins, explain the role and preserve the visitor's opening words.

Review access and retention with the team

Decide who can see visitor context, which roles can invite a visitor, and what happens when a private conversation ends. Review retention and access settings with the design studio's responsible owner. Do not describe a Kiguri room as proof of security, confidentiality, regulatory compliance, or design quality; those responsibilities depend on the design studio's own policies and systems.

Test a prospect, existing client, referral partner, and after-hours visitor. Check whether the visitor understands the boundary, whether the employee receives enough context, and whether the chosen room fits the purpose. Remove a room that creates confusion instead of adding value.

Use queue states that match work, such as new, claimed, waiting for visitor, waiting for specialist, and complete. A claimed inquiry should have an owner and next action. If a visitor changes purpose, route them back through clear reception language instead of opening another private room without explanation.

Confirm current Kiguri pricing, visitor rules, and workspace limits before publishing a private-room capability or plan promise.

Review the room message whenever the design studio changes service hours, specialists, or approved communication channels. Keep the visitor-facing wording aligned with the team's actual operating policy.

Train every host on the same transition language so visitors receive consistent expectations across locations and time zones, and review it regularly.

Consistent room language helps the design studio avoid accidental promises about scope or outcomes.

FAQ

Should every design studio visitor enter a private room?

No. Start with reception and intake. An employee should choose a private destination when the purpose and access requirements make it appropriate.

Does a private room guarantee confidentiality or security?

No. The design studio remains responsible for its policies, systems, records, and legal or regulatory requirements.

Can the AI receptionist enter the private room instead of an designer?

The AI supports approved intake and orientation. A human employee decides when and how a private conversation continues.

What if the designer is unavailable?

Keep the inquiry in a response queue and give an honest follow-up message. Do not imply that a private room means an immediate expert conversation.

Give private conversations an intentional beginning

Private consultation rooms are most useful when they follow clear arrival, limited context collection, human ownership, and an explicit room decision. Kiguri supplies that operating workflow while design professionals remain responsible for the work, information boundaries, and client relationship.

[Explore Kiguri](/) and design private destinations that help your design studio have focused conversations without exposing unrelated work.

Sources and further reading

• [Kiguri customer reception](/) • Kiguri map preview • Kiguri pricing and plan overview • Kiguri guides

Sources and further reading

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