Expected today
Approved invitations with an arrival window today
Prepare the host, destination, badge, and any required check.Connect pre-registration, host approval, arrival, front-desk check-in, onsite accountability, exceptions, checkout, and searchable visit history.
The system is useful when reception can see who is expected, who is waiting, who is onsite, what is overdue, and the exact visit record behind every signal.
Every count should identify the visit, host, destination, deadline, and response behind it.
Approved invitations with an arrival window today
Prepare the host, destination, badge, and any required check.Arrived visitors without a completed host handoff
Notify the host, record the response, and escalate when the wait passes the service target.Checked-in visits without a completed checkout
Keep the current location, host, expected checkout, and escort state visible.Open visits beyond the expected departure time
Contact the host or visitor and record the departure or exception.Do not bury approval, arrival, onsite status, and closeout in one free-text log.
Capture the visitor, company, purpose, site, host, arrival window, access zone, and supporting information.
One invitation ID and accountable host.Approve, return, reject, or cancel the request while preserving the reason and reviewer.
A visible decision rather than an email thread.Place approved visits in today’s expected-arrival queue with badge, escort, and destination instructions.
Reception knows what should happen before the person arrives.Confirm the visitor, create the active visit, issue the badge or pass, and record the host handoff.
A current onsite record with arrival time.Assign host delays, missing approvals, escort gaps, arrival mismatches, and overdue checkout.
One owner, severity, response due date, and next action.Record departure, badge return, closeout, and any unresolved follow-up.
The onsite list returns to an accurate state.Search completed visits by visitor, host, site, purpose, date, and exception.
Operational history without rebuilding a spreadsheet.Separate records preserve ownership while keeping the visit connected.
Owns the visitor, reason, host, site, arrival window, approval, access zone, and preparation instructions.
Creates the expected-arrival queue.Owns the arrival, check result, badge, escort, location, current status, expected checkout, and actual departure.
Answers who is onsite now.Owns the problem, severity, response owner, due date, action, escalation, and closeout evidence.
Prevents a reception issue from disappearing.Owns the site, destination, responsible host, default access zone, arrival instruction, and review date.
Keeps destinations and host ownership consistent.A new visitor type, approval path, destination rule, exception state, role view, or dashboard filter should follow the operating team’s policy cycle.
A fixed visitor product or custom portal may send the change through requirements, vendor scheduling, development, testing, and deployment over roughly 5–20 business days.
A trained Jodoo administrator can often configure and test one focused field, option, rule, role view, reminder, or dashboard change in about 30 minutes–4 hours.
Keep specialist products where their hardware, identity, safety, or regulatory capabilities define the purchase.
The priority is configurable forms, approvals, queues, host handoffs, exceptions, mobile-ready updates, dashboards, and frequent business-owned changes.
Native watchlists, identity verification, badge hardware, access control, emergency functions, or enterprise security certifications define success.
Visitor arrival must be purchased with native desk booking, room displays, occupancy, or a broader workplace platform.
It is the operating system for expected visits, approval, arrival, check-in, host handoff, onsite status, exceptions, checkout, and history. The useful version connects those steps instead of storing only a sign-in row.
Yes. A host or visitor can submit the visit details before arrival, and reception can work from an approved expected-arrival queue.
Yes. Use the active-visit record and dashboard for checked-in, onsite, overdue-checkout, and checked-out states. Keep the expected checkout and current destination visible.
Jodoo can retain badge numbers, check results, approvals, and visit status. Dedicated printers, identity verification, watchlists, and physical access control may require specialist hardware or integrations.
A trained administrator can usually add a focused field, status, choice, reminder, role view, or dashboard measure in the same working session. Test changes that affect permissions or integrations before rollout.
Yes. Include site, destination, host, access zone, and location-specific instructions, then give each reception team a filtered view while management reviews the combined operation.
Start with today’s arrivals, open a waiting or overdue visit, and test how your team would assign, resolve, and retain the response.