Employee presence and availability for property management companies

Presence and availability answer different questions

Avoid confusion by giving each state a separate question.

**Presence asks:** Where is the tenant, and what is their current property workspace status? A tenant may be signed in, active in a map, in a meeting, away, or offline. Presence is useful for coworkers coordinating work and for understanding whether a person is likely to see an internal notification.

**Availability asks:** Can this team tenant accept a tenant inquiry through the reception right now? Availability should residents and tenantship account for coverage hours, the employee's current conversation, escalation rules, language or service experience expertise, and whether the chosen channel is staffed.

For example, a property operations specialist can have the presence state "active" while availability is "not accepting new visitors" because they are investigating an incident. A manager can be present but available only for scheduled calls. A specialist can be marked unavailable in the public reception while still working asynchronously on a queue.

Kiguri's public materials describe tenant presence or status as part of the property workspace experience and describe an inquiry flow that can reach an available employee. Teams should preserve that separation in their own labels, policies, and visitor messages.

A practical state model for property management companies

Most teams do not need dozens of statuses. A small set is easier to operate and explain:

• **Present (internal only):** The employee is in the property workspace and can see team activity, but no live tenant promise is implied. • **Available for live property operations:** The employee can accept a new reception handoff in the stated channel. • **Busy with a visitor:** The employee is already handling a tenant conversation. A queue or follow-up path should be offered instead of another live handoff. • **Available for scheduled work:** The employee can join a planned consultation but is not accepting unscheduled inquiries. • **Follow-up only:** The employee can review a request later, with an honest response expectation set by the team. • **Offline:** The employee is not monitoring the reception. The visitor should be directed to the team's documented follow-up route.

The names can differ, but every tenant-visible state should answer what happens next. Avoid exposing internal labels such as "deep work," "backstage," or "on-call rotation" unless the visitor understands them.

Why this distinction matters to visitors

A visitor usually wants to know three things before submitting an inquiry:

1. Is this the right place to ask? 2. Will someone respond now or later? 3. What information should I prepare?

Presence alone does not answer these questions reliably. An online map can suggest an immediate conversation even when that person is in a private meeting. Keep internal presence useful to residents and tenants while publishing a separate, conservative availability message to visitors.

For a property operations reception, visitor copy can be simple:

> Our property operations reception is open. Share your service experience area and a short description, and an available property operations employee will join when ready.

When no live employee is available:

> The property team is not taking live conversations right now. Leave the context of your request and we will follow up through the stated property operations channel.

Do not show "available now" merely because someone has an active browser session. The public message should reflect the handoff policy, not a technical heartbeat.

How Kiguri fits into the workflow

Kiguri provides a front door for tenant conversations: a visitor enters through a branded reception link, shares identity, tenant organization, and purpose, and meets an AI receptionist or inquiry intake flow. The request can move into a response queue and then to an available employee. Depending on the team's setup and current plan, the conversation may continue by chat, browser phone, video, screen sharing, or a private consultation room.

The service experience should not be described as deciding every staffing question automatically. A team still defines which employees accept live inquiries, which requests need a specialist, and what happens outside coverage hours. Kiguri is the reception and connection layer; the property operations operation owns the service policy.

Write a policy employees can follow

Before publishing presence labels, property managers should agree on a small set of operating rules. Define who can change an availability state, how often a person checks it, and what a visitor sees when the state is uncertain. A leasing coordinator might mark themselves available only while they can respond to a browser chat or phone request. A maintenance liaison may remain visible internally but appear unavailable to residents until the right handoff is confirmed. Keep the language neutral: it should describe the next conversation step, not imply a guaranteed response time, repair result, tenancy decision, or emergency service. Review the wording with the people who answer inquiries so the public flow matches daily practice.

FAQ

Is tenant presence the same as employee availability?

No. Presence describes a tenant's property workspace state. Availability describes whether the employee or team can accept a new tenant inquiry under the published handoff policy.

Should visitors see individual employee presence?

Only when the team has a clear reason and the displayed state cannot be mistaken for a live-service promise. In many cases, a team-level reception message is safer and easier to keep accurate than a directory of individual states.

Can Kiguri automatically decide who is available?

Kiguri's public workflow describes reception, inquiry context, a response queue, and handoff to an available employee. The team remains responsible for defining coverage, roles, escalation rules, and the exact availability policy. Confirm current property workspace behavior before publishing detailed automation claims.

What should happen when everyone is busy?

Keep the visitor's context in a queue or collect a follow-up request, then explain the next step honestly. Do not imply that a live employee is joining if the team is not monitoring the reception.

How should a property team measure this policy?

Track repeat explanations, queue age, handoffs that find the right owner, channel changes, and follow-ups that lack an owner. These operational signals help improve staffing and intake; they are not guaranteed response-time or conversion claims.

Sources and further reading

• Kiguri. (2026). *A virtual reception for tenant inquiries*. https://kiguri.com/ • Kiguri. (2026). *A virtual reception for tenant inquiries*. https://kiguri.com/ • Kiguri. (2026). *A virtual reception for tenant inquiries*. https://kiguri.com/ • Kiguri. (2026). *A virtual reception for tenant inquiries*. https://kiguri.com/

Verify live labels, plan limits, and channel availability before publication.

Sources and further reading

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