1 · Find the visit
Use an approved reference such as booking code, appointment, visitor list or registration record when the customer supplies that interface.
The current RIFE check-in page positions AI avatars and kiosks for hospitality, healthcare and other visitor environments and publishes three hardware formats: lobby kiosk, wall-mounted tablet and desk-tablet version. The redesigned page now separates the universal arrival pattern—identify the visit, explain the next step, route the person, hand off exceptions—from sensitive identity, biometric and payment functions that require dedicated integrations.

The same interaction pattern can support a hotel guest, hospital appointment visitor, office guest or event attendee, but the source systems are different. Booking references, appointment records, visitor lists, QR codes, badges and queue systems must therefore be treated as customer-owned inputs rather than as a generic RIFE database.
The legacy page also claims facial recognition, ID verification, digital visitor logs, real-time analytics and large percentage improvements.



Use an approved reference such as booking code, appointment, visitor list or registration record when the customer supplies that interface.
Present required information, forms, queue/counter guidance or staff instructions without assuming identity verification.
Provide on-screen directions, wayfinding or a staffed escalation when the arrival cannot be completed through self-service.
ID/passport scanning, biometrics, payments, room keys, health declarations or access-control actions require their own approved systems and controls.
It guides a person through an approved arrival or registration process, presents information, can connect to a customer system where commissioned, gives directions and escalates exceptions to staff.
Not by default. Those capabilities appear in the legacy marketing copy but require separately specified hardware, privacy/security controls, consent and a verified customer workflow.
The current page publishes floor-standing lobby kiosk, wall-mounted tablet and desk-tablet/counter-top deployment options. Final hardware configuration and peripherals are confirmed per project.
The interface pattern can be reused, but the data, identity rules, integrations and escalation logic must be different for each environment.
No.