Multi-building virtual campus for SaaS support teams

What a multi-building virtual campus means

A multi-building virtual campus is a set of connected virtual destinations with a shared reception. Each building represents a meaningful customer journey rather than an internal department name. For example, a company might create a Product Support building, an Implementation building, a Trust and Security building, and a Customer Success building. The visitor still begins at one customer-facing front door.

The map is an information architecture. It answers three questions quickly:

• Where should this visitor start? • What kind of help happens in this area? • What happens if the right employee is not available?

Kiguri's public workflow supports the important transition between orientation and conversation. The visitor can describe the purpose of the visit, and the AI receptionist can answer approved questions or collect missing context. When an employee takes over, the interaction can continue in the channel appropriate for the request, including chat, browser phone, video, screen sharing, or a private room where that option is configured.

When multiple buildings improve support

Different requests need different preparation

An integration problem and a security questionnaire are both support requests, but they require different context. A Product Support destination can ask for the affected feature and error description. A Trust and Security destination can explain the approved way to discuss security questions before a human joins. Clear destinations reduce the chance that a customer gives a sensitive or highly technical request to the first person who happens to answer.

Customers have more than one relationship with a SaaS company

An existing customer may need troubleshooting, an implementation team may need a launch conversation, and a prospective buyer may want a product explanation. A campus can reflect those journeys without exposing internal employee rooms. Use customer language such as “Get product help,” “Plan an implementation,” or “Talk with our team,” rather than labels that only make sense to employees.

Distributed teams need a shared arrival pattern

Remote employees can work in different time zones and still share one reception. A visitor does not need to know which person is online or which region owns the issue. Identity, company, and purpose intake gives the response queue enough information to locate the right available employee. The campus provides orientation; the queue provides operational routing.

A practical multi-building layout

Start with three to five destinations. More buildings are appropriate only when they represent a real difference in the visitor's next step.

Building 1: Customer reception

This is the public entry, not a directory. Explain that the visitor can share their name, company, and purpose, ask an approved question, and be connected to an available employee. Link to the [Kiguri customer reception](/) for the product-level example.

Building 2: Product support

Use this destination for product behavior, troubleshooting context, and requests that may benefit from screen sharing. The AI receptionist should answer only questions the team has approved. It should not invent a fix or request secrets that the support process does not need.

Building 3: Implementation and onboarding

This area can set expectations for launch planning, configuration questions, and a conversation with an implementation employee. Ask for the customer goal and timing rather than a long technical questionnaire. The employee can decide whether chat, video, or a private room is the best next step.

Building 4: Trust and security

Keep the visitor-facing explanation high level and route detailed requests to the appropriate human. Do not place confidential documents or internal notes in the public map. Link to the Kiguri security information only when it matches the questions your team is prepared to answer.

Building 5: Customer success

This destination can support account reviews, adoption conversations, and escalation follow-up. It is a useful place for a visitor who knows the business outcome they want but not the internal team responsible for it.

How a visitor moves through the campus

The experience should feel like one conversation, not five unrelated forms.

1. The visitor opens the shared reception and recognizes the company. 2. The reception asks for identity, company context, and purpose. 3. The AI receptionist answers approved questions and clarifies missing details. 4. The inquiry enters the response queue with the context attached. 5. An available employee accepts the handoff and chooses the right channel. 6. If a private conversation is needed, the employee moves the visitor to an appropriate private room.

This sequence keeps the campus visible while keeping employee spaces controlled. It also prevents the map from making a promise the team cannot keep. If no employee is available, the reception should state what the response queue does next instead of suggesting an immediate call.

Rules for keeping a campus understandable

Name destinations by customer outcome. Keep the first screen short. Make the public reception visually distinct from private rooms. Review every AI answer as an approved piece of guidance. Test a visitor journey from an unfamiliar browser and check that the employee receives the submitted context.

Measure whether visitors reach the right handoff without being redirected. If people routinely choose the wrong building, simplify the choices rather than adding another building. A campus earns its place when it reduces explanation and preserves context.

Frequently asked questions

Does Kiguri require a multi-building layout?

No. A single reception or a smaller map may be the better design. Use multiple areas when they make a meaningful difference to visitor orientation and handoff.

Can visitors see every employee room?

The public reception should be treated as a controlled arrival point. Configure visitor destinations and private rooms according to your access rules, and verify the current behavior in your workspace before launch.

Can the AI receptionist answer questions in every building?

It can support approved answers in the configured workflow. Keep answers specific, reviewed, and appropriate for a public visitor. Human employees remain responsible for complex or sensitive conversations.

How much does a Kiguri campus cost?

Kiguri public pricing lists a Free plan at $0 for up to 8 members, a Business plan at $12 per user per month, and Custom volume pricing. Confirm current limits and whether the workspace design you need is available on your selected plan at the time of purchase; see the Kiguri pricing section.

Sources and further reading

• [Kiguri customer-facing virtual office](/) • Kiguri security information • Kiguri pricing • Kiguri Guides

Sources and further reading

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