Guest-day pricing model for digital agencies

Define a guest-day for agency planning

For this article, one guest-day means one external visitor or visitor group creating a meaningful reception interaction on one calendar day. The interaction could be an inquiry to the AI receptionist, an item in the response queue, a live employee handoff, or a follow-up conversation. A person who only views a public page does not need to count unless the agency separately wants an awareness metric.

Write the definition down with finance and client service. A client returning on a second day creates another guest-day. Decide whether a buying group counts as one group-day or several visitor-days. Either choice can work if the agency uses it consistently. The goal is to estimate work and capacity, not to imply that Kiguri charges an unpublished fee per visitor.

Segment guest-days by purpose because effort varies:

• New-business discovery or capabilities questions • Active-client delivery and status requests • Creative or strategy reviews • Partner and production coordination • Event or campaign follow-up

The same count can represent very different work. Ten short capability questions are not equivalent to ten multi-stakeholder creative reviews.

Keep three budget lines separate

1. Member seats

Members are the agency employees who operate the reception, receive inquiries, or join conversations. Count people who need access to the workspace and its workflow. An account lead who owns the queue may need regular access; a freelance specialist who joins one approved conversation may have a different requirement. Confirm current workspace roles and plan terms instead of assuming every collaborator needs the same seat.

2. Guest-day volume

Guest-days show how much external demand the reception handles. Track the count by visitor purpose, source link, and outcome. A conference link, a client portal link, and a website reception may produce different quality and follow-up patterns.

3. Human effort

The AI receptionist can answer approved questions and collect context, but agency employees still make scope decisions, give creative judgment, and conduct client conversations. Estimate the minutes spent reading context, joining, responding, changing channels, and recording the next action. Keep a short text answer separate from a browser phone call, video review, screen-sharing session, or private consultation.

Use a simple planning equation

An agency can start with this internal formula:

**Monthly service effort = guest-days by purpose x average human minutes per guest-day**

Add a handoff factor for the share of guest-days that reach a person, then add a follow-up factor for reviews or specialist conversations. For example, an agency might forecast 80 new-business guest-days at 12 human minutes each, 45 client guest-days at 20 minutes, and 15 partner guest-days at 25 minutes. The result is an effort estimate, not a promise about response time or a Kiguri invoice.

Use ranges rather than false precision. A new-business question might take 5-20 minutes; a client delivery request might take 15-45; a creative review can vary widely. Recalculate after two or four weeks of real queue data.

Map the model to the Kiguri workflow

Kiguri's customer-facing flow gives the agency useful measurement points. A visitor opens one branded link, shares identity, company, and purpose, and receives approved answers from the AI receptionist. If a person is needed, the inquiry can enter a response queue or move to an available employee. The conversation can continue through chat, browser phone, video, screen sharing, or a private consultation room when configured.

Record where the guest-day ends:

• **Self-served:** the approved answer resolved the question. • **Queued:** the team needs to follow up later. • **Handed off:** an employee accepted the conversation. • **Deepened:** the visitor entered a longer meeting or private room. • **Redirected:** the request moved to another owner or building.

This outcome breakdown prevents the agency from judging the reception only by traffic. A lower handoff rate can be healthy if approved answers resolve common questions. A high private-room rate can signal valuable work, or it can reveal that the public intake is too vague.

Compare a plan without inventing visitor fees

The public Kiguri plans currently describe Free at $0 for up to 8 members, Business at $12 per user per month, and Custom volume pricing. Public materials associate Business with AI reception, response queue and employee handoff, browser phone, longer meetings, and private consultation rooms. Confirm the current limits, included channels, and availability before making a purchase decision.

Put those facts in the **workspace line** of the model. Put guest-days and human minutes in separate **service lines**. A sample worksheet might contain:

| Planning line | What to enter | What it does not prove | | --- | --- | --- | | Member seats | Employees who need workspace access | That guests become members | | Guest-days | Meaningful external interactions per day | A Kiguri per-visitor charge | | Handoff minutes | Employee time per accepted inquiry | A guaranteed response SLA | | Deep-session minutes | Longer calls, reviews, or private rooms | Unlimited meeting capacity | | Plan baseline | Current public member pricing | Future pricing or unlisted limits |

The table is a budgeting aid. It should not be copied into a contract as a billing interpretation.

Account for agency seasonality

Guest volume often follows pitches, launches, events, and reporting cycles. Model a normal month, a pitch-heavy month, and a launch month. Include the people who are available to respond, not only the number of visitors. A reception that handles 200 light inquiries can be less demanding than one that receives 40 urgent production requests.

Use the response queue for peaks rather than promising a permanent live specialist. Create a backup owner for client support and a clear offline message. Presence and status can help route a live inquiry, but they are signals—not a guarantee that the person is the correct account owner or free for a long review.

Review the model after launch

Compare forecast and actual data every month. Look at guest-days by purpose, first-response time, queue age, handoff rate, repeated explanations, private-room invitations, and effort per outcome. If a destination consistently receives the wrong requests, rewrite the reception copy or merge the destination. If one owner receives all the work, add a backup or change the intake question.

Keep the model understandable to the agency team. The best result is not a complex spreadsheet; it is a shared understanding of how member capacity, visitor demand, and client-service effort interact. Update the public pricing link when Kiguri changes plan details and mark all calculations as planning assumptions.

FAQ

Does Kiguri bill digital agencies by guest-day?

This article does not make that claim. The public pricing model reviewed for this guide is member-based, with Free, Business, and Custom plans. Treat guest-days as an internal capacity and effort metric, and confirm billing terms directly before purchase.

Should every agency visitor count as a guest-day?

Only if the agency's definition says so. Count meaningful interactions consistently and keep anonymous page views as a separate traffic metric if useful.

How many member seats should an agency plan for?

Start with employees who operate the reception, own the response queue, or regularly join visitor conversations. Confirm roles, limits, and current plan details with Kiguri rather than inferring them from visitor volume.

Does AI reception remove the need for client-service staff?

No. It can answer approved questions and collect context. Employees remain responsible for creative judgment, scope, sensitive information, and the human handoff.

How should an agency model a pitch spike?

Create a separate peak-month scenario with higher guest-days and shorter or longer effort ranges by purpose. Use queue and availability assumptions instead of promising every visitor an immediate call.

Sources and further reading

• Kiguri pricing • [Kiguri customer-facing virtual office](/) • Kiguri map preview • Shared response queue for digital agencies • Employee presence and availability for digital agencies • Virtual office pricing in 2026 • Kiguri guides

Sources and further reading

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