Trust starts with telling it straight.
Clear permissions. Visible limitations. Records that distinguish what the vehicle reported from what a person observed. These are product requirements, not footnotes.
Access begins with permission.
Connected readings require the vehicle owner’s authorization through Tesla. The owner can revoke third-party access through Tesla and remove a paired key from the vehicle. GuestLot does not ask for the owner’s Tesla password.
- Limit the connection to the authorized vehicle and custody purpose
- Show unavailable or revoked connections clearly
- Do not equate authorization with verified key pairing
The right people. The right record.
Staff access is scoped to the shop they belong to. Owner sharing is an explicit shop choice. Public reports provide a visit summary without exposing private staff notes or precise location coordinates.
- Private report access by default
- Owner links expire and sharing can be disabled
- Internal records require shop authentication
Unknown is an honest answer.
A missing battery reading is not zero. An absent lock reading does not mean locked. Where a signal was never collected, GuestLot prints “not recorded” rather than a zero or a blank. Last reported location needs a timestamp and source, and staff-recorded location must be labeled as an observation.
- Missing data reads “not recorded”, never 0% and never an empty field
- No invented live telemetry for disconnected visits
- Show freshness alongside available readings
- Keep data gaps visible in both the workspace and report
A handover deserves a real check.
GuestLot can close its own custody connection and record the handover. Tesla-side key removal is a separate operation with its own requirements. We do not present local status changes as verified removal of every key. Three limits below are properties of Tesla’s platform, not choices we made, and no software can work around them.
- An NFC key card cannot be remote-wiped, has no expiry, and leaves no per-card usage audit trail — a card handed back is only accounted for by counting the cards
- Tesla’s Fleet API has no set_service_mode command. Service Mode is entered on the vehicle touchscreen or through Tesla Toolbox, so an authorized app can read whether it is on and never set it
- Valet Mode locks the frunk, which makes it the wrong default for PPF, wrap, and collision work — we do not turn it on for you
A useful record, with clear limits.
Preserve recorded readings and timestamped observations so a visit can be understood later. These records can support an internal review or claim file together with original evidence. GuestLot does not certify legal admissibility or insurance coverage.
- Distinguish staff statements from vehicle readings
- Keep original condition photos and repair authorizations
- Review your shop’s own retention and insurer requirements
A clearer answer.
A better start.
Can staff see precise vehicle location?
Authorized shop staff can see a valid last reported position with its timestamp during custody. A staff-recorded location is labeled separately. Precise coordinates are not included in public owner reports.
Does GuestLot guarantee a car cannot be driven?
No. GuestLot is a visibility and documentation tool. Physical keys, vehicle settings, connectivity, owner authorization, and shop procedures affect what can happen to a vehicle.
Is a closed record independently certified or tamper-proof?
No. GuestLot preserves the recorded visit and restricts normal application edits, but it does not provide an independent notarization, a forensic chain-of-custody certification, or a guarantee of legal admissibility.
Make the next handover
a better one.
$179 per location per month · 14 days free · No credit card required