Resident guest
Resident or host, arrival window, lobby confirmation, destination, guest status, and departure.
Connect resident authorization, appointment or work-order context, lobby check-in, host confirmation, access window, destination, exception, and departure.
The lobby needs different answers for a resident guest, delivery, contractor, service provider, prospect, and event guest—without losing one current view of who is inside.
A common visit lifecycle can branch into the correct confirmation, destination, and closeout.
Resident or host, arrival window, lobby confirmation, destination, guest status, and departure.
Recipient, reference, package or service context, approved handoff point, and completion.
Work order, property host, service entrance, access window, evidence, area, and closeout.
Appointment, resident or property owner, service purpose, equipment, destination, and completion.
Leasing appointment, agent, viewing destination, arrival instruction, and follow-up.
Event, organizer, attendee status, amenity or event area, arrival window, and departure.
The lobby should not depend on phone calls that disappear after the visitor enters.
Capture visit type, host or resident, purpose, destination, approved window, and any reference or evidence.
Expected visitor appears before arrival.Find the authorization, record arrival and check result, issue pass if appropriate, and start the visit.
No duplicate lobby log.Record the responsible person, destination, and access instruction.
The current owner is visible.Assign resident unreachable, delivery mismatch, missing work order, access-window conflict, changed destination, or overdue departure.
One property-team response record.Record checkout, pass return, completion, and unresolved follow-up.
The current lobby list is accurate.Keep property, intercom, credential, and door-control work in the systems designed for those responsibilities.
The need is configurable guest, delivery, contractor, service, event, lobby, exception, and dashboard records that property teams can change.
Lease, resident, unit, billing, maintenance accounting, amenity commerce, or resident-portal depth defines the purchase.
Intercoms, credentials, readers, elevators, turnstiles, cameras, and security controls determine physical entry.
Yes. Use a focused authorization with resident or host, visitor, arrival window, purpose, destination, and any property-specific instruction or approval.
Yes, but each needs a distinct branch. Deliveries need recipient, reference, handoff, and completion; contractors need work order, property host, access window, evidence, area, and closeout.
No. Jodoo can coordinate request, approval, pass context, exceptions, and status. Intercoms, credentials, readers, elevators, and physical access decisions require specialist systems or integrations.
Use explicit checkout, pass return, actual departure, and closeout. An expired access window alone should create an exception, not silently assume departure.
Yes. Govern property, destination, local host, visitor type, access window, and instruction, then provide filtered lobby views and a combined portfolio dashboard.
Run a resident guest, delivery, contractor, service visit, unreachable host, missing work order, access-window conflict, and overdue departure.