Craft business: qualify website enquiries
A craftsman must make it possible to understand the work offered, the area served and the intervention conditions before requesting photos or an estimate. The site gains in utility when it reduces requests that cannot be processed and helps the customer to describe their need.
These files describe preparation methods. They do not present customer achievements and do not replace the validation of information by the organization concerned.
All sectoral filesInterventions and scope
Distinguish troubleshooting, maintenance and planned construction. One page per service is only useful if it specifies a different problem, the work included and the exclusions. Describe the truly possible movements; A long list of cities proves no local presence. When the cost depends on a diagnosis, explain the necessary information rather than publishing an artificially accurate price.
A form adapted to the construction site
Ask for the type of work, the common and a short description before the technical details. A photo may help, but plan a contactless means without attachment. Indicate accepted formats and information processing. Do not ask for access codes, identity documents or information that is useless for the first exchange.
Understandable evidence
Present a realization with its context, the perimeter executed and the photos whose publication is authorized. Separate your own work from the illustrations. For certification or insurance, check the holder, covered domain and validity before publication. Do not turn a particular qualification into a general promise on all jobs.
The two routes to check
Test a scheduled request and a request that you cannot accept. The visitor must be able to recognize an intervention outside the zone or outside the specialty before completing the form. After sending, confirm receipt and explain the sequel without promising a delay that the team cannot ensure. Check who receives and resumes requests during an absence.
Maintain operational information
Assign a person the schedules, contact details, scope of intervention and seasonal services. Remove abandoned services. Keep a history of important changes to understand an old request. When changing zones, also correct local pages, external sheets and confirmation texts.
Information to gather before writing
- Services with inclusions and exclusions
- Actual area and travel conditions
- Allowed photos and context captions
- Information needed for the first quote
- Responsible for monitoring requests
For each item, keep the source, the person validating it and the language versions concerned. Missing information must become a question to solve, never a value invented to fill the page.
Frequently asked questions
display a fixed price?
only if the service and its conditions are sufficiently defined. Otherwise, describe the cost factors and how to get an estimate.
Create a page for each city?
A page deserves to exist if it brings verified local information. Group the pages that only replace a common name.
Make photos mandatory?
A photo can be useful, but a simple alternative avoids excluding a person who cannot provide a file.
resources to deepen
- Practical guides of the web project
- Understanding Web Terms
- Prepare course checks
- Organize request tracking
Additional reference: W3C Wai: Structure an accessible page. The sectoral recommendations of this sheet are an editorial method; This reference does not certify the information specific to an establishment.