Operators want the access primitive without platform lock-in
Phone unlock, vehicle location, and return locks are useful primitives. Guestpass packages the access portion for operators running their own workflow.
Getaround Connect alternative
A Getaround Connect alternative for independent carsharing operators
Levy Guestpass gives operators a provider-agnostic access layer for guest unlock links, trip-window controls, fallback instructions, and audit logs across supported connected vehicles.
Move the access workflow out of a marketplace-owned box and into a provider-aware, auditable host dashboard plus guest pass.
Getaround Connect alternativeGetaround Connect replacementalternative to Getaround Connectcarsharing remote unlock softwareconnected car access for hosts
Comparison
What operators are trying to replace.
These searches come from operators who need guest access, verification timing, fallback instructions, and proof in one workflow.
Access decision
Typical path
Levy Guestpass path
Control layer
Dedicated marketplace hardware and app flow
Levy Fleets session layer with provider-specific command routing
Operator workflow
Marketplace handles booking, verification, unlock, and return
Operator keeps booking and verification decisions, Guestpass handles access and proof
Fallback planning
Marketplace-specific key, immobilizer, and support expectations
Per-trip RF pouch, lockbox, host contact, and provider-failure instructions
Why hosts search for it
The category is really access control plus proof.
Getaround Connect alternative searches usually come from hosts who already have demand but need a cleaner way to hand off a vehicle without exposing lockbox codes, sharing OEM credentials, or losing the audit trail.
Provider-agnostic access layer for mixed fleets.
Guest links, trip windows, fallback instructions, and support proof.
Smartcar/OEM and Uconnect first, compatible hardware where needed.
Built for operators with marketplace, direct, or replacement-rental demand.
Deep dive
How this works in the actual handoff.
Guestpass is not one hardware bet
The access provider can vary by vehicle. That matters for mixed fleets where one car supports OEM API control and another needs installed hardware.
Audits matter when the marketplace is not doing everything
If you own the workflow, you also need proof. Guestpass keeps verification state, command attempts, fallback visibility, provider response, and support notes together.
Product tour
Guestpass is a pass, not a loose instruction thread.
The guest app and mobile web flow keep verification, command controls, and fallback support in one place.
Open pass
Trip pass opens with status first
Guests see the vehicle, access window, verification status, and the next required step before any command button is emphasized.
Verify phone
Phone verification binds the session
The pass verifies the guest phone number before command access, which helps reduce forwarded-link and wrong-recipient risk.
Control window
Controls unlock only inside policy gates
Unlock, lock, and find-vehicle actions are shown only after the session, phone, device, ID gate, and time window allow it.
Fallback support
Fallback instructions stay visible
When provider commands fail or a physical fob is required, guests see fallback instructions and support actions without leaving the pass.
Controls and safeguards
Built to keep access narrow.
Guestpass should make remote access easier without making it casual. The product keeps host verification, fallback keys, and provider failure states visible.
Hashed public access tokens instead of reusable public codes
Guest phone OTP before command access
Optional device binding for forwarded-link mitigation
Host-controlled ID verification gate
Trip-window and post-trip grace enforcement
Provider-specific command failure classification
Bulk revoke and per-session token rotation
Audit export for disputes, claims, and support
Guest mobile surface
The guest opens a focused pass instead of receiving OEM credentials, screenshots, or reusable lockbox codes.
Time-window enforcement
Command access follows the trip window, session state, verification status, and lock grace rules.
Audit-ready events
Views, OTPs, denials, commands, provider failures, revokes, and support actions stay attached to the session.
Fallback-first support
Guests still see physical-key fallback instructions when provider access fails or a fob workflow is required.
Operational model
Host-owned setup, guest-safe controls.
Host-created access session
The host chooses the vehicle, trip start/end, guest phone, marketplace label, pickup instructions, and physical-key fallback copy.
ID verification remains manual by design
Guestpass does not unlock before the host marks marketplace or direct-rental ID verification complete.
Command routing uses connected providers
The guest action routes through the vehicle path already configured in Levy Fleets, including Smartcar/OEM, Uconnect, Linka, or hardware paths where available.
Support sees the audit trail
Page views, OTP attempts, denied commands, successful commands, provider failures, support overrides, and revocations stay attached to the session.
FAQ
Practical answers before a pilot.
Is Levy Guestpass an official Turo or Getaround integration?
No. Levy Guestpass is a host-managed access layer for authorized Levy Fleets workflows. It does not scrape marketplace data or claim official marketplace authorization.
Can guests unlock before the trip starts?
No. Commands are gated by trip window, session state, phone verification, device checks, and the host-controlled ID verification gate.
Does it replace a physical key or fob?
Not completely. Guestpass can reduce lockbox and manual OEM-app unlock work, but hosts should still keep a physical-key fallback in an RF pouch or approved lockbox workflow.
What happens if remote unlock fails?
The guest sees fallback instructions and support actions, while the host can inspect the provider response, command timestamp, verification state, and audit trail.
Pilot Levy Guestpass
Tell us your access setup.
We will qualify your vehicles, marketplace workflow, fallback plan, and pilot timing.