Guest-day pricing model for marketing agencies

What this planning model means

Treat a guest-day as a way to estimate visitor activity over a day, not as a promise that every visitor interaction has the same billing treatment. Separate three populations:

1. **Members:** employees who need roles, presence, queue ownership, or private workspace access. 2. **Guests:** prospects, clients, partners, vendors, and event visitors arriving through a reception link. 3. **Occasional participants:** people who join a specific consultation without needing permanent internal access.

This distinction helps an marketing agency avoid buying a permanent seat for every prospective participant. It also prevents underestimating the members needed to provide a responsible human handoff. Guest planning describes visitor activity; it does not replace engagement ownership or campaign judgment.

Public Kiguri plan signals

Kiguri public materials reviewed on August 8, 2026 describe a Free plan at $0 for up to eight members, with public reception and visitor links, inquiry forms/basic handoff, member presence or status, three maps, and a stated map-tile allowance. The Business plan is listed at $12 per user per month and includes two guest-days per paid seat every day, AI reception, a response queue and employee handoff, browser phone, longer meetings, and private consultation rooms. Custom pricing is described for higher seat or verified-visitor allowances and additional review or onboarding needs.

These are planning inputs, not a permanent price promise. Limits, names, and included features can change. Verify the live Kiguri pricing and workspace settings before using these details in a proposal.

Calculate the starting requirement

First count the employees who need to own or accept visitor inquiries. Do not count every marketer if only client-service or business-development roles need queue access. Next estimate a typical day and a busy day: new visitors, concurrent conversations, and roles needed for live handoff.

If the Business allowance is still two guest-days per paid seat each day, an marketing agency can compare the seats it genuinely needs with the visitor pattern it expects. A team with four customer-facing seats would plan around the allowance associated with those seats, then confirm how Kiguri defines a guest-day and whether that covers its actual use. This is a prompt for verification, not a capacity guarantee.

Write assumptions plainly: "Three client-service members need queue access; most visitors are project prospects or current clients; a quarterly event may create a temporary spike." That is more useful than choosing a plan from a single website traffic number.

Use a small worksheet with four columns: visitor purpose, expected busy-day visitors, employee owner, and next destination. A engagement prospect may need a business-development host and a private introduction. An existing client may need the engagement owner and a controlled room. A partner may need alliances and a browser call. This worksheet turns visitor volume into operational seats and destinations rather than treating every click as equivalent.

Review the worksheet with the people who actually monitor the queue. If a role cannot accept visitors during a engagement deadline, record the backup path. If a visitor purpose rarely needs a live conversation, keep it in chat or a queued response. The result is a more honest estimate of seats and guest activity.

Match the plan to the operating workflow

Free can be a useful way to test a branded reception, visitor links, inquiry forms/basic handoff, presence, and a small map setup when the published limits fit. Use the test to learn which visitor purposes arrive and whether the team can own the resulting queue.

Business becomes relevant when the marketing agency needs AI reception, a response queue and employee handoff as a repeatable operation, browser phone, longer meetings, or private consultation rooms. Buy seats for employees who need those responsibilities, not every specialist who might answer in the future.

Custom may be worth discussing when visitor volume, verified-visitor allowances, seat count, phone needs, retention or DPA review, guided onboarding, or priority support fall outside the standard description. Describe the workflow and ask Kiguri to confirm current options.

Account for uneven engagement cycles

Guest demand can spike around a proposal, launch, client workshop, or partner event. Separate normal days from known peaks and decide who reviews the queue when engagement teams are busy. Write an after-hours message that accurately states whether visitors can leave an inquiry and when the team reviews it.

Presence and roles can help make live language truthful. An marketer may be online but unavailable for an unplanned engagement discussion. A queued response is better than a transfer that nobody owns. Review retention and access as visitor volume grows, since more inquiries mean more context in the queue.

Do not claim that a pricing model improves conversion, utilization, response time, or engagement outcomes without measuring your own operation. Confirm current visitor rules, plan limits, and workspace configuration before making public commitments.

Record the date of every pricing review because plan terms can change. When an marketing agency adds members or a new visitor campaign, update the worksheet and verify whether the current allowance still fits. Treat the public pricing page as the source of truth rather than copying an old proposal.

Keep one owner for this review and document the assumptions for each update each time, too.

This keeps pricing assumptions visible to the whole operations team.

FAQ

Is a guest-day a Kiguri billing definition?

This article uses guest-day as a planning model. Exact billing terms and allowances come from the current Kiguri pricing page and workspace agreement.

How many member seats should an marketing agency plan for?

Start with employees who need queue ownership, presence, routing, or private follow-up. Add seats when a real role requires them.

Is the Free plan enough for a small marketing agency?

It may be a useful starting point when the published member, visitor, map, and handoff limits fit the workflow. Verify current details before relying on a feature.

When should we discuss Custom?

Ask when visitor volume, seats, verified visitors, phone needs, retention review, onboarding, or support expectations do not fit the standard plan description.

Plan for responsibility as well as visitors

A guest-day planning model helps an marketing agency separate who works in the virtual office from who visits it. The practical decision combines member ownership, visitor patterns, live handoff needs, private destinations, and honest after-hours operations. Kiguri's live pricing page remains the authority for current numbers and limits.

Review Kiguri pricing and then [explore the customer reception](/) with your actual visitor intents and accountable hosts.

Sources and further reading

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

Sources and further reading

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