OEM apps were built for owners, not guest handoff
They can be powerful, but guest access often becomes a manual host workflow. Guestpass wraps the command path in a guest-safe session with narrow permissions.
OEM app alternative
An OEM app alternative for guest carsharing access
Turn host-only OEM remote commands into guest-safe trip links with verification gates, time windows, and support logs.
Why hosts search for it
The category is really access control plus proof.
OEM app 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.
Avoid sharing OEM account credentials with guests.
Avoid manually triggering every guest unlock from a host phone.
Use provider readiness checks and fallback instructions.
Preserve one audit trail across all guest command attempts.
Deep dive
How this works in the actual handoff.
The vehicle provider can change later
A host may start with Smartcar/OEM access, then add Uconnect, Linka, or hardware for unsupported vehicles. The Guestpass guest experience stays consistent.
Support can see the provider state
When an OEM command fails, support needs context: stale telemetry, expired account auth, permission failure, vehicle offline, or unknown provider response.
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.
Does this require a marketplace API?
No. Hosts create or manage access sessions in Levy Fleets, then send a guest link. Guestpass does not depend on private marketplace APIs.
Does the guest get unlimited vehicle access?
No. Commands are gated by session status, time window, phone verification, device checks, and the host-controlled ID verification gate.
What is the fallback if remote commands fail?
The pass keeps physical-key or fob fallback instructions visible and records the provider failure for host/support follow-up.
Pilot Levy Guestpass
Tell us your access setup.
We will qualify your vehicles, marketplace workflow, fallback plan, and pilot timing.