25 WordPress themes for plumbers and heating engineers

Request a repair

The visitor arrives from a service page, selects the reason, enters the postcode, then leaves a callback number and a short description. Display the towns served and opening hours near the button. Validation must check the values received by the server. In the exercise, postcodes 69001, 69002 and 69003 are served and the office responds between 8 a.m. and 6 p.m., Paris time.

Run P01 to P04. At 10 a.m., a fictional request for a leak at 69001 is received by the office. Postcode 13001 produces an out-of-area response. An empty phone number must trigger a message beside the field. At 7 p.m., display the out-of-hours instructions and also test the 8 a.m. and 6 p.m. boundaries. Use “Request received, the team will call you back” once the record is saved successfully. The service visit and its time are agreed afterward.

In Contact Form 7, set the recipient in the Mail tab, the sender on the site’s domain and the useful fields in the message. Check delivery to a test mailbox. Checking the area and hours requires configuration suited to the site.

The diagrams in each entry illustrate a workflow to check. The local dataset reproduces nine fictional repair and maintenance requests. On a WordPress copy, check the hours, the distinction between a preference and an appointment, and the message received.

Book a maintenance appointment

Present the equipment you maintain and ask for the postcode, contact details and a preferred time slot. In the exercise, E1 is November 30, 2026 at 10 a.m. and E2 is December 1 at 2 p.m., Paris time. The heating team can confirm only one appointment per slot. An acknowledgment indicates that the request is pending, then the office confirms a date separately.

Run P05 to P09. Submit ENT-A and ENT-B with E1 as their preference, then confirm ENT-A. Check that a second confirmation for E1 fails and offer E2. Repeat confirmation from two sessions with a clean initial state. Only one confirmation must be recorded and sent. Capacity must be checked when the slot is confirmed.

If you use a calendar, set the duration, resource, capacity and time zone. WooCommerce Bookings, for example, documents a maximum capacity per block. Check how pending requests behave in your tool. To accept several preferences for the same slot, the request queue can come before the final booking.

Publish a service area

Display the towns as text next to the map and explain any differences between maintenance and repairs if the areas differ. Check the postcode from every form, including when arriving directly on a service page.

Decide who answers repair requests and who schedules maintenance

Start by writing down what the team can promise through the site. A repair request receives a tracking number and indicates how the next response will arrive. A maintenance request can suggest a provisional slot. A confirmed appointment means the slot has been reserved in the calendar actually used. For a small team that still coordinates visits by phone, a callback request may be sufficient for both activities.

Separate the two actions on service pages. A visitor looking for a quick visit must be able to find the area, response hours and contact information before opening a form. Someone planning maintenance can take time to choose a date. On the test site, review the wording on the button, summary and reply message. Every screen must explain what will happen next.

• Open a Repair page directly, then a Maintenance page, without going through the home page. Check that contact details and arrangements for the correct service are visible.
• Ask the colleague who receives these messages to restate the promise displayed on the site. Correct any discrepancy before choosing the final template.

Approach 1. Qualify a repair request

In the mockup, the form asks for a reason, postcode and callback method. Use a text field for the postcode and compare it with the list of towns actually served. A larger service area may suit scheduled maintenance if routes allow. Keep the two lists separate in that case. The repair form must explain the next step if the postcode is outside the area, without collecting contact details unnecessarily.

Configure a dedicated test recipient for repairs. In example P01, the leak request is eligible and the team receives the reason. P02 checks the out-of-area case, P03 missing contact details and P04 an out-of-hours submission. If the business accepts messages outside response hours, simply confirm receipt and state the expected response time. If it does not, display the next opening time or the channel designated by the team.

• First try an accepted postcode, then one outside the area. Return to the first postcode and check that the contact field retains its value while the request remains eligible.
• Repeat the form without contact details and at a time when nobody monitors the mailbox. Read the site’s response and check whether there is a notification in the test capture.

