Turo-heavy hosts
For hosts who want a Turo Go alternative workflow without claiming an official Turo integration or scraping marketplace data.
Contactless access automation
Levy Guestpass
Time-gated guest unlock passes for Turo, Getaround-style, former HyreCar-style, and direct carsharing trips. Built into Levy Fleets with a dedicated native guest app.
OTP
Phone-bound guest access
ID
Host verification gate
API
OEM and hardware commands
Logs
Every command audited
What it replaces
A practical remote handoff layer for carsharing hosts.
Hosts still follow marketplace check-in rules. Levy Guestpass handles the access automation around that process: time windows, phone verification, command routing, fallback instructions, and support-grade logs.
Host-controlled ID gate
Guests cannot unlock until the host marks marketplace ID verification complete.
Phone and device binding
Each pass verifies the guest phone and binds commands to the verified device.
Trip-window enforcement
Unlock, lock, and find controls obey the session window and lock grace rules.
Provider-agnostic commands
Commands route through Levy's existing Uconnect, Smartcar, Linka, and hardware paths.
Lockbox operators
For operators who are tired of exposed codes, public lockbox placement, manual code rotation, and text-message proof gaps.
OEM app workflows
For hosts who can unlock with an OEM app but do not want to be on-call for every guest arrival and return.
Direct rental fleets
For smaller operators using Levy Fleets as the access, audit, and support layer for owned direct-booking trips.
Workflow
Built around the real host handoff.
Levy Guestpass does not pretend to be an official marketplace API. The host controls when a guest gets access, and the guest gets a focused pass for the trip.
1
Host creates a pass from Levy Fleets
2
Guest opens the link or native app
3
Guest verifies phone by SMS
4
Host confirms ID verification
5
Guest unlocks, locks, or finds the vehicle
6
Every event is logged for support
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.
Animated walkthrough
The pass moves from draft to verified to command-ready.
The host stays in control of the risk gates while the guest gets one focused access surface.
1
Create
Host selects vehicle, trip window, guest phone, and fallback instructions.
2
Verify
Guest verifies phone. Host completes marketplace ID verification.
3
Command
Guest can unlock, lock, or find the vehicle during the allowed window.
Controls
The guest sees only what they need.
A mobile web link and native app both use the same secure command gate. Hosts can rotate or revoke access without changing the vehicle setup.
Unlock
Lock
Find
Product screenshots
Guest app screens are built from the product surface.
The screenshots below come from the dedicated Levy Guestpass Expo app.
Session readiness
Phone verification
Command controls
Fallback support
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.
Trip window
Vehicle label
Verification status
Fallback-ready layout
Phone verification binds the session
The pass verifies the guest phone number before command access, which helps reduce forwarded-link and wrong-recipient risk.
OTP challenge
Guest phone match
Device binding
Retry limits
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.
Unlock
Lock
Find vehicle
Denied-state messaging
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.
RF pouch notes
Host contact
Provider status
Support escalation
Safeguards
Designed to avoid the obvious failure modes.
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
Pricing
Launch pricing for connected-car hosts.
Existing Levy carsharing hosts get a 60-day founding-host pilot with 250 included sessions.
Starter
$29/mo
Hosts testing remote handoff on a small carsharing fleet.
25 access sessions included
$1.50/session overage
- Guest magic links
- OTP and device binding
- Audit export
- Physical-key fallback copy
Growth
$99/mo
Active hosts replacing lockboxes and manual OEM-app unlocks.
125 access sessions included
$0.95/session overage
- Everything in Starter
- SMS and email delivery
- Bulk revoke
- Provider readiness warnings
Scale
$249/mo
Operators who need support workflows and larger audit volume.
500 access sessions included
$0.60/session overage
- Everything in Growth
- Support override audit trail
- Command-failure alerts
- Priority onboarding
FAQ and support
Support content for hosts, guests, and sales.
Levy Guestpass FAQ
Answers for hosts evaluating remote unlock links, ID gates, fallback keys, and native app access.
Host setup checklist
The pre-trip checklist for connected vehicles, physical fobs, access windows, and support escalation.
Smartcar setup guide
How to think about Smartcar/OEM readiness, command scopes, stale telemetry, and fallback paths.
Is Levy Guestpass an official Turo integration?
No. Levy Guestpass is a host-managed access layer. Hosts still follow marketplace rules, complete ID verification, and keep physical-key fallback available.
Can we describe it as a Turo Go alternative?
Yes, as comparative category language. We should not call the product Turo Go, use Turo branding as if it is official, or imply marketplace authorization.
Can it replace a lockbox?
It can replace many lockbox handoff steps for supported connected vehicles, but hosts should still keep a fob or physical key fallback in an approved RF pouch or lockbox workflow.
What vehicles are supported?
Guestpass routes through the connected-vehicle providers already configured in Levy Fleets, including Smartcar/OEM, Uconnect, Linka, and installed hardware paths where supported.
What happens when unlock fails?
The guest sees fallback instructions and contact actions, while the host and support team see the command failure reason, provider, timestamp, and audit trail.
Does the guest need the native app?
No. Mobile web is the default fallback. The dedicated Levy Guestpass app gives a cleaner repeat-access experience after internal testing builds are published.
Does Guestpass scrape Turo, Getaround, or HyreCar?
No. Hosts create access sessions manually or through authorized Levy Fleets workflows. Guestpass does not scrape marketplace messages, calendars, guests, or listings.
Why keep a physical key or fob?
Marketplace rules, vehicle provider outages, dead zones, drained batteries, or OEM account failures can make remote commands unavailable. Guestpass keeps the fallback path explicit.
Conversion tracking
GTM dataLayer events for page views, CTA clicks, and lead-form outcomes.
Support path
Guest support copy for failed unlocks, wrong phones, exposed links, and provider outages.
Compliance copy
Marketplace disclaimers, ID gates, and physical-key fallback stay visible.
Request access
Launch remote handoff without waiting on a marketplace integration.
Levy Guestpass is live in the Levy Fleets product surface and ready to package for hosts who already have connected vehicles. Tell us how your cars are accessed today and we will route the request into sales follow-up.
Smartcar/OEM fit check
Pilot scope and pricing follow-up
Fallback plan for lockbox or RF-pouch workflows