What should reception do when software support asks for remote access?
A pause, verify and authorize procedure for reception when someone claiming to be hotel software support requests remote access.
The essentials
- Keep remote access pending until the provider and the proposed work have been independently verified.
- Verify the support request and obtain manager authorization as two separate checks.
- If access has already been granted, escalate promptly through the hotel’s incident procedure.
Pause before allowing access
Do not install software, open a remote session or start screen sharing while an unexpected support contact remains unverified. Reception’s immediate job is to establish who requested the work and who can authorize access, not to decide whether the caller sounds technically convincing.
Booking.com warns that unauthorized device access through malware or remote-control software can result in identity theft, data theft and account takeover. This does not mean every remote-support request is malicious; it means granting access deserves a deliberate check.
Booking.com: device access and partner safety guidance
Hypothetical reception response: “We verify support requests before allowing access. I’ll contact the provider through our approved support route and ask our manager to confirm the work.”
Use the following as an original hotel procedure, not a provider-prescribed sequence. Apply it to unexpected calls, emails, messages and visits.
Record what the contact wants
Capture a short factual record in the hotel’s approved location. Do not follow instructions to open a link or install a tool just to obtain these details.
| Field | What to note |
|---|---|
| Claimed identity | Provider, caller’s name and contact channel |
| Reason | Stated problem and ticket reference, if supplied |
| Requested access | Device, proposed action and requested timing |
| Current position | Whether anything has been installed, shared or allowed |
| Next action | Responsible manager and follow-up point |
Keep guest information, passwords and verification codes out of this record. Treat a ticket reference as a detail to check, not proof of authorization.
Check whether the hotel requested the work
Ask the responsible manager or designated IT contact whether the hotel opened a support request. Compare the reported issue with the proposed work: which system is affected, which device needs attention and what help was requested?
An existing ticket does not automatically authorize any action connected to it. A request about a report, for example, should not silently become permission to access a reception workstation.
Hypothetical example: the manager confirms an unresolved printing issue, but knows nothing about the caller’s proposed software installation. Keep access pending while the provider confirms whether that installation belongs to the agreed work.
Reach the provider independently
The FTC advises checking suspicious emails or texts by contacting the company through a phone number or website known to be genuine, rather than details in the message. Applying that independent-contact principle to an incoming support call is a practical adaptation for reception.
FTC: contact a company through a known, genuine route
- End or pause the incoming contact without granting access.
- Find the hotel’s previously approved provider support route.
- Ask the provider to confirm the ticket, the person handling it and the proposed remote session.
- Record what was confirmed and any question still unresolved.
Do not substitute a callback number or support link supplied by the unverified contact. If the approved route is unavailable, keep access pending and refer the decision to the manager.
Escalate if access has already been granted
Tell the manager and designated IT contact promptly. Report when the session began, which device was involved, what was installed or shared and whether access appears to remain active. Do not copy credentials into the report.
Follow their incident procedure rather than improvising a workstation cleanup. If you cannot confirm whether the session has ended, state that uncertainty explicitly. Record the next action and owner instead of marking the matter resolved because the caller disconnected.
Make the decision possible on every shift
Keep approved provider contact routes and the manager or IT escalation route accessible to reception. Agree who can authorize remote work when the usual manager is absent. Until verification and authorization are complete, the status remains access pending.
When evaluating Stayelier or another hotel system, ask the provider to explain its actual support process. This article does not establish that Stayelier offers remote support, session recording, access approval controls or support-identity verification.
Include support responsibilities in your software evaluation
Bring the support questions from this guide to a product walkthrough. Agree who owns a reservation or room-assignment issue, how the hotel contacts the provider and what access the hotel must approve. Review the operational workspace separately; this guide does not promise a remote-support service or support-identity verification in Stayelier.
Review the hotel PMS workflows before your provider discussion