Approach 2. Request maintenance with a preferred time slot

For a first site, let visitors choose a date or time slot they prefer. The form can pass this preference to the team maintaining the calendar. Display a response such as Request received. We will confirm the time slot. Cases P05 and P06 in the local dataset illustrate two requests for E1. The tool can receive both as long as the page presents the date as a preference. The team then handles requests in its chosen order.

Prepare the test email with the requested slot, intended service and fictional contact details. Add the request reference to the acknowledgment. During a callback, this reference distinguishes two requests from the same household or company. If a comments field is used to specify access details, make it optional and ask people not to enter a password, gate code or document. Necessary access details can be collected later through the usual channel.

• Submit two E1 preferences from two sessions. Check that both requests appear with separate references and that the response refers to a preference.
• Offer another slot in the test record. Check that the colleague can find the original preference and agreed time without confusion.

Approach 3. Confirm only a slot that is actually reserved

Choose an appointment plugin if the site must confirm availability immediately. On the WordPress copy, create a technician, maintenance duration, E1 slot and travel buffer. Compare the displayed duration with the time reserved in the calendar. The slot must disappear or become unavailable when the planned capacity is reached. A provider can manage several visits in parallel if separate technicians are actually available. Also test absences and travel time.

The P07 then P08 sequence checks that the same slot does not produce two confirmations. In two separate sessions, prepare the same request. Confirm the first, then submit the second. The second visitor must receive actionable information, with another slot or a way to resume booking. Check the recorded appointment list and test mailbox. Only one confirmation must be associated with E1 for the test technician.

• Cancel the confirmed appointment and check when the slot becomes bookable again. Compare the public screen and the team’s calendar.
• Move a maintenance appointment from E1 to E2 and check the message sent, E1’s status and the newly reserved time.

Review messages, hours and the mobile workflow

Check the offset between the WordPress time zone, scheduling plugin and browser. Test with a time close to closing and note the time recorded in the record. If different hours apply on Saturday or during a closure, simulate that date on the copy. The site must show the slot in the business’s time zone when its services cover a local area.

On a phone, start with the button on the detail page, then go through all fields using the keyboard or touch keyboard. Check that focus moves to the invalid field and that the message can be understood without relying on color. After an interruption, check whether a record was created before trying again. Repeat a double click and check the number of requests and acknowledgments. Identify a monitored backup mailbox if the usual recipient is absent.

• Compare the receiving address, reason, postcode and time for a repair. Compare the slot, status and technician for maintenance.
• Repeat submission while zooming in on the page, then when returning from an invalid field. It must remain possible to correct the form without starting over.

Compare the theme and the tools the team will use

On a copy, import only one demo per theme and create the same service pages. Use your photos, service-area text and the two acceptance-test workflows. Check whether the page template depends on a builder, bundled plugin or separately purchased license. A demo displaying a calendar must let you identify the tool that actually records the booking. Calculate the cost of the theme, that tool and inbox maintenance.

Before the final choice, perform a trial builder update and check the two representative requests on the copy. Also check who can change time slots and who can change fields. A person scheduling visits rarely needs to change the site’s presentation. The handover file must specify the inbox address, the cover procedure during an absence and where to find requests that have not yet received a reply.

• Download the fictional cases from the resources and repeat them before connecting the real recipients.
• Have the team approve the service area, callback hours and confirmation wording. Keep two fictional reference requests for future checks.

Compare prices and components

The ThemeForest listings consulted on November 11, 2026 displayed 39 to 89 USD for a standard license and six months of support. The record specifies the age of each indexed copy. Review the cart and the author’s terms, then check the versions of the builder and required plugins on your copy.

The illustrations show workflows to reproduce. Product listings specify what the publisher advertises, and each entry provides a test to check the selected configuration.

Further reading

• Compare mapping and location plugins
• Compare appointment and time slot tools
• Compare form plugins
• Download the nine fictitious cases and checking script