Separate new work from concerns about a recent visit.
Add a recent-service help block beside your normal service request.
Label it for problems reported after your company’s recent work.
Customer status alone doesn’t tell your office what someone needs.
An existing customer might simply want an unrelated service.
Another person might report that the same cooling problem returned.
Neither situation tells you whether earlier work caused today’s concern.
Keep your service-page contact section available for new work.
Give recent-service concerns a separate, monitored route for office review.
Your office decides whether concerns relate to earlier work.
Staff confirm coverage, charges, and whether another visit is needed.
Customers shouldn’t need a job reference or coverage decision first.
Show the route without inventing a support promise.
This fictional sample does not represent any actual contractor’s capabilities.
Replace every bracketed instruction with your company’s checked process.
Fictional sample component
Report a problem after our recent visit.
Call [verified office phone] about your concern.
Tell us what happened after our visit.
An approximate date helps, if you know.
A job reference is optional, not required.
Unsure customers can use this same route.
For unrelated work, use [normal service request].
For urgent concerns, use [verified urgent route].
Place the normal service action alongside this smaller help block.
Keep verified urgent-contact and safety guidance accessible independently, too.
Never send immediate safety concerns into an asynchronous problem form.
Give the office context without deciding coverage.
Assign an office owner before making this route public.
Use a form only when its destination preserves the distinction.
Otherwise, a verified office phone route can carry the request.
Collect contact details and a short description through that route.
Pass the reported concern privately, with optional date and reference.
Don’t require invoice uploads, payment details, diagnostics, or customer logins.
A fictional handoff records: "Cooling problem returned; visit date unknown."
Mark it for service review, with the customer’s contact details.
Keep its relationship to earlier work pending office review.
Acknowledge receipt only, not an appointment, coverage, or free work.
Explain warranty support separately, without promising eligibility during intake.
Test three situations with your office.
Use these fictional cases to test the sample’s matching routes.
- An existing customer requests unrelated work. Use the normal service request. Confirm the office treats it as new work, not a callback.
- A customer reports a problem after recent work. Use the recent-service office route. Preserve the concern and optional job context privately. Confirm receipt without booking a visit or approving coverage.
- A customer is unsure or lacks a job reference. Use the same office-review fallback. Confirm missing details don’t block contact or force eligibility decisions.
Check that each request reaches its assigned office owner.
Don’t count unresolved recent-service concerns as new estimate leads.
HVAC contractors need websites organized around calls and estimate requests.
Check availability of HGM website services in your market.

Founder of HVAC Growth Machine