Impeller with worn molded number
PartSnap should look for vane shape, shaft seal context, pump family, and a second photo of the pump label.
- Need: model plate
- Need: diameter or stamped number
- Ask for help when number is unreadable
These are conservative field examples for SplashLens and PartSnap. They show what the app should ask for before a tech orders, calls for help, or saves the visit details. No example is a manufacturer-confirmed fitment claim.
Try PartSnap FreeThe moonshot is a living field network: PartSnap identifies possible part families, Connected Pool Network adds smart-equipment context, training mode turns misses into field lessons, and the dashboard catches mystery parts for review.
PartSnap should look for vane shape, shaft seal context, pump family, and a second photo of the pump label.
Use unions, cable connector, controller model, cell length, and flow switch context to narrow the family without pretending certainty.
Robot parts often look similar across families. PartSnap should ask for cleaner model, power supply label, track profile, and basket style.
Automation work needs safety language and board/box model photos. The app should help package cleaner details for the experienced tech helping.
Lighting examples should ask for voltage, niche/fixture style, transformer label, and GFCI behavior before any recommendation.
PartSnap should prompt for tank model, grid count/height, manifold shape, and air-relief assembly proof.
Use model plate, displayed fault, ambient temperature, water temperature, flow condition, and qualified service boundary before recommending direction.
Controller proof should include probe age, calibration standard, flow cell condition, tank level, feed tube condition, and manual test comparison.
Connected equipment needs app screen, firmware/app status, Wi-Fi path, power proof, and local fallback checks before blaming the part.
Spa parts need controller ecosystem proof first: Balboa, Gecko, Waterway NEO, OEM-branded pack, or unknown.
Ozone, UV, and AOP proof should include the module label, status light, lamp age, injector/check-valve condition, tubing route, and flow proof.
Automation readings need manual test comparison, calibration proof, probe age, flow-cell condition, and feed-line/tank state.
Prompt for pipe size, valve body markings, actuator model, lid screw pattern, and O-ring dimensions.
Capture the display code, heater model, gas/electric context, serial plate, and manual reference before field action.
Ask for control box label, motor plate, switch style, cover brand, and qualified-safety verification.
Connected Pool Network asks for the controller family, app status, device assignment, wiring label, and what changed before the failure.
When a partner supplies official proof requirements, SplashLens can turn that into a verified card. Without that, it remains unverified guidance.
Every mystery part can become a short training scenario: what proof is visible, what is missing, whether to order, and what to tell the customer.
Pool schools, service companies, vendors, creators, and manufacturers can send a private example for feedback or partnership discussion. SplashLens can build safe training scenarios without implying endorsement.