Levy Fleets support
Help for hosts and guests
Get help with Levy Guestpass access links, vehicle commands, billing, onboarding, and Levy Fleets dashboard workflows.
Levy Guestpass support policy
Guestpass controls vehicle access, so support actions are conservative and audit-first. The fallback key or fob remains part of the host handoff process even when remote commands are available.
Unlock failed
Use the physical key or fob fallback instructions shown in Guestpass, then contact the host or Levy support. Support checks the command log and vehicle provider before any retry.
Wrong phone number
The host must update the guest phone in Levy Guestpass and send a fresh link. Old active links are disabled when the phone changes.
Link was forwarded or exposed
The host or support should rotate the link or revoke the session immediately, then confirm vehicle lock state and review the audit log.
Vehicle provider outage
Remote commands can fail if the OEM, Smartcar, Uconnect, Linka, hardware, or cellular provider is unavailable. The physical-key fallback remains the primary continuity path.
Support rules
- Hosts are responsible for marketplace ID verification before enabling unlock.
- Guests should never be instructed to bypass marketplace rules or physical-key fallback requirements.
- Support will not unlock a vehicle for a guest when the ID verification gate is still pending.
- Remote retries must be checked against recent provider errors, vehicle status, and command count limits.
- Emergency, safety, theft, or injury issues should be escalated to local emergency services first, then Levy support.