RReshape.
← All articles

Standardizing Lead Forms by Service Category: A Landscaper's GoHighLevel Foundation

By Alex Regueiro · October 25, 2026 · 5 min read

A landscaping company could not see its leads in one place. Facebook leads were tracked in a separate Google Sheets spreadsheet outside the CRM, and the website and Facebook forms had not been standardized, so tracking and dashboards could not be central.

The call was a systems and build review with the company's owner and operations lead. If you run one of the many home service businesses that takes leads through several channels, this is how we reset the foundation around the service itself.

The situation

Leads reached the company through website forms, Facebook lead forms and phone calls. The Facebook leads were tracked in a Google Sheets spreadsheet that sat outside GoHighLevel, so tracking and dashboards were not central.

Two other blockers came up. Phone routing could not be finished until a third GoHighLevel number was in place. And the job-costing software has no automation trigger that sends a won deal back to the CRM, so the end of the pipeline needed another route.

What was broken

Four gaps showed up in the review.

  • Facebook leads lived in a Google Sheets spreadsheet, outside the CRM, so reports could not include them.
  • The website forms and the Facebook forms were not standardized around the same set of services.
  • Phone routing was waiting on a number, so the call path could not go live.
  • The job software had no trigger to report won deals back to GoHighLevel.

What we built

We started with the part that everything else depends on, which is what a lead is asking for.

  • Five service categories: the website forms and the Facebook forms were standardized around the same five categories, and all forms were set to be updated within days.
  • A call-routing order: we built a new phone menu with three routing destinations and staged it for testing, ready to go live when the third number is in place.
  • Pipeline structure: we set the stages that a lead moves through in the CRM.
  • One lead source: the Facebook leads spreadsheet was imported into GoHighLevel, so those contacts sit in the same system as everything else.
  • Payment signals: we checked the options for payment notifications through the job software and the accounting software, since the job software cannot trigger one on its own.
  • Content: four video script outlines were sent for review.

What changed

Lead volume and response time were not reported, because the call ended with the build in progress. What changed is that a lead now means the same thing wherever it enters. Before, Facebook leads sat in a spreadsheet outside the CRM. After, the forms share five service categories, and the spreadsheet contacts live in the CRM.

The phone menu was staged for testing and not yet live, and the payment signal was still being worked out.

Build your forms around services, not channels

This section is advice for your own business. List the services you actually sell and pick a short set of categories that covers them. Then make every form, on every channel, ask the customer to choose from that same set. A lead from your website and a lead from Facebook should land in your CRM looking the same.

If you track any lead source outside the CRM, import it first. Dashboards built on partial data teach the wrong lesson.

Frequently asked questions

Why standardize lead forms around service categories?

Forms built channel by channel produce leads that look different, and reports cannot add them up. Using the same service categories on every form means a lead from the website and a lead from Facebook can be counted, routed and tracked together.

What should I do with leads tracked in a spreadsheet?

Import them into the CRM so every contact lives in one system. On this build, the Facebook leads spreadsheet was imported into GoHighLevel so tracking and dashboards could start from a single source.

How many routing destinations should a phone menu have?

Only as many as you have real destinations. The menu we staged had three routing destinations and was built to be tested before it goes live.

What if my job software cannot send won deals back to the CRM?

Look for another signal, such as a payment notification from the software or from your accounting tool. In this build we checked those options because the job software had no automation trigger for it.

If your leads arrive through several channels and never line up, book a 30-minute AI follow-up and reporting audit. We look at your forms and your pipeline and show you where one structure would replace many.