Reservation lookup
Start from the booking information and lookup method agreed with the property and PMS.
Middle East hotel arrival
Hotel self check-in planned around Middle East guest journeys.
Evaluate reservation lookup, identity steps, registration, payment, deposit collection, keycard issuance and PMS synchronization as one property-specific arrival workflow.
Actual hotel deployment / customer identity withheldVisible todayReal M100 check-in, deposit and checkout demonstrations
Project scopeGuest journey, hardware, PMS, payment and keycard handoffs
Language boundaryArabic interface and documents confirmed for the selected configuration
Operational fit
Define the complete arrival path before selecting the kiosk configuration.
A kiosk is only one part of hotel arrival. The project must define how a guest finds a reservation, presents a passport or identity document, reviews registration information, pays any balance or deposit, receives room access and gets help when self-service cannot continue.
MythAsia uses the hotel’s current process and vendors as the starting point. The public M100 footage demonstrates the working product flow; Middle East language, document, payment and integration requirements are then confirmed for the individual property.
View the complete global kiosk page (English) →Hotel self check-in kiosk
Evaluate reservation lookup, identity steps, registration, payment, deposit collection, keycard issuance and PMS synchronization as one property-specific arrival workflow.
Passport and identity steps
Define accepted documents, verification points, privacy responsibilities and staff escalation.
Room payment and deposit
Map balances, deposits, receipts and interruption handling around the approved payment environment.
Keycard and PMS handoff
Complete room-access issuance and update the agreed arrival status in hotel operations.
A six-step arrival sequence for project review.
MythAsia uses the hotel’s current process and vendors as the starting point. The public M100 footage demonstrates the working product flow; Middle East language, document, payment and integration requirements are then confirmed for the individual property.
- 01
Choose language and find the reservation
Confirm the guest’s starting languages, lookup inputs and booking-not-found path.
- 02
Read the agreed identity document
Verify supported passports or documents and define what happens when scanning fails.
- 03
Review guest and stay details
Present the registration information and required acknowledgements clearly.
- 04
Complete digital registration
Capture required fields and signatures in the agreed document workflow.
- 05
Process payment or deposit
Confirm terminals, currencies, receipts and safe recovery from an interrupted transaction.
- 06
Issue access and update operations
Provide the keycard or agreed room-access handoff and synchronize status with the PMS.
Confirm these Middle East requirements in writing.
Share the country, property type, room count, required languages, current PMS, payment and keycard environment, arrival volume and target timeline.
Arabic and English
Interface language, registration text, terms, receipts and staff-assistance messages.
Documents and data
Accepted passports or identity documents, retention, access and hotel responsibilities.
Local connections
PMS, payment terminal, currencies, deposit rules, printer and keycard compatibility.
Delivery model
Remote discovery, local partner scope, import, travel, installation, training and support coverage.
Evidence before claims
Inspect real MythAsia product evidence.
Use the published workflow and product pages to understand what is visible today. Confirm language, integration, delivery and local requirements separately for the proposed Middle East project.
View verified workflow evidence →↗Questions and boundaries
Evaluate MythAsia hotel self check-in kiosk workflows for Middle East properties, including passports, payments, deposits, keycards and PMS connections.
Is the M100 interface already available in Arabic?
The current public demonstrations show English and Chinese prompts. Arabic interface, registration text and documents must be confirmed in writing for the proposed configuration.
Can the kiosk scan passports and collect a deposit?
The published M100 workflow shows passport scanning, guest details, terms, room payment and deposit collection. Accepted documents and local payment compatibility are verified per project.
Can it connect to our current PMS and keycard system?
Compatibility depends on the property’s vendors and available interfaces. MythAsia reviews the required data and room-access handoff before confirming scope.
Can a hotel start with one kiosk?
The starting scale is defined around the property, arrival types, acceptance criteria and support plan. A focused pilot may be considered before broader deployment.
Middle East project enquiry
Review your Middle East arrival workflow with MythAsia.
Share the country, property type, room count, required languages, current PMS, payment and keycard environment, arrival volume and target timeline.