A heating and cooling website that helps customers choose

Start with the customer’s decision

An attractive homepage can still leave someone unsure whether to call. They need a repair, but the page talks about installations. They live nearby, but cannot find the service area. The form asks for a long message without saying what helps.

Before discussing a new layout, answer four questions: do you handle this job, do you cover the property, what evidence helps someone trust you, and what happens after contact?

Use this checklist to brief a supplier or review your current site. The recommendations are design and process advice, not a measured conversion study.

Separate repair, installation and maintenance

A repair customer wants to know whether you handle the problem and how to reach you. An installation customer may be comparing options and needs to understand the estimate process. Maintenance can involve a planned visit or an ongoing agreement.

Give each real service a clear route. In the US, HVAC is familiar language. In Australia, air conditioning and heating often describe the work more directly. Use the words your customers use, and have the contractor approve equipment and technical claims.

A website enquiry does not confirm a booking or establish emergency dispatch. Say what the team can genuinely provide.

Make coverage and proof specific

“Serving the local area” only helps if the customer knows what local means. Name the actual coverage. If the team travels farther for installations than repair callouts, explain that distinction.

Show real work photographs, approved customer comments and verified credentials. A project caption can explain the type of work without exposing a customer’s private details. Check permission before publishing.

A licensed interior photograph can illustrate a design idea. It does not prove your team installed the system. Keep sample imagery separate from real projects, and never replace missing evidence with an invented rating or client count.

Ask what helps the team respond

The first form starts a conversation. It should not ask for every detail required for an engineering quotation.

• A name and a working contact route.
• The service requested, with a useful “not sure” choice when needed.
• Enough location detail to check coverage.
• A short description of the work or problem.

Explain why any additional field matters. Uploads, several mandatory contact methods and long questionnaires add handling work; include them only when the process needs them.

Every field needs a label. An error should explain what to correct. After a recoverable delivery failure, keep the customer’s message and provide a usable alternative. The confirmation must say what actually happened, rather than imply a booked visit.

Check the receiving side

Identify the person or team responsible for the request before launch. Confirm where the record goes, what action follows and what happens if delivery fails.

A small business may only need a dependable inbox and a named person. If field-service software already offers a suitable request form, check it before paying for another connection. Jobber, for example, supports requests that can progress to assessment, quotation or a job. Features and account access need confirming for the actual setup. Jobber request documentation.

Our Still Air demonstration shows a sample request, team assignment, reply and next action. It is a fictional example running in the browser, with no live customer or CRM connection.

Run one complete test on a phone

Ask someone unfamiliar with the website to find a service and make a labelled test enquiry. Give them a task, such as asking about an installation in an area you genuinely cover, rather than telling them which button to tap.

1. Find the service and coverage without returning repeatedly to the homepage.
2. Open the menu and contact route on a narrow screen.
3. Complete the form, then check an invalid field and a failed submission.
4. Inspect the receiving inbox or system. Confirm the details and responsible person.
5. Check keyboard access, readable text and the page when images fail.

A design sign-off and a successful enquiry test are separate pieces of evidence. Agree both with the supplier before launch. If you are changing search URLs, discuss redirects and measurement before replacing the old pages.

Bring a useful brief

Bring the real service list, coverage, approved images and credentials, response arrangements and tools the team already uses. Identify one customer decision the current website handles poorly.

The right recommendation may be a clearer service page or a form change. A rebuild is useful when the larger structure or design needs work, rather than simply because a supplier sells websites.

See the website design offer, or read how to organise installation quote follow-up.