Guest-day pricing model for SaaS support teams

What “guest-day” should mean

For planning, define one guest-day as one visitor having an active support or reception interaction during one calendar day. A visitor who returns on a different day creates another guest-day. A visitor who opens a page but does not submit an inquiry does not need to count as a support guest-day unless your team wants to measure anonymous traffic separately.

This definition keeps a casual page view separate from a conversation that needs employee attention. It also lets finance and support operations use the same language. Write the definition down before comparing tools; vendors may use “guest,” “visitor,” “session,” or “external user” differently.

Kiguri's workflow is centered on a customer-facing virtual office. A visitor can share identity, company, and purpose, receive approved answers from an AI receptionist, enter a response queue, and be handed to an available employee. The guest-day model should therefore measure the work around that journey, not simply count map impressions.

The four numbers to collect

1. Member count

Members are the employees who need to operate the workspace, receive inquiries, or join conversations. Start with the smallest accurate number. If a person never needs to see or handle a request, do not include them in a draft seat estimate simply because they work at the company.

2. Active guest-days

Count visitor days that create an inquiry or employee handoff. Track the total and separate it by purpose when possible: product support, onboarding, security, sales, or customer success. Purpose tells you whether the cost is mostly intake, live conversation, or specialist time.

3. Human minutes per guest-day

An AI receptionist can answer approved questions and collect context, but a human employee remains responsible for complex conversations and decisions. Estimate the average employee minutes per guest-day, including reading the context, joining, and closing the interaction. A short chat and a screen-sharing troubleshooting session should not have the same weight.

4. Follow-up rate

Some visitor days end with one answer. Others create a queue item, a second conversation, or a private consultation. Track the percentage that needs follow-up. This number often matters more than raw visitor volume because it determines specialist capacity.

Using Kiguri's published plans as the baseline

The Kiguri pricing section lists a Free plan at $0 for up to 8 members, a Business plan at $12 per user per month, and Custom volume pricing. These are plan prices, not a claim that each external visitor is billed as a paid member or that Kiguri publishes a guest-day surcharge.

For a team with six members, the published Free plan is the first baseline to check. If the team grows to twelve members, a simple Business estimate at $12 per user per month would be 12 × $12 = $144 per month before taxes or any separately stated terms. That arithmetic is an illustration of the published per-user price, not a quote. A team with a larger or negotiated deployment should ask about Custom volume pricing.

The key accounting separation is:

• **Workspace cost:** the plan and member seats needed by the team. • **Guest operations cost:** employee time, specialist coverage, and follow-up created by visitors. • **Conversation cost:** any phone, video, screen-sharing, or private-room workflow that requires additional people or policy.

This structure prevents a team from treating visitor access as unlimited free labor. It also avoids inventing a guest billing rule that the public pricing page does not state.

A worked internal guest-day model

Imagine a support team with eight members and 90 active guest-days per month. Suppose 60% of those days need 12 minutes of employee attention, while 40% need 35 minutes because the request requires a deeper conversation or screen sharing.

The estimated human time is:

• 54 lighter guest-days × 12 minutes = 648 minutes; • 36 deeper guest-days × 35 minutes = 1,260 minutes; • total = 1,908 minutes, or about 31.8 employee hours.

The exercise does not change Kiguri's plan price. It reveals the capacity that the support team must reserve. If an AI receptionist answers an approved question before handoff, the team may reduce avoidable back-and-forth. If many visitors require a specialist or a private room, the operations estimate should increase.

Use the model for scenarios rather than false precision. Run a low case, expected case, and peak case. Change the guest-day count, human minutes, and follow-up rate, then compare the result with the employee capacity available each month.

When a guest-day model is useful

Seasonal support

Launches, renewals, and annual events can create short periods of high visitor volume. A guest-day view shows the staffing need without suggesting that the team must permanently add seats for a temporary spike.

Partner and implementation work

Partners may visit for a small number of focused sessions, while the implementation team still needs a stable workspace. Count the guest-days and specialist minutes separately so the budget reflects the actual engagement.

Evaluating a virtual reception against a chatbot

A chatbot comparison should include the cost of escalations. If a visitor must repeat context after an automated answer, the apparent software saving may be offset by employee time. Kiguri's reception-to-AI-to-human workflow is useful to evaluate as a complete handoff, not just as a chat widget.

Questions to ask before signing up

Ask whether the quoted plan is based on members, visitors, or both. Confirm what “user” means in the current order form. Ask which conversation channels are included for your plan and whether map, campus, or private-room requirements change availability. Verify how an inquiry enters the response queue and what context the employee receives. Finally, ask how Custom volume pricing is calculated for a larger deployment.

Do not treat an internal guest-day spreadsheet as a vendor promise. It is a way to compare the operational cost of different arrival and handoff designs using the facts you can verify.

Frequently asked questions

Does Kiguri publish a guest-day price?

The public pricing information reviewed for this guide lists member-based plans: Free at $0 for up to 8 members, Business at $12 per user per month, and Custom volume pricing. It does not establish a separate guest-day meter. Confirm current billing terms with Kiguri before purchase.

Should every visitor become a paid member?

Not automatically. A member is someone who needs to operate the workspace; a visitor is an external person arriving for a conversation. Confirm the current plan definition and permissions for your workspace rather than assuming the two are billed identically.

How can an AI receptionist affect guest-day costs?

Approved answers and better intake can reduce repeated explanations and unnecessary handoffs. They do not remove the need for a human employee when a request is complex, sensitive, or account-specific.

Where can I verify Kiguri's current plan prices?

Use the Kiguri pricing section and confirm the offer at the time of purchase. Prices, limits, and availability can change.

Sources and further reading

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

Sources and further reading

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