.svg){kind=small}
Lockbox codes are hard to audit
A shared code can be reused, photographed, forwarded, mistyped, or left on public property. Guestpass creates a trip-specific access path and records each event.
New: Tesla fleet integration Tesla Fleet Integration is here — launch your Tesla car sharing business.Learn more →
Lockbox alternative
A lockbox alternative for supported connected vehicles
Reduce exposed codes and manual code rotation while keeping physical-key fallback instructions available.
Connected access does not eliminate fallback keys
Remote commands can fail because of provider auth, signal, battery, or vehicle state. Guestpass keeps fallback instructions visible.
Support gets command context
Instead of relying on text-message screenshots, support can review phone verification, ID gate state, command attempts, provider responses, and revocations.
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.
Is Levy Guestpass an official Turo integration?
No. Levy Guestpass is a host-managed access layer inside Levy Fleets. Hosts still follow marketplace rules, complete ID verification, and keep physical-key fallback available.
Can we use it as a Turo Go alternative?
Yes, as comparative category language. The product should not be called Turo Go, and it should not imply official Turo approval or marketplace API access.
Does Guestpass replace a lockbox?
It can replace many daily lockbox handoff steps for supported connected vehicles, but hosts should still maintain a physical fob or key fallback through an approved RF pouch or lockbox workflow.
Which vehicles are supported?
Guestpass depends on the provider paths configured in Levy Fleets, including Smartcar/OEM, Uconnect, Linka, and supported hardware paths where available.
Does the guest need the native app?
No. Mobile web remains the fallback. The dedicated Levy Guestpass app gives a cleaner repeat-access experience once app distribution is approved for the host workflow.
What happens if unlock fails?
The guest sees fallback instructions and contact actions, while hosts and support can inspect the command failure reason, provider, timestamp, and audit trail.
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