New:Thread Pilot—AI follow-ups for Gmail.
Learn more

Product tour

See the Guestpass handoff from host to guest.

The product is split into two surfaces: the host creates and audits sessions in Levy Fleets, while the guest opens a focused pass for verification, commands, and fallback support.

Levy Guestpass product mockup showing host workflow and guest controls
1

Host-created access session

The host chooses the vehicle, trip start/end, guest phone, marketplace label, pickup instructions, and physical-key fallback copy.

2

ID verification remains manual by design

Guestpass does not unlock before the host marks marketplace or direct-rental ID verification complete.

3

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.

4

Support sees the audit trail

Page views, OTP attempts, denied commands, successful commands, provider failures, support overrides, and revocations stay attached to the session.

Guest app screenshots

The guest sees status, verification, controls, and support.

Levy Guestpass app open pass screen

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
Levy Guestpass phone verification screen

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
Levy Guestpass control window screen

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
Levy Guestpass fallback support screen

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

Try it with your vehicles

We will map this tour to your real handoff.

Tell us your vehicle provider, marketplace workflow, fallback key process, and pilot timing.

We will use this to qualify your vehicle access setup and route the right follow-up.

Contact

Tell us what you're building and we'll get in touch fast

Ship a proof-of-concept, integrate Metro2, or hand off the workflow entirely—we respond within one business day and loop in the right Switch Labs partner for your stack.

Response Time
< 24 hours
Delivery Options
Product | Services

By submitting you agree to let Switch Labs contact you about relevant products and services.