A lead isn’t a job until someone follows up

TradeProStack is reader-supported. When you buy through links on this page, we may earn a commission at no extra cost to you. That support does not change our verdict or our recommendation.

A lead follow-up system is the difference between a phone that rings and a calendar that fills. For a 2 to 10 person trade shop, the problem is rarely a shortage of enquiries. The problem is what happens after first contact: a missed call with no reply, an enquiry buried in an inbox, a quote sent and never chased, a finished job with no review request. This pillar sets out the follow-up system a small shop can actually run, what it costs, where it stops, and which option fits which shop. It draws on vendor pricing and product pages checked October 27, 2026, plus TradeProStack’s own Cluster F spokes. It is a docs-based synthesis, not a hands-on trial, and it claims no testing of the platform.

The short version: reply to every missed call and every new enquiry, keep one visible record per lead with a next action and a date, run a short cadence that stops when the customer replies, and ask for a review after the job. A shop that does those four jobs reliably will book more of the leads it already gets, without buying a bigger advertising budget first. The rest of this pillar explains each job, the tool that covers them in one subscription, the manual alternative, and the limits to watch.

Quick Take: what follow-up system fits a small trade shop?

Verdict: for a 2 to 10 person shop whose main leak is front-office follow-up, GoHighLevel Starter at $97 per month (USD, plus usage charges) is the simplest paid starting point, taken month to month after a 14-day trial. It covers the front-office job in one subscription: reply, record, next action, and review request. It does not run dispatch, GPS tracking, or a trade pricebook, so a shop whose main leak is field chaos should fix that first instead. Start on Starter, and only move up when a real constraint forces it, such as a fourth brand or sub-account, or reselling the platform.

Three conditions apply to that recommendation, and all three must hold. First, the shop’s main leak must be front-office follow-up: missed calls, unworked enquiries, and unsent review requests, not field chaos. Second, the shop must be able to name one person who owns replies and the pipeline each working day. Third, the shop must accept a usage-based bill above $97 per month and check the per-unit rates inside the trial before turning on every automation. If any condition fails, the recommendation changes: fix field chaos first, or start with the manual system near the end of this pillar and revisit a paid system when enquiry volume justifies it.

Best for: HVAC, plumbing, electrical, cleaning, and landscaping shops with 2 to 10 people whose leads go cold between first contact and booked job. Not the first fix for: a shop whose crews, routes, and invoices are the mess, or a shop with almost no enquiries yet, where the priority is getting found before getting organised.

Why do good leads go cold in a small shop?

Picture a typical Tuesday. The owner is on a job when a call comes in. The phone rings out. By the time the job finishes, there is a voicemail, two form enquiries, and a Facebook message, all in different places, and none of them has a next action attached. The owner means to call back, then the next job starts, and the lead cools. Nothing dramatic happened. No one refused the job. The lead simply never got a reply, a record, or a next step, and by the time someone follows up, the customer has booked someone else. That gap, between first contact and booked job, is where small shops lose work they already paid to attract.

Three habits create the gap. First, no automatic reply: a missed call gets silence instead of a text. Second, no single record: the lead lives in a voicemail, a personal inbox, and a notebook at the same time, so nobody can see the full list of open leads. Third, no next action: even a lead that was contacted once has no dated follow-up, so it drifts until it is forgotten. A follow-up system exists to close all three gaps at once, and it does not need to be complicated to do it. If the system needs more attention than the shop can give it, the shop will stop using it, and the gap will reopen.

Before buying anything, it helps to size the leak. TradeProStack’s missed-call cost calculator lets a shop estimate what unanswered calls are worth in its own numbers. The tool is an editorial framing aid only. It does not prove revenue recovery, and no figure from it should be treated as money already lost or money a system will recover.

What does a lead follow-up system have to do, at minimum?

A workable system has four jobs, and a shop should judge any tool or manual process against all four before anything else.

• Reply fast. Every missed call and every new enquiry gets an automatic, useful reply, with a booking link where one fits, even after hours.
• Keep one record. Every lead has one visible record: name, source, what they need, status, next action, and next action date. One record, not three inboxes.
• Keep a next action. No lead sits without a dated next step. When the step is done, the next one is set before the record is closed.
• Close the loop. After the job, the shop asks for a review while the work is still fresh, and records the outcome so the loop is visible.

Anything beyond those four jobs is optional at the start. Extra channels, extra automations, and extra reports can wait until the four jobs run without fail for a few weeks. Shops that buy the biggest system first often end up running none of the four jobs well, because setup and daily upkeep swallow the time that should have gone to replies.

