Start with what you see.
We’ll route the service.
You do not need to diagnose the computer or choose the perfect service name. Tell us who you are, what the device is doing, whether important data is involved, and how you would prefer the service to happen.
Three rules make the intake safer and more useful.
The form should collect service context—not sensitive secrets or a guessed diagnosis.
Tell us what the computer actually does.
“Shuts off after ten minutes” is more useful than guessing that the power supply is bad.
Say whether files matter and whether a backup exists.
That changes how aggressively the device should be tested, copied, repaired, or referred.
Do not submit passwords or recovery information.
No account passwords, recovery codes, Social Security numbers, authentication codes, or payment details belong in ordinary intake.
One form, grouped by the decisions that actually matter.
This prototype shows the intended presentation. The production deployment must preserve the existing live form implementation and submission behavior.
The form should collect context, not credentials.
If a repair genuinely requires access later, that should be arranged for the defined service—not entered into ordinary intake.
Your selection is a preference, not an automatic appointment.
The current live form offers four methods. The request should keep all four until Circuit Craftworks deliberately changes the operating policy.
Drop-off by appointment
Best fit for diagnostics, repair, upgrades, operating-system work, data service, assembly, and extended testing.
Pickup and delivery
This remains selectable on the current live form. Availability, address, timing, and applicable terms should be confirmed before treating it as scheduled.
On-site visit
Useful when the customer’s environment is part of the work, rather than merely a convenience preference.
Remote support
Appropriate when the computer starts, connects reliably, and the problem does not require physical access.
The request starts the workflow. It does not authorize everything that comes after it.
The current live page already has the right approval principle; this redesign makes the sequence easier to understand.
Your description and device details are reviewed.
The likely service and method are identified.
Drop-off, pickup, on-site, or remote details are agreed.
The defined starting service is performed.
Findings and written estimate are reviewed before additional work.
You do not have to guess your way through the request.
Use the Help Center for pricing, data, credential, appointment, and service-boundary questions. Use Services if you want to understand the available paths first.