For the visit record
A modern browser and a staff account. Use a camera-capable device to capture condition evidence, and keep your existing physical key controls.
Hardware and connection requirements
Start with the devices at your counter.
A browser for the team. A camera for condition photos. A clear visit record that stays together.
GuestLot's connected Tesla features use owner-authorized vehicle data, without an added tracker. Each reading shows when it was observed.
What you need
A simple setup, with clear boundaries.
For vehicle readings
An authorized Tesla connection and a vehicle that can provide the requested data. Last-reported location is distinct from a staff-entered parking note.
For the owner handoff
Review the visit and explicitly enable the private report link when you want to share it. The owner does not need a GuestLot account.
Keys are a separate responsibility
Keep the driving credential under control.
A key card, a Bluetooth phone key, and an app authorization serve different purposes. Log physical handoffs and review Tesla permissions and any paired shop keys at pickup. Closing a GuestLot visit discards its stored connection tokens; it does not remotely remove every permission or key.
Tesla documents phone-key proximity and key management in its Model Y keys guide. See GuestLot's security and limits for product boundaries.
Questions
Before the first vehicle arrives
Do we need a special tablet or tracking device?
No proprietary tablet or added tracker is required for GuestLot. Use a modern browser for visit records and a device with a camera when capturing condition photos. Connected Tesla readings depend on the vehicle, owner authorization, and integration availability.
Does every advisor need a Tesla account?
No. Staff use their own GuestLot accounts to access the shop. Do not share a customer's Tesla password. Any physical driving key, added-driver access, or shop phone-key arrangement is a separate vehicle-access workflow.
Can a phone in the cloud act as a Bluetooth key?
GuestLot does not host virtual phone keys. A Tesla Bluetooth phone key requires a compatible phone near the vehicle. Remote API commands are a different capability and do not establish that a phone key is present or that a vehicle can be driven safely.
What can we do without connecting a Tesla?
Keep the visit, condition notes, photos, manual parking details, staff handoffs, and pickup record. Vehicle-reported location and Tesla readings remain unavailable and are labeled not recorded.
Is continuous monitoring active once we sign up?
No. Authorized snapshot refreshes show available readings with their observation times. Continuous telemetry and alert delivery require additional services to be provisioned and monitored; basic account setup does not establish continuous protection.
Put a clearer record behind your care.
Start with condition documentation and staff handoffs. Add available authorized Tesla readings when the connection is ready.