Send a secure pre-arrival link for guest details, ID, card-on-file setup, and policy acknowledgments.
Staff creates each invitation, chooses email or SMS, and reviews the guest's submission before marking it verified.
Mobile Guest Check-in is a staff-initiated secure form. The desk enters the guest and stay details, sends the invitation by email or SMS, and reviews the completed submission. Guests can confirm contact and stay details, upload identification, set up a card on file, add optional vehicle information, and acknowledge hotel policies from their phone.
Three representative previews of Mobile Check-in: the guest form, ID upload, and front-desk review.
Before a busy arrival window, the desk still needs the guest's contact details, ID, card-on-file setup, and policy acknowledgments. Waiting until the guest reaches the counter puts every step into the same queue.
Move the form to the guest's phone, then give staff one submission to review before arrival.
secure invitation and review, while the PMS stays separate
Every step ties to a real, connected feature.
Staff sends a secure email or SMS link. The guest completes card verification, uploads the documents the hotel requests, and e-signs. Staff review the audit PDF, fraud analysis, and rebuttal documents.
Invite a guest to complete check-in details, review the submission, share a branded stay portal, and keep human conversations and service requests tied to that stay.
Staff review the local recommendations, choose what to include, and print a personalized handout with an optional expiring QR link for the guest.
No. It collects pre-arrival information beside your PMS. Staff review the submission and can record verification and key handoff in Hotel Central. That status does not change the PMS reservation, post to its folio, or issue room keys; the desk still completes its normal arrival procedure.
Staff creates an invitation with the guest and stay details, then chooses email or SMS delivery. SMS depends on the hotel having messaging set up and the delivery being eligible. Staff can also create a shareable link without sending a message and give that link to the guest directly.
Guests can confirm contact and stay details, upload identification, save a card on file, add optional vehicle information, acknowledge hotel policies, and provide a digital signature. They open the secure form from their invitation on their phone; the submission then waits for staff review.
No. Uploading ID is document collection, not automatic identity clearance. The form requests front and back images; for a passport, it asks for the photo page in both upload fields. Staff must review the submission and follow the hotel's identification policy before choosing Verify or Reject.
No. The card-on-file step saves a payment method; it is not a room-payment receipt or a PMS folio posting. Your team still follows the hotel's payment and authorization procedures. Do not treat a submitted or verified intake form as proof that the stay has been paid.
Authorized staff review the submitted record, verify it or reject it with a reason, and record key handoff separately after verification. These are staff-controlled steps in Hotel Central, not an automatic arrival approval or a substitute for the desk's PMS work.
An expired, rejected, or voided link shows that it is no longer active and directs the guest to the front desk. Staff should resolve the invitation with the guest rather than assume an old link can still accept a submission. A submitted form shows a receipt screen instead of reopening the intake steps.
No. Mobile Guest Check-in is the pre-arrival intake and review workflow within Guest Hub. The stay portal is the guest-facing place for stay information and messages. Completing the intake form alone does not mean the guest has arrived or that the desk has handed over keys.