.svg){kind=small}
Keyless entry is the workflow, not the risk decision
Hosts still decide whether the guest is verified. Guestpass handles the repeatable access mechanics after that decision: OTP, time window, command routing, and fallback.
New: Tesla fleet integration Tesla Fleet Integration is here — launch your Tesla car sharing business.Learn more →
Turo keyless entry
Turo keyless entry for hosts who need guest-safe unlock links
Use Levy Guestpass to turn connected vehicle access into time-gated guest unlock links with phone verification, host ID gates, fallback-key instructions, and audit logs.
Replace reusable lockbox codes and on-call OEM-app unlocks with a session-specific pass that only works for the verified guest inside the allowed pickup and return windows.
Turo keyless entryTuro remote unlock for hostsTuro contactless check-in keylesskeyless entry for Turo carsremote unlock link for Turo guest
Comparison
What hosts are actually trying to replace.
Searchers are not looking for another generic fleet page. They need a practical answer for remote access, physical-key fallback, verification timing, and support proof.
Access decision
Typical manual or marketplace-owned path
Levy Guestpass path
Guest access
Lockbox code, host-triggered OEM unlock, or manual message thread
One mobile pass for phone verification, pickup copy, unlock, lock, find, and fallback
Key handling
Physical key instructions are often separate from the remote unlock step
RF pouch or lockbox fallback instructions stay inside the guest access flow
Security
Codes and instructions can be forwarded or reused
Hashed token, OTP check, device signals, ID gate, time window, and revoke controls
The guest does not get your OEM account
Guestpass exposes only trip-scoped controls. Guests do not receive the host’s OEM login, Smartcar account, or Levy Fleets dashboard access.
Every command is attached to the trip
A failed unlock becomes a support event with provider, timestamp, access state, and fallback visibility instead of a loose text conversation.
Marketplace operator notes
Built for search intent, constrained by real host obligations.
The strongest positioning is direct: keyless entry, remote check-in, and Turo Go or Getaround Connect alternatives. The implementation still needs verification gates and fallback-key discipline.
Do not unlock early
The host controls ID verification and Guestpass enforces the trip window before command controls become available.
Keep the key plan explicit
Remote access still needs a physical-key fallback because provider outages, low battery, poor signal, or marketplace rules can require it.
Use supported vehicle paths
Guestpass routes through configured Levy Fleets providers such as Smartcar/OEM, Uconnect, Linka, or supported hardware where available.
App screenshots
The guest app is built around status, verification, controls, and fallback support.
Mobile web remains the fallback path. The dedicated Guestpass app gives repeat guests a cleaner access surface after app distribution is approved for the host workflow.
Open pass
Trip status before commands
Guests first see the vehicle, access status, trip window, and next required verification step.
Trip window
Vehicle label
Verification status
Fallback-ready layout
Verify phone
Phone verification
The pass verifies the guest phone number before command access to reduce forwarded-link risk.
OTP challenge
Guest phone match
Device binding
Retry limits
Control window
Unlock, lock, and find
Commands are available only when the host ID gate, phone check, session state, and time window allow them.
Unlock
Lock
Find vehicle
Denied-state messaging
Fallback support
Fallback support
Guests see physical-key instructions and support actions when a provider command cannot be completed.
RF pouch notes
Host contact
Provider status
Support escalation
Safety gates
Remote access stays conditional.
Hashed public access tokens instead of reusable public lockbox codes
Guest phone OTP before command access
Device-binding signals for forwarded-link mitigation
Host-controlled ID verification acknowledgement
Trip-window and post-trip grace enforcement
Provider-specific command failure classification
Per-session token rotation and revoke
Audit export for support, claims, and disputes
FAQ
Answers for marketplace hosts.
These pages use marketplace comparison language for search clarity. Guestpass remains a host-managed Levy Fleets access workflow.
Does Levy Guestpass connect directly to Turo or Getaround reservations?
No. Guestpass is a host-managed access workflow inside Levy Fleets. Hosts create access sessions manually or through authorized Levy workflows instead of scraping marketplace calendars, messages, or guest data.
Can a guest unlock before the trip starts?
No. Guestpass keeps command access behind the trip window, phone verification, device signals, session status, and the host-controlled ID verification gate.
Does Guestpass remove the need for a physical key or fob?
No. Supported connected vehicles can reduce manual handoff work, but hosts should still maintain a physical fob or key fallback in an RF pouch or approved lockbox workflow.
What happens when the connected-car command fails?
The guest sees fallback instructions and support actions, while the host can review command status, provider response, timestamp, verification state, and any revoke or retry activity.
Reference points
Get Started Today
Pilot Levy Guestpass
Tell us how your vehicles are accessed today. We will map the right Guestpass pilot, provider setup, and fallback workflow.
Secure & Confidential
Response within 24 hours
127+ Active Fleet Partners
Step 1 of 2Personal Information