Employee presence and availability for franchise operators

Why the distinction matters in a franchise network

Franchise teams often work across locations and time zones. A regional manager may be present for internal work but unavailable for a customer call. A local host may be available for chat but not for video. A specialist may want to accept a scheduled browser-phone conversation while declining walk-in requests. If the reception shows every active member as immediately reachable, visitors may be transferred repeatedly or wait without an explanation.

Start by listing visitor situations rather than internal job titles: current client question, new-business introduction, franchise prospect, tenant request, vendor inquiry, and event arrival. Then decide what availability means for each situation. The policy should be understandable to a new staff member and easy to explain to a visitor.

Create a simple status model

Use a small number of customer-facing states:

• Available for new chat conversations. • Available for browser phone requests. • Available for video or screen-sharing conversations. • Busy with an existing visitor. • Away or unavailable for new visitors.

The exact labels should match the options configured in your Kiguri workspace. Do not publish a status that the team cannot maintain. If a host changes from chat to a meeting, the reception should stop presenting chat as the preferred path. If your team cannot update status reliably, use a broader “request a host” flow and explain that response timing depends on availability.

Route by purpose and channel

An inquiry about a current client account may need the account owner, while a franchise prospect may need a development host. A tenant may need the local office contact. Include the visitor's purpose in the queue entry so a host can decide whether chat, browser phone, video, screen sharing, or a private room is appropriate.

These routing rules are operating decisions, not automatic classifications that Kiguri promises to make. Keep a human accountable for accepting and reassigning. When two hosts are available, give the first owner a clear reason to accept. When no host is available, preserve the original context instead of asking the visitor to start again through another channel.

Set expectations in the reception copy

Visitor-facing text should describe the next action accurately. “A franchise host can join by chat when available” is safer than “Connect instantly.” “Request a browser-phone conversation and include your purpose” tells a visitor what will happen. If the team offers a follow-up path outside the live window, state that plainly without promising a deadline you cannot maintain.

Explain channel differences in simple language. Chat is useful for a short answer. Browser phone is a voice option without a separate application. Video and screen sharing add context for a demonstration or workflow explanation. A private room is appropriate after the host accepts a conversation that should not remain in the public reception.

Make maps reinforce availability

Kiguri's virtual office map can help visitors understand destinations such as reception, client meetings, partner introductions, and private consultation rooms. Avoid using a map as a directory of every employee. Expose a small set of visitor goals and let the queue determine which available host takes ownership.

For multiple franchise locations, label destinations by location and purpose. Keep internal rooms private, and provide one direct reception link for visitors who are unsure where to go. A map should reduce orientation friction; it should not make a visitor guess which internal room contains a free employee.

Handle busy and offline states

Write an offline policy before launch. Decide whether a visitor can leave an inquiry in the shared response queue, request another host, or view public information. Preserve the name, organization, purpose, and original question so the next employee can continue the conversation. If a request is reassigned, tell the receiving host why.

Busy states need similar care. A host already speaking with a visitor should not be presented as the default for a second urgent-looking request. Offer a different channel or a private follow-up path when appropriate. Avoid words such as “priority” or “guaranteed” unless your team has defined and can honor them.

Pilot with a coverage table

Create a simple table for one location and one regional team. List visitor type, preferred first owner, customer-facing channel, backup owner, and offline wording. Run scenarios at opening, during a busy period, across a time-zone handoff, and after the last host leaves. Ask participants whether the displayed state matched what they could actually do.

During the pilot, review the queue for repeated questions, unclear ownership, and visitors who selected a channel no host could accept. Improve approved AI answers and reception copy based on those observations. Do not infer that a short queue means demand is low; it may mean visitors cannot find the correct path.

Keep the policy portable across locations

A franchise brand often has a central team and local operators. Write the availability policy so a new location can adopt it without copying another office's staffing assumptions. Define the minimum host role, the backup role, and the words shown when both are offline. A location can then add its own hours or destinations while keeping the same visitor-facing logic.

Review the policy whenever a location opens, a host changes responsibilities, or a new conversation channel is introduced. Retire labels that visitors misunderstand. If a local team uses “on site” to mean something different from “ready for a visitor,” choose separate labels. Consistent language across locations makes a branded reception feel dependable while still allowing real staffing differences.

Keep a short change log for approved answers and status definitions. This is especially useful when a public service description, office address, or contact owner changes. The goal is not to create a heavy operations manual; it is to ensure that the next host sees the same expectations the visitor saw at arrival.

Frequently asked questions

Does presence mean an employee is available to customers?

No. Presence indicates participation in the workspace; customer-facing availability is a separate policy for accepting new conversations.

Can a host be available for chat but not video?

Yes, if your team defines channel-specific availability and communicates it accurately in the reception.

What should happen when no franchise host is available?

Keep the visitor's context in the response queue or offer a clear alternate destination. Explain the next step without promising an unsupported response time.

Does Kiguri automatically schedule staff coverage?

This guide does not claim automatic staffing or scheduling. Operators remain responsible for coverage, statuses, and handoff policy.

Sources and further reading

• [Kiguri home](https://kiguri.com/) • [Kiguri pricing](https://kiguri.com/#pricing) • [Kiguri security information](https://kiguri.com/security) • [Kiguri blog](https://kiguri.com/blog)

Confirm current Kiguri behavior, plan limits, and team availability before publishing a promise to visitors.

Sources and further reading

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