Practical customer feedback guide
How should a car wash test distance, glass, and lighting?
A car-wash feedback setup should be tested at the actual stopping point, with the real vehicle position and lighting. ThumbsUp uses a compatible camera-equipped Android tablet for a supported gesture, but a car, truck, window, glare, and weather condition should not be treated as interchangeable without a site test.
For Operations, facilities, or technology lead validating a car-wash feedback pilot before rollout.
Decision frame
Start with one physical service moment.
ThumbsUp helps an authorized team review a configured location and time signal. The setup still needs a site test for distance, lighting, reach, accessibility, privacy, and safe use.
Ask the question that matters to your team
Authorized managers can create or change the short question shown on assigned feedback devices. After Question Mode is enabled on those devices, customers answer the active question with a supported hand gesture—for example, “How good was the cleaning service?”—so each location can collect a signal about the service moment it wants to improve.
Test the customer's real view, not an empty bay
The useful test starts where a customer will actually stop. Set the tablet at the proposed height and angle, then test the distance from the driver or passenger position, the window state, the available hand position, and the time a vehicle can remain stationary.
Treat an open-air finishing area, an open window, and a closed window as different conditions. Do not describe a gesture as proven through a windshield or for every vehicle until those exact conditions work at the intended site.
- Use representative vehicle heights and driver positions, not only the vehicle used by the installer.
- Repeat the test in direct sun, shade, changing daylight, and the site's normal wet or spray conditions.
- Check that a driver can see and reach the prompt without leaning into a moving lane or taking an unsafe action.
- Record a fallback location when the proposed exit point is not stable enough for a customer interaction.
Record the operating envelope explicitly
A short test log prevents a successful demonstration from becoming an unqualified rollout claim. Record what was tested, what was visible, and what still needs a different placement or channel. The result is a site-specific operating envelope, not a universal promise about every wash layout.
Use the same labels in the dashboard and the site checklist so a later score pattern can be compared with the conditions under which the prompt was used.
| Condition | Record during the test | Pass question |
|---|---|---|
| Distance and angle | Vehicle position, camera height, angle, and reach | Can the intended customer position see the prompt without an awkward movement? |
| Window and vehicle type | Window open or closed, car or larger vehicle, driver side | Does the proposed interaction work for the vehicles the site actually serves? |
| Light and glare | Sun direction, reflections, shade, and time of day | Is the view usable across the planned operating periods? |
| Water and weather | Spray, rain, splash, mounting exposure, and cleaning routine | Can the hardware position be maintained without assuming dry conditions? |
Decide what happens when a condition fails
A failed condition is a placement decision, not a reason to pressure customers into an unreliable interaction. Move the point to a safer finishing area, revise the mounting angle, or use a phone-based channel for a longer follow-up when the site cannot provide a dependable stationary view.
If a site serves multiple vehicle classes, keep the test result tied to the class and position that were actually checked. A fleet lane or taller cab can require its own pilot.
- Pause expansion when glare, distance, or queue movement makes the interaction uncertain.
- Separate hardware or placement remediation from the interpretation of customer scores.
- Tell attendants which conditions are supported and when to offer a staff-assisted or phone-based route instead.
Illustrative test plan
Illustrative example: an operator tests a tablet at a tunnel exit at morning, midday, and evening positions. Midday glare makes the screen difficult to view, so the operator records a shaded finishing-area position instead of generalizing the morning result.
Illustrative example: a fleet wash has a different cab height and stopping distance from the consumer lane. The operator treats it as a separate deployment test rather than reusing the passenger-car setup.
Questions operators ask
How should a car wash test distance, glass, and lighting? questions, answered clearly.
Can ThumbsUp be described as certified through a car windshield?
No. A through-window or through-windshield use case needs to be tested at the intended distance, glass condition, window position, lighting, and vehicle type. Do not treat it as a universal capability without that evidence.
What lighting should a car wash test?
Test the site's real direct sun, shade, reflections, changing daylight, and wet or spray conditions at the proposed mounting point. Record the conditions rather than assuming one successful demonstration covers every period.
Should trucks and passenger cars share one placement test?
Not automatically. Vehicle height, cab position, distance, and stopping geometry can differ, so a fleet or truck lane should have its own site test.
Does a successful recognition test explain a low customer score?
No. Recognition and feedback capture are separate from the cause of a rating. Managers still need to inspect equipment, queues, staffing, and customer comments when a pattern appears.
Plan the right feedback point with ThumbsUp.
Bring the service journey, site constraints, and reporting questions. The contact form can help define what a responsible pilot should test before launch.
Book a car-wash feedback demo