Entry 01 Table
Detail by detail: its source and its job
Most rows start life in one of three places: a phone conversation, the booking window, or the technician standing at your appliance. The bottom two are different; the pages gather them by themselves as you browse, and a later section describes how.
Table 1Personal details on file
| Detail | Source | Purpose |
|---|---|---|
| Name | Said to the dispatcher, or entered in the booking window | So the technician knows whom he is meeting and the job sheet carries the right owner |
| Phone number | Your call itself, or the booking window | Confirming the slot, a heads-up before arrival, a ring once a part comes in |
| Street address of the kitchen | Spoken on the phone or entered while booking | Routing the technician to your driveway and fitting the trip into a day that suits your stretch of coast |
| Your description of the fault | In your words: igniters clicking nonstop, a griddle that never gets hot, a steam oven flashing a water warning | Letting the technician prepare for that specific Wolf model category before he knocks |
| Job sheet | Filled in on site once diagnosis is done | Showing what was wrong, the figure you approved, what got replaced and whether a second trip is pending |
| Proof of payment | Issued when an outside payment provider completes the charge | Tying money received to the right job; card numbers themselves stay off our systems |
| Visit statistics | Recorded as you read by the counting script our group runs; a visit's IP address is added only if it includes a phone or booking tap | Telling which pages earn their keep and how briskly they load, plus, from tap IPs kept 90 days, the rough whereabouts of people who call or book |
| PostHog usage data and replays | PostHog's own recorder, loaded by that script, except in browsers sending either of the privacy signals named further down | Spotting what the site should do better; replays last 30 days, other material up to twelve months |