What should happen in the first hour after a lead arrives?

Speed matters most in the first hour, and the first hour is mostly about two replies: the missed-call text-back and the new-enquiry reply. When a call goes unanswered, GoHighLevel’s Missed Call Text Back automatically sends a text message with the business booking link, so the caller can book and the appointment lands on the HighLevel calendar, including after hours. That description comes from the vendor’s own missed-call text-back post. The feature is listed platform-wide on the vendor homepage, not as a per-plan statement, so this pillar does not claim a specific plan includes it. Readers should check the plan detail on the vendor page before buying on that basis.

A new enquiry deserves the same treatment: an immediate acknowledgement, a short statement of what happens next, and a booking link or a clear question that moves the job forward. A booking link does more work than a message that only says someone will call back, because it lets the customer act while interest is high. The vendor’s feature list, again platform-wide rather than per-plan, includes calendars, appointment reminders, and a consolidated conversation stream across SMS, Messenger, Instagram DM, WhatsApp, and live chat, which is what makes one reply record possible instead of five separate threads.

Video: HighLevel’s missed-call text-back overview (gohighlevel.com). No autoplay.

Two cautions belong in this section, not in fine print. First, the built-in text-back can fire on every missed call, including repeat calls from the same number in a short window. Duplicate control needs a workflow with Wait steps or tag filters, so a repeat caller does not get the same message twice in quick succession. Second, a menu path for turning the feature on has changed before across vendor pages and prior TradeProStack spokes, so this pillar deliberately does not print a step-by-step menu path as current. Use the feature and the toggle concept, and check the vendor’s current help pages at setup time.

For wording that gets a reply, see our missed-call text-back templates, which sets out five templates with timing and opt-out rules, and our full GoHighLevel review for the platform verdict and feature sections.

What cadence can a 2-person shop actually run?

A cadence is a short, planned sequence of follow-ups, and the one this pillar recommends is TradeProStack’s own editorial method, not a vendor schedule and not a vendor benchmark. It is the 5-touch, 7-day cadence set out in our Facebook follow-up playbook: five touches across seven days, each with a different purpose, so the shop is persistent without repeating the same message five times. The touches move from acknowledgement and booking help, through a useful question or a short piece of relevant information, to a final check-in that leaves the door open. The full sequence lives on the spoke, and the pillar does not reprint it here, because the spoke owns that detail.

Three rules keep the cadence workable for a two-person shop. First, the cadence stops when the customer replies, books, or opts out. A sequence that keeps messaging a booked customer is not follow-up, it is noise. Second, every touch has an owner and a date, so a touch is never skipped because nobody knew it was due. Third, the cadence is short on purpose. A longer sequence looks thorough on paper and collapses in practice, because nobody in a small shop has time to run twelve touches per lead while also doing the work.

Consent is the other rule, and it is not optional. A Facebook message is not SMS consent, and an incoming call is not email consent. A shop must only message a customer on a channel the customer has agreed to, and must honour opt-outs immediately. The cadence assumes consent on each channel it uses. If consent is unclear, the shop should ask on a channel it is entitled to use, or drop that channel for that lead.

The cadence and pipeline detail is set out in full in our Facebook lead follow-up playbook for a 2-person shop, which this pillar links to rather than duplicates.

How do pipelines keep leads from slipping?

A pipeline is a visible list of stages a lead moves through, from new enquiry to booked job or lost lead, with a next action at each stage. The vendor’s Opportunities pipelines use owner-defined stages, with Won and Lost created automatically, Kanban and List views, and the ability for a pipeline stage change to trigger a task. That description is carried from prior TradeProStack spokes citing vendor docs from October 16 to 17, 2026, and stage names in this pillar are editorial examples, not vendor-prescribed trade pipelines. A shop should define stages that match its own sales steps, such as new, contacted, quoted, booked, and done, rather than copying a generic template that does not match how it sells.

The value of a pipeline is not the board itself. It is the weekly review the board makes possible. Once a week, the owner of replies looks at every open lead, checks that each one has a next action and a date, and chases the ones that have stalled. Without that review, a pipeline becomes a list of names nobody looks at, which is no better than an inbox. With it, the shop can see at a glance where leads stall: too few replies, quotes that never get chased, or bookings that never get confirmed.

An HVAC example of an estimate pipeline is set out in our GoHighLevel fit check for a small HVAC shop, and the pipeline section of our Facebook lead follow-up playbook shows the same idea applied to a two-person shop.

What does a lead follow-up system cost, and what sits on top of the subscription?

