Screen sharing in customer reception for partner offices

Why visual reception helps a shared office

Shared partner offices contain several destinations and relationships. A tenant may not know where to start, a client may not know the steps in a joint workflow, and a channel partner may need to see how visitors reach a named host.

Screen sharing can make the first human conversation concrete. A host can point to a visitor-facing map, walk through a public workflow, or show the next action in a collaboration process. The screen should reduce ambiguity, not overwhelm the visitor with internal tools. Keep the shared view aligned with the visitor's purpose and move to a private consultation room when a narrower conversation is appropriate.

Use other formats when they are simpler. Chat is useful for a short link. Browser phone is useful for a quick explanation. Video can establish face-to-face context before a visual walkthrough. Screen sharing should appear when seeing the same thing will help both people decide what happens next.

Capture the reason for a visual conversation

Begin with a branded Kiguri reception link on a client page, tenant guide, partner invitation, or event page. Explain that visitors can ask a question, request a host, or describe a workflow to review. Do not make them choose "screen sharing" before the office understands what they need.

Use a short intake to collect:

• name and organization; • relationship to the partner office; • reason for visiting; and • a free-text description of the question or desired outcome.

For a client, a project or workstream field may help identify the right host. For a tenant, a destination or orientation topic may be enough. For a channel partner, ask about the proposed audience or introduction only if it changes routing. Keep optional fields limited; the purpose is to give the host a useful starting point, not to reproduce a full account record.

Avoid asking a visitor to upload private documents or provide credentials in the public reception. If the host later needs a more focused discussion, accept the inquiry and move it to an appropriate private room. The visitor should know why a host is asking for a new context before the conversation changes.

Give the AI receptionist a visual-support boundary

Prepare approved answers for stable questions: what the partner office does, which kinds of hosts can help, how a visitor can request a consultation, and where to find current public information. Review these answers when the office map, event program, or tenant guidance changes.

The AI can recognize that a visitor wants an explanation and route the request with its wording intact. It should not claim to have viewed a private project, diagnose an account issue, or promise that a specific workflow will be shown. When a question depends on a relationship, the best answer is a clear handoff with context.

Tell visitors that an available host may offer screen sharing when a visual explanation is useful. If no host is ready, the response queue or another supported format remains available.

Route the request to a host who can explain it

Create a practical routing map:

• **Client workflow:** account owner, project lead, or client-success host. • **Tenant orientation:** community host or office operations owner. • **Partner introduction:** alliance or partner-development owner. • **Prospective client:** business-development host. • **Event or community visit:** event owner or greeter.

These labels are policies for the office. Kiguri's response queue carries the visitor's relationship, purpose, and description so an employee can accept or reassign the inquiry. A host who cannot provide the visual explanation can acknowledge the visitor and select a colleague or follow-up format without asking the visitor to start over.

Use presence and availability carefully. A host may be able to answer in chat while preparing a visual consultation. Another may prefer to schedule a longer review. Show the visitor the option the team can actually deliver, and let the employee choose screen sharing after reading the context.

Prepare a simple screen-sharing agenda

Before sharing, the host should restate the visitor's goal: "We will look at the client handoff path," or "I will show where tenant orientation begins." Agree on the narrow question the screen will answer. One clear visual path is more useful than a tour of every map, desk, and room.

Use the Kiguri map when orientation is the point. A host can show reception, a meeting destination, or a public consultation area. Use a workflow view when a client or partner needs to understand who owns the next step. Keep internal spaces out of a visitor-facing explanation. If the topic becomes relationship-specific, move to a private room.

Narrate what is on screen and pause for questions. Visitors may be unfamiliar with the office's labels, so replace internal shorthand with plain language. Check understanding before changing views. Send a public link in chat when it will help the visitor revisit the explanation, but do not assume a link alone completes the handoff.

End with a named action. The host might assign a project follow-up, connect a tenant with a community owner, schedule a longer partner meeting, or return the visitor to chat. Summarize who is responsible and what the visitor should expect next. Do not promise a recording, transcript, or document unless the office has explicitly configured that process.

Design fallbacks for real visitors

Screen sharing is not always the right format. A visitor may be on a small screen, prefer audio, or arrive when the host is occupied. The reception should preserve the original context when switching to browser phone, video, or chat. If no employee is available, explain how the response queue works and what follow-up path is actually offered.

Test a client who needs a workflow explanation, a tenant who wants map orientation, a partner who asks for a visual introduction, and a visitor who chooses an incorrect category. Confirm that each person understands why a host selected a format and can continue without repeating their reason for arrival.

Measure whether the visual handoff worked

Pilot five paths: client workflow review, tenant orientation, partner introduction, prospective-client question, and general visitor request. Review intake completion, handoffs, format changes, and visits that reach a named owner. Ask whether the screen view answered the question and the next step was clear.

Look for unnecessary complexity. If visitors need a long tour to understand one destination, simplify the map or arrival message. If hosts repeatedly ask the same missing question, add one concise intake prompt. The value of screen sharing is a clearer conversation, not a larger presentation.

The [Kiguri virtual reception](/) explains the overall visitor flow. Related guides cover customer inquiry routing for partner offices, human handoff workflow for partner offices, and browser video consultations for partner offices.

Frequently asked questions

What does screen sharing add to partner-office reception?

It lets an employee show a map, public workflow, or next-step explanation after accepting a visitor inquiry. The visual session is connected to the original context instead of beginning as an unrelated meeting.

Should every partner-office visitor be offered screen sharing?

No. Use it when seeing the same map or workflow reduces ambiguity. Chat, browser phone, or video may be simpler for other questions.

Can a tenant and a client follow different visual paths?

Yes. Ask for relationship and purpose during intake, then route the inquiry to the appropriate host. The host chooses what to show and can switch formats when the request changes.

Does screen sharing expose every office area?

The host should show only the destination or workflow needed for the visitor's question. Use visitor-facing maps and private consultation rooms according to the office's own access choices; do not promise a particular visibility policy in the article.

Is screen sharing available on every Kiguri plan?

Public Kiguri materials describe screen sharing as one of the customer-facing conversation formats. Public pricing lists a Free plan for up to 8 members, a Business plan at $12 per user per month, and Custom volume pricing. Confirm current feature availability and limits before publishing a plan claim.

Sources and further reading

• [Kiguri customer-facing virtual reception](https://kiguri.com/) • [Kiguri pricing and plan information](https://kiguri.com/#pricing) • [Customer inquiry routing for partner offices](https://kiguri.com/blog/customer-inquiry-routing-for-partner-offices) • [Human handoff workflow for partner offices](https://kiguri.com/blog/human-handoff-workflow-for-partner-offices) • [Browser video consultations for partner offices](https://kiguri.com/blog/browser-video-consultations-for-partner-offices)

Sources and further reading

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