.svg){kind=small}
The value is app-based access, not platform dependency
Getaround proved that guests understand phone-based unlock. Guestpass lets operators bring that same expectation into their own fleet operations.
New: Tesla fleet integration Tesla Fleet Integration is here — launch your Tesla car sharing business.Learn more →
Getaround keyless entry
Getaround-style keyless entry for operators building their own access layer
Levy Guestpass gives carsharing operators guest unlock links, phone verification, trip windows, fallback instructions, and command audit logs without depending on a marketplace-owned access stack.
Give operators the guest convenience of app-based unlock while keeping access sessions, fallback copy, and command history under their own operating system.
Getaround keyless entryGetaround unlock with phone alternativeGetaround remote car accessGetaround-style carsharing accesskeyless entry for carsharing operators
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
Access ownership
Marketplace-owned hardware/app stack controls the full guest access path
Operator-owned Levy Fleets access sessions control guest command eligibility
Guest experience
Guest uses the marketplace app and marketplace-specific check-in flow
Guest opens a dedicated Guestpass link or app for a narrow trip-scoped control flow
Vehicle support
One proprietary access stack
Provider-aware routing across Smartcar/OEM, Uconnect, Linka, or supported hardware paths
The access link is narrower than a marketplace account
A Guestpass session can only expose the actions the trip needs: verify, unlock, lock, find, and fallback. It is not a full marketplace app.
Provider failures are part of the workflow
Connected-car access can fail because of immobilizer state, provider auth, battery, cellular signal, or vehicle state. Guestpass records and classifies those outcomes.
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.
Useful for former marketplace operators
Operators who liked phone-based unlock can keep the access pattern while moving sessions, support, and audit logs into their own workflow.
Not a Getaround integration
Guestpass does not connect to Getaround reservations or impersonate the Getaround app. It is for operator-managed trips and authorized Levy Fleets workflows.
Hardware is optional by vehicle
Start with supported OEM/Smartcar paths where possible, then use compatible hardware for cars that cannot be controlled through provider APIs.
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