Créez un site web pour plombier ou électricien qui aide les clients à vous joindre

Build a mobile-first website for my [PLUMBING OR ELECTRICAL] business. Make it useful on the first visit: customers should quickly see what we do, where we go and whether to call or request service. Build a polished first version, then report what still needs my facts, setup or testing. Do not invent a business, credentials, jobs or customer proof to fill gaps.

MY BUSINESS — REPLACE THE BRACKETS WITH REAL DETAILS
- Public business name and legal name if different: [DETAILS]
- Trade: [PLUMBING / ELECTRICAL / BOTH, ONLY IF WE ACTUALLY OFFER BOTH]
- Country, state/province, city, website language, currency and time zone: [DETAILS]
- Exact area served: [CITIES, NEIGHBOURHOODS OR POSTCODES WE ACTUALLY VISIT]
- Services we perform: [PLAIN-LANGUAGE LIST, GROUPED BY TRADE IF BOTH]
- Phone, business email and actual customer-facing hours: [DETAILS]
- After-hours or emergency availability: [EXACT POLICY / NONE]
- Contact response expectation: [REAL COMMITMENT / NONE]
- Callout, diagnostic or estimate fees, and any prices we approve for display: [EXACT TERMS / OMIT]
- Verified licences, registrations, insurance and the work each credential covers: [EXACT APPROVED FACTS / OMIT]
- Who we are and how a request becomes an assessment or job: [REAL FACTS]
- Existing field-service system or request-form link: [PROVIDER AND APPROVED URL / NONE]
- Privacy notice and contact for requests/photos: [REVIEWED TEXT AND LINK / DRAFT NEEDED]
- Brand colours, wordmark and style: [DETAILS / USE DEFAULT BELOW]
- Photos I own or have permission to use, with intended placements: [FILES / NONE]

FIRST-BUILD SCOPE AND DESIGN
Create Home, Services, Service Area, About and Contact / Request Service. This first version is a public website and request route, not a dispatch board, instant quote engine, confirmed calendar, payment checkout or client portal. Use one trade throughout unless I supplied real services and credentials for both.

Use a confident, practical visual style: clear type, generous spacing, one strong accent and useful imagery rather than stock-looking badges. If I supply no brand direction, use warm off-white, deep navy or charcoal, and one restrained copper or blue accent. Use my approved photos where supplied. You may make a neutral illustration or atmospheric close-up of tools or materials, but do not depict invented completed jobs, team members, branded vehicles, premises, licences or reviews as mine. Do not leave empty image frames. At 320px, keep all headings, navigation, request fields and actions visible with no horizontal scrolling.

PUBLIC PAGES
Home: state the selected trade, actual area, key services and real hours. Give two clear actions: “Call [PHONE]” and “Request service.” On phones, keep both easy to reach without covering the content. Say “emergency” or “24/7” only if the supplied availability truly supports it.
Services: explain only the supplied work in plain language, with a short description of when someone should contact us. Do not invent specialisms, brands, guarantees, response times, prices, DIY electrical instructions or diagnostic claims.
Service Area: list the real places covered and explain any boundary or travel-fee policy I supplied. A visitor should be able to tell whether to ask about their address. Do not expose a residential or private home address as a public storefront. Do not generate near-identical pages for every town; add a separate location page only if I later supply genuinely distinct, useful local details.
About: use my actual people, story, credentials and real media only. Omit unprovided licences, insurance badges, awards, review scores and job counts. If I supply verified credentials, show their exact type, number and scope rather than a generic “licensed” icon.
Contact / Request Service: show actual contact methods, hours, area and the request route. An urgent visitor should see the phone route immediately; the form is for requests that staff will review. If there is an immediate hazard, direct visitors to the appropriate local emergency or utility service without inventing a number or giving repair instructions.

REQUEST FLOW
If I supplied an approved Jobber, Housecall Pro or other field-service request link, use that supported form as the request destination and do not create a duplicate inbox. Otherwise build a short native form with name, exactly one contact method (phone or email), area/postcode, service category from my list, an optional brief description and optional preferred contact window. Ask for a full address only later, when staff need it. Never ask for payment-card details.

An optional problem photo is useful only if this builder can store it privately, restrict it to authorised staff and show the actual data handling in the privacy draft; otherwise omit the photo field for now. Do not imply a photo guarantees a price or faster response. Validate the form on the client and server, apply basic spam and duplicate protection, and save one valid request as Pending before showing success. Say “Request received; we will review it,” not “appointment confirmed” or “quote ready.” Use a response-time promise only if I supplied one.

Create a protected owner view for native requests. Only authorised owner/admin accounts may read or change requests or uploaded photos; enforce this on the server, not only by hiding a link. Show Pending, Contacted and Closed plus timestamps. Keep the owner interface in English. If a supported email/SMS provider, sender, destination and required plan/domain are configured, send a minimal alert. Saving and alert delivery are separate statuses; if an alert fails, the request remains saved and the owner sees the failure. Do not claim an alert was delivered unless tested.

TRUST, PRIVACY AND FINDABILITY
Display only supplied prices, fees, availability, reviews, guarantees, qualifications and insurance facts. Hide missing proof sections. Do not generate reviews, before/after jobs, logos of organisations or licence numbers. A service request is not a diagnosis, agreed price or confirmed visit. Show the actual steps by which this business reviews the request and gives any estimate or contract. Generate a privacy draft that reflects the form, optional photo, storage, alerts, providers and retention; mark it for owner review before using the site with real customers. Do not add marketing opt-ins or tracking pixels by default.

Give each public page a useful title, description and canonical based on actual facts. Add business structured data only from verified name, phone, area, hours and services. Do not promise search rankings. Use descriptive links, labelled fields, clear errors, keyboard access, visible focus and good contrast.

HANDOFF AND TESTS
Check all five pages at 320px and desktop size. Test tap-to-call with the correct international phone format, every navigation link, area/hours copy and the actual request destination. For a native form, exercise valid, invalid and duplicate sample requests, confirm one Pending record before success and separate saved/alert states. Test signed-out, authorised-owner and unrelated signed-in access to the owner view. Verify optional uploads are private. If you cannot run a check, mark it UNTESTED instead of claiming success. List every missing business fact, privacy review, provider/domain/plan setup and real image that I should supply before launch.