GoHighLevel pricing, checked live on the vendor pricing page on October 27, 2026, is monthly or annual, in USD, with usage charges on top of the subscription. The monthly prices are Starter $97, Unlimited $297, and Agency Pro $497. The annual prices, confirmed live on the same October 27, 2026 check, are Starter $970 per year, Unlimited $2,970 per year, and Agency Pro $4,970 per year, shown on the pricing page as $970, $2970, and $4970 per year. Each annual figure equals ten months at the monthly rate. Annual pricing is therefore printed here with the October 27, 2026 confirmation date.

Across all plans, the vendor states unlimited contacts and unlimited users. Starter is limited to 3 sub-accounts, while Unlimited and Agency Pro allow unlimited sub-accounts. Every plan includes a 14-day free trial with full access to the features of the chosen tier, and there is no long-term contract: the vendor states month-to-month billing, with upgrade, downgrade, or cancellation from the dashboard at any time, and a mid-month upgrade charged only the prorated difference.

What sits on top of the subscription matters as much as the subscription itself. Usage-based costs apply for telecommunications and AI services: phone numbers, SMS, emails sent, and premium AI usage. The vendor describes these as industry-standard rather than hidden fees, but no per-unit rate appears on the public pricing page, so this pillar states no per-text, per-minute, per-email, or per-number rate. A shop should confirm the per-unit rates inside the platform or trial before budgeting messaging volume. On Unlimited and Pro, usage costs can be rebilled to clients, but the vendor pages differ on markup wording, with the homepage card saying no markup and the pricing FAQ referring to adding a markup, so confirm the current rebill terms before relying on a markup.

Two further pricing cautions. First, all prices are USD, and no Canada-specific pricing was found on the vendor pages checked. Second, AI features such as Conversation AI and Reviews AI have pricing and plan inclusion that were not established in the evidence reviewed, so this pillar does not price them or claim they are included on Starter. Where AI is mentioned, treat availability and pricing as usage-based or add-on, and confirm them in the trial.

The full breakdown, including the overpay-per-tier analysis, is on our GoHighLevel pricing page. The pricing section of this pillar is a summary of that spoke plus the October 27, 2026 live check, not a replacement for it.

Where does GoHighLevel stop, and what should you buy instead for field work?

GoHighLevel covers the front office: replies, records, pipelines, workflows, calendars, reminders, reputation management, automated review requests, lead scoring, estimates and proposals, invoicing, and a mobile app, as listed platform-wide on the vendor homepage. It does not claim native technician dispatch, GPS tracking, route optimization, or a trade flat-rate pricebook in the evidence reviewed. A shop that buys it expecting a field operations system will be disappointed, and that disappointment is avoidable if the boundary is stated plainly before purchase.

For shops whose dominant problem is scheduling, dispatch, and invoicing, the field tools are the first buy, with a follow-up system second. Jobber and Housecall Pro are linked here as plain vendor links only, pending programs, never as affiliate links in this pillar. Jobber is at jobber.com and Housecall Pro is at housecallpro.com. Their follow-up depth is a different question from their field strength, and it is covered on their own pages, not settled here.

The full front-office versus field comparison, including the buy-first decision, is on our GoHighLevel versus Jobber versus Housecall Pro comparison, and the field gaps for a small HVAC shop are set out in our GoHighLevel HVAC fit check.

Setup is the other boundary. Pipelines, stages, workflows, triggers, and review-request timing are configured by the shop. GoHighLevel does not ship a ready-made trade follow-up playbook in the evidence reviewed, so a shop should budget setup time, not just subscription money. One inbox also does not equal one person answering: automation still needs someone owning replies, opt-outs, and escalations every working day.

Which shop should choose which option?

The chooser follows the shop’s real constraint, not the size of the feature list.

• One brand, one crew, front-office leak: GoHighLevel Starter, month to month after the 14-day trial, if all three conditions in the Quick Take hold.
• Multiple brands or client accounts: Unlimited, because Starter’s 3 sub-account limit will bind first, and unlimited sub-accounts remove that constraint.
• Reselling the platform: Agency Pro only, because SaaS Mode, which lets an agency sell subscriptions from its own website, set its own price, with automatic account creation and rebilling, is the Pro plan’s job. No other plan in this pillar is presented as a reselling option.
• Field chaos dominant: a field tool first, follow-up system second. Buying follow-up software will not fix missed routes, unassigned jobs, or invoicing delays.
• No tool at all yet, low enquiry volume: the manual system below, revisited when volume justifies a paid system.

That recommendation is the pillar’s verdict, linked here as in the Quick Take: GoHighLevel Starter, month to month after the 14-day trial, for a shop that meets all three conditions. If a condition fails, the chooser above, not the verdict, is the answer.

What if you are not ready to pay $97 per month?

A manual system the shop already owns is a genuine alternative, not a throwaway. Use one shared sheet or notebook with one row per lead: name, source, what they need, status, next action, and next action date. Name one owner per day. Apply a same-day reply rule. Review every open row once a week. Cost: staff time only. That system will run the four jobs in this pillar, slowly and by hand, for as long as enquiry volume stays low and the owner is not on jobs all day.

Its limit is plain, and it is the reason a paid system eventually earns its keep. The manual system breaks when enquiry volume rises or when the owner is on jobs all day, which is exactly when an automatic text-back earns its keep, because the reply happens whether or not anyone is free to pick up the phone. A shop should start manual without embarrassment, and move to a paid system when missed replies, not software enthusiasm, make the case. The trigger to revisit is simple: open rows that keep missing their next action date, week after week.

A short aside for shops evaluating software at a trade show: the questions worth asking on a show floor, including how a vendor handles follow-up, are set out in our event-context piece, PHCC CONNECT 2026 software questions. It is context for evaluation, not a core spoke of this pillar.

How do you close the loop with a review request?

A review request belongs after the job, while the work is still fresh, and it belongs in the follow-up system rather than in someone’s memory. The vendor’s platform-wide feature list includes reputation management and automated review requests, which is what lets the request go out as part of the workflow instead of as a favour the owner remembers to ask for at the end of a long day. The request itself should be short, specific to the job just done, and easy to act on, with one link and no extra steps.

TradeProStack’s review-request script generator helps a shop draft that short request in its own words. Like the missed-call calculator, it is an editorial aid, not evidence about review outcomes, and it does not change the rule that the request must be genuine, unsolicited in the sense of not being bought, and sent to real customers after real jobs.

What to confirm in the trial before you pay

A 14-day trial is long enough to test the four jobs, if the shop tests them deliberately. Before paying, confirm each item below, and do not turn on every automation until the answers are in.

• Per-unit usage rates inside the platform: what a text, a call, an email, and a phone number actually cost at the shop’s expected volume.
• Text-back duplicate behaviour on repeat calls: whether a second missed call from the same number in a short window triggers a second message, and which workflow setting prevents it.
• Canadian messaging rules: US texting registration rules do not automatically apply in Canada, so check Canadian carrier and consent requirements before turning on automated texts.
• Whether the pipeline and cadence fit the shop’s real enquiry volume: a system that works for five leads a week may not work for fifty, and the trial should use real volume, not a demo list.
• Who owns replies, opt-outs, and escalations each working day, by name, not by role alone.

If any answer is missing at the end of the trial, that is a reason to extend the test or to start with the manual system, not a reason to pay and hope the answer appears later.

Cluster map: every Cluster F spoke, in one place

This pillar synthesises the live Cluster F spokes. Detail stays on the spoke, and each link below goes to the page that owns that question.

• GoHighLevel review: CRM, follow-up, and missed-call text-back for small trade businesses (full platform review).
• GoHighLevel pricing: 3 plans plus usage fees (full pricing and usage breakdown).
• Missed-call text-back templates: 5 templates that get a reply (text-back wording, timing, and opt-out rules).
• Facebook lead follow-up: 5-touch cadence over 7 days for a 2-person shop (cadence and pipeline playbook).
• Is GoHighLevel enough on its own for a small HVAC shop? (front-office fit check and field gaps).
• GoHighLevel versus Jobber versus Housecall Pro (front office versus field operations, buy-first decision).
• PHCC CONNECT 2026 software questions (trade-show evaluation context).
• Missed-call cost calculator (size the leak before buying).
• Review-request script generator (draft the post-job request).

No GoHighLevel deal page exists, so this pillar links none. Forcing an unrelated deal into a follow-up pillar would break its intent, and the pillar is complete without one.

The bottom line

For a 2 to 10 person shop whose leads go cold, the system that pays first is the simplest one the shop will actually run: an automatic reply to every missed call and new enquiry, one visible pipeline with a next action on every lead, a short cadence that stops when the customer replies, and a review request after the job. GoHighLevel Starter at $97 per month, month to month after a 14-day trial, covers that front-office job in one subscription, with usage charges on top and per-unit rates to confirm in the trial. It does not run dispatch, GPS tracking, or a trade pricebook. Start on Starter, name the person who owns replies, check the usage rates, and only move up when a real constraint forces it. That is the whole system, and it is enough to start.