← OneStudio Guides

Websites

Car Wash Equipment Service Request Form: Fields That Matter

Build a car-wash equipment service form around site, equipment type, brand/model, operating status, issue, urgency, photos and PM needs without turning the website into dispatch software.

Overview

A car wash equipment form should help the service team answer:

Current B2B equipment providers already use this structure.

  • Which site?
  • Which equipment?
  • Is the wash down?
  • What changed?
  • How urgent is the problem?
  • Is this repair, maintenance, parts or installation?
  • Are photos or videos available?

Field 1: Company and requester

Collect:

  • company;
  • name;
  • role;
  • phone;
  • email;
  • preferred contact method where useful.

Field 2: Site name and address

Wash-Right currently asks for:

That is a strong model because multi-site operators need site-level routing.

  • site/location name;
  • site address;
  • city/state/ZIP;
  • on-site contact.

Field 3: On-site contact

Ask for:

The person who approves the repair may not be the person meeting the technician.

  • name;
  • phone;
  • same as requester / different.

Field 4: Equipment type

Useful options can include, where supported:

Wash-Right and D&S use equipment-type routing for exactly this reason.

  • tunnel / conveyor;
  • in-bay automatic;
  • self-serve bay;
  • pressure washer;
  • vacuum;
  • dryer;
  • pump station;
  • chemical system;
  • pay station / POS;
  • water treatment/reclaim;
  • door;
  • other.

Field 5: Brand / model

Ask:

Do not make this mandatory for an emergency.

  • brand;
  • model;
  • not sure.

Field 6: Serial number

Optional.

Useful for:

  • parts;
  • warranty;
  • configuration;
  • equipment history.

Field 7: Bay / tunnel position

For sites with multiple machines:

  • bay number;
  • tunnel section;
  • component location;
  • not applicable.

Field 8: Equipment status

Current Wash-Right form uses a useful split:

That is better than a vague urgency field.

  • down completely;
  • intermittent;
  • operating but not correctly.

Field 9: When did the issue start?

Ask for:

  • today;
  • yesterday;
  • this week;
  • recurring;
  • after maintenance/change;
  • exact date if known.

Field 10: Problem description

Prompt:

Describe what the equipment is doing, any error messages, unusual noise/leak/behavior, and what happened before the problem began.

Keep this customer-reported.

Field 11: Service type

Useful options:

  • emergency repair;
  • priority repair;
  • routine repair;
  • preventive maintenance;
  • installation;
  • upgrade/retrofit;
  • parts;
  • troubleshooting/technical support;
  • not sure.

Field 12: Preventive maintenance

Shore currently distinguishes:

A provider can adapt this to its actual plans.

Do not publish recurring options the company does not sell.

  • monthly PM;
  • PM when requested;
  • one-time repair.

Field 13: Preferred service date

Ask for a preference.

Do not imply technician dispatch until the service team accepts it.

Field 14: Emergency path

If equipment is down and the provider has an emergency line:

show the phone number immediately.

Keep the web form as backup/supporting context.

Field 15: Photos and videos

Express Carwash Equipment explicitly asks customers to share pictures or videos to speed service.

Useful media can show:

Do not encourage unsafe access to moving or energized equipment.

  • error screen;
  • damaged part;
  • leak;
  • motor/pump;
  • equipment label;
  • overall assembly.

Field 16: Part number

For parts requests:

Shore currently branches its form around parts and installation.

  • part number;
  • equipment brand/model;
  • photo;
  • quantity;
  • installation needed / self-install.

Field 17: Installation project

For new equipment or upgrades, collect separately:

Do not force a new installation through a repair form.

  • existing/new site;
  • wash format;
  • project location;
  • equipment/system need;
  • desired launch;
  • plans/specs if available;
  • budget/project stage at a high level.

Field 18: Notes

Prompt:

Tell us which site and equipment are involved, the current operating status, what problem you see, and whether this is emergency, repair, PM, parts or installation.

What the form should not decide

Do not ask the public form to determine:

Those belong to qualified service review.

  • root cause;
  • electrical diagnosis;
  • PLC logic;
  • part compatibility;
  • PM interval;
  • technician;
  • route;
  • warranty eligibility;
  • final repair price.

Should every request create a work order?

Usually not automatically.

Use:

web request → service review → equipment/site match → accepted job → work order

This prevents spam, duplicates and incomplete machine data from polluting operations.

Confirmation message

Use:

Thanks. We received your car-wash equipment request. Our team will review the site, equipment, operating status, issue, urgency and any photos or part details and contact you about the next step.

Avoid:

A technician is dispatched.

unless dispatch has actually accepted the job.

Collect enough to get the right service team moving without pretending the machine is already diagnosed

A strong request form reduces back-and-forth and keeps operational truth in the field-service system.

Explore OneStudio features, compare plans, or review the turnkey website service.

Questions businesses ask

What fields matter most for an emergency repair request?

Site, equipment type, operating status, issue description, phone and useful photos/video.

Should brand and model be mandatory?

No. They help, but a down site should still be able to submit without them.

Should parts and repair use the same form?

A branched form can work, but parts should collect part/equipment data while service should collect status, issue and urgency.

Does OneStudio dispatch car-wash technicians?

No. OneStudio should remain the public website, enquiry and ordinary CRM layer.