Host-controlled ID gate
Unlock stays disabled until the host marks marketplace or direct-rental ID verification complete.
Levy Guestpass
Time-gated guest unlock links, host-controlled ID gates, phone verification, fallback-key instructions, and audit logs built into Levy Fleets.
Guestpass session
ID verified
Window active
Commands gated
What it does
Unlock stays disabled until the host marks marketplace or direct-rental ID verification complete.
Guest links work only during the active session window and defined post-trip lock grace period.
Commands route through the vehicle access path configured in Levy Fleets, including Smartcar/OEM, Uconnect, Linka, or supported hardware paths.
Page views, OTP attempts, command denials, provider responses, revokes, and support actions stay attached to the session.
Workflow
Guestpass keeps the host in control of verification and fallback while letting guests self-serve the narrow access tasks.
Connect or configure the vehicle provider in Levy Fleets.
Create an access session with guest phone, trip window, pickup copy, and fallback instructions.
Send a magic link by SMS or email after the trip is ready.
Guest verifies the phone number and opens the pass.
Host marks ID verified before unlock is enabled.
Guest can unlock, lock, or find the vehicle during the allowed window.
Support reviews command logs and fallback instructions when something fails.
App screenshots
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
Guests first see the vehicle, access status, trip window, and next required verification step.

Verify phone
The pass verifies the guest phone number before command access to reduce forwarded-link risk.

Control window
Commands are available only when the host ID gate, phone check, session state, and time window allow them.

Fallback support
Guests see physical-key instructions and support actions when a provider command cannot be completed.
Provider readiness
Guestpass is provider-aware, but it does not guarantee remote commands. Provider auth, cellular state, vehicle state, and fallback-key readiness still matter.
Connect the host OEM account through Smartcar, confirm lock/unlock permissions, then refresh the vehicle in Levy Fleets before creating a Guestpass.
OAuth reauthorization or missing lock/unlock scope should be treated as a support-blocking issue before guest handoff.
Confirm the Jeep/Stellantis vehicle is eligible, has an active connected-services plan, and is configured with `iot_connection_type = uconnect`.
Credential/session refresh failures should route to Levy support before the host shares a guest link.
Use LINKA or installed hardware when OEM APIs are unavailable. Confirm the device identifier, cellular status, battery, lock state, and fallback key path.
LINKA merchant tokens and hardware SIM/device health are support-owned readiness checks.
Pricing
Existing Levy carsharing hosts get 60 days free and 250 included Guestpass sessions during the pilot.
For hosts testing contactless handoffs on a small carsharing fleet.
25 sessions included
$1.50/session overage
For active hosts replacing lockboxes and manual OEM-app unlocks.
125 sessions included
$0.95/session overage
For multi-market hosts and operators that need support workflows.
500 sessions included
$0.60/session overage
FAQ
Guestpass is access automation, not a shortcut around marketplace rules, vehicle provider limits, or physical-key fallback.
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.
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.
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.
Guestpass depends on the provider paths configured in Levy Fleets, including Smartcar/OEM, Uconnect, Linka, and supported hardware paths where available.
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.
The guest sees fallback instructions and contact actions, while hosts and support can inspect the command failure reason, provider, timestamp, and audit trail.
Tell us how your vehicles are accessed today. We will map the right Guestpass pilot, provider setup, and fallback workflow.