Guest-day pricing model for IT service desks

Define the guest day before estimating it

Write one sentence describing the event: “A two-hour employee technology fair,” “A customer onboarding afternoon,” or “A partner support session.” Note visitor groups, expected range, peak window, host coverage, conversation modes, and the result each visitor should reach.

A basic brief includes:

• **Visitor purpose:** orientation, support process, onboarding, partner help, or event attendance. • **Expected and peak volume:** a planning range, not a guaranteed count. • **Host coverage:** named service-desk employees, backups, and event owner. • **Modes:** chat, browser phone, video, screen sharing, or private room. • **AI content:** approved general answers and the human-routing boundary. • **Follow-up:** how unanswered or technical requests move to approved channels.

These inputs describe workload; they do not change Kiguri’s published product pricing.

Separate product allocation from event labor

Use two main budget buckets. **Allocated product cost** is the Kiguri plan and member seats your organization chooses for its ongoing operation. **Event labor and preparation** includes map and copy preparation, host coverage, AI answer review, coordination, follow-up, and contingency.

For an internal worksheet, write:

> **Estimated guest-day budget = allocated product cost + host coverage + preparation + follow-up + contingency**

This is a planning equation, not a statement about Kiguri invoicing. Do not turn it into a per-visitor charge or imply that Kiguri bills each line item.

Estimate coverage from the peak

Average volume can hide the real staffing need. If forty employees are expected across four hours but most arrive during a thirty-minute window, the peak determines coverage. Estimate how many simultaneous conversations one host can handle in each mode.

Chat may allow a host to acknowledge several general questions. Browser phone and video occupy a more focused block. Screen sharing may require a prepared workflow. A private room may need a host and a defined support path.

Create a table with primary host, backup, mode, and escalation rule. Kiguri’s response queue shows visitor context so an employee can accept or reassign the request. Presence helps identify who may respond, but it does not guarantee coverage, recovery, or an SLA.

Give AI a bounded event role

Prepare approved answers for event times, map destinations, service-desk hours, and how to request a host. Assign an owner to review them before the guest day and whenever details change.

Route account, access, incident, security, or technical questions to a person and the approved process. The AI should not provide credentials, diagnose an incident, promise recovery, claim that a system is secure, or imply compliance. Include time to write, test, and review AI content in preparation costs.

Plan the map and modes

Use a branded visitor link as the event front door. Name destinations for visitors: “IT support,” “Account or access,” “Customer onboarding,” “Partner support,” and “Events.” Keep a direct reception route visible.

When a host accepts, offer the mode that matches the request. Chat may handle a general process question. Browser phone can orient a visitor. Video can support onboarding. Screen sharing can show an approved public workflow. A private room can support a focused conversation after handoff.

The visitor access boundaries guide explains public, request-only, and focused destinations. The shared response queue guide covers assignment and follow-up.

Include follow-up and approved channels

Some visitors will need a ticket, authentication, or a technical channel after the guest day. Add time for reviewing the queue, reassigning requests, sending an approved next-step message, and confirming that sensitive details move to the correct process.

Define completion by route. An orientation visitor may be complete after receiving an approved answer. An access request may be complete only when it reaches the approved owner. An incident question is not complete because an AI greeting was shown.

Add a documented contingency

Use a time buffer or percentage for higher volume, host absence, and longer conversations. Write the assumption: “Reserve one backup host for the peak” or “Hold two hours for next-business-day follow-up.” A stated assumption is more useful than an unexplained round-up.

If the event grows, review product plan and staffing separately. Confirm current Kiguri plan details and member limits rather than assuming that a guest-day model changes capacity or billing.

Example planning scenario

Imagine a two-hour employee technology fair. One reception host answers general questions, an access specialist handles approved request routing, a support host covers customer questions, and an event owner monitors the queue. Chat is the default; browser phone or a private room is offered after acceptance.

The worksheet lists allocated Kiguri cost, map and AI preparation, host coverage, event coordination, follow-up, and contingency. It does not label those as per-visitor Kiguri charges. It is an internal decision tool for staffing and event readiness. Keep the assumptions visible to finance and service-desk owners.

Frequently asked questions

Does Kiguri charge an IT service-desk guest-day fee?

This article does not establish Kiguri billing. It is a planning model only. Check the [Kiguri pricing page](https://kiguri.com/#pricing) and confirm current plans, member limits, and terms before purchasing.

How should an IT service desk estimate a guest day?

Define visitor purpose, expected and peak volume, host coverage, modes, preparation, follow-up, and contingency. Combine internal event costs with the product cost allocated to the event.

Should AI reception be budgeted as zero labor?

No. Include time to prepare approved answers, test edge cases, review conversations, and route questions that need a person or approved technical channel.

Can this model promise an SLA or recovery time?

No. It estimates planning assumptions only. It makes no claim about IT performance, uptime, security, privacy, recovery, compliance, SLAs, or support outcomes.

Which Kiguri features can support the event?

Public Kiguri materials describe branded links, virtual map, AI reception, response queue, employee handoff, presence, chat, browser phone, video, screen sharing, and private consultation rooms. Confirm current availability.

Sources and further reading

• [Kiguri pricing](https://kiguri.com/#pricing) • [Kiguri virtual reception](https://kiguri.com/) • [Kiguri visitor access boundaries for IT service desks](https://kiguri.com/blog/visitor-access-boundaries-for-it-service-desks) • [Kiguri shared response queue for IT service desks](https://kiguri.com/blog/shared-response-queue-for-it-service-desks) • [Kiguri employee presence and availability for IT service desks](https://kiguri.com/blog/employee-presence-and-availability-for-it-service-desks)

Sources and further reading

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