“21-point tune-up” means little unless the page explains the useful categories, reporting, authorization boundaries, and next step when a defect is found. Audit the page as a homeowner preparing for heavy cooling season.
1. Define the inspection and service scope
Group the visit into understandable work: thermostat and operating check, electrical and safety observations, airflow and filter review, accessible coil or drain inspection, temperature or performance readings where appropriate, and a written summary. State what cleaning or adjustment is included.
Test: can a buyer compare two tune-up offers without relying on point counts?
2. Separate maintenance from diagnosis and repair
Explain what happens if the system is not operating, unsafe, inaccessible, or already showing a fault. State whether diagnostic work is separate and confirm that repairs, refrigerant, parts, and deeper cleaning require findings and authorization.
Test: can the visitor tell which outcomes may create a separate quote?
3. Distinguish one-time service from membership
Show a fair route for customers who want a single visit. Compare frequency, included visits, priority service, discounts, renewal, cancellation, transfer, and exclusions only where those terms are current. Link to the full maintenance-plan page for recurring details.
Test: can someone choose one-time service without being forced into a plan?
4. Qualify seasonal and efficiency claims
Use Phoenix heat and dust as relevant context, but do not promise a tune-up will prevent breakdowns, cut bills by a fixed amount, extend equipment life by a set number, or restore performance without evidence from the actual system.
Test: replace “will” with the evidence—does each outcome claim still hold?
5. Make price and eligibility legible
If a price is shown, state the equipment count, system types, geographic limits, appointment window, taxes or fees, coupon deadline, and exclusions. Keep current offer terms consistent with the dedicated specials page and dispatch script.
Test: can dispatch honor the visible offer without adding unstated conditions?
6. Build a scheduling path that sets expectations
Ask for service area, system count or type, operating status, access notes, preferred timing, and contact details only when needed. Provide confirmation, response timing, rescheduling context, and an urgent repair alternative.
Test: book at 320px width, trigger every error, and verify the entered data remains.