CRM leads sitting four days: the $1,800 estimate nobody followed

A customer received an $1,800 estimate. Four days silent. In the film we use on the automotive page, that stall has a name on it so a shop owner can feel it. The CRM already had the record. GoHighLevel will watch an opportunity sit for as long as you let it. Watching is not following up. Following up is somebody’s job (the office manager, or you) and it loses to the drive every time.

The same board usually has the rest of the pattern. A brake inquiry with no follow-up. A tire lead never contacted. A conversation that died in SMS because the thread was on a personal phone. None of this requires a new CRM. It requires an assignment: when an estimate ages past the window, draft the next step from the file, write it back, and put it in front of a person. Discovering it next Tuesday is not a process. It is a regret.

Why CRMs go quiet in shops

GoHighLevel, Jobber, and the rest are good at capturing. Shops are good at working the car that is here. The opportunity pipeline is a third job nobody was hired to do. Drip campaigns paper over it until the customer gets a “just checking in” on a job they already declined, or worse, on a job they already completed. The Automotive Service Association can teach service drive process. It cannot sit inside your opportunity pipeline at 7 p.m.

The Oldroyd lead-response work is directionally useful here too, even though it was not a shop study: waiting a day to touch a new inquiry is how you donate the job. Four days on a written estimate is a different crime. The customer already has your number, your total, and a growing suspicion you do not want the work. A person should say something that is about their car, not about your cadence.

What the agent actually does

It checks history. It prepares the follow-up under your rules. It writes the attempt back to the CRM. It flags the record if a person still needs to take it. When a job later completes, a review request can go out because that is a different, dumber path (closer to an automation) and it should not depend on the same memory as the $1,800 stall. Completed job. Review request went out. Those can be checkboxes. Untouched estimates cannot.

• Age thresholds you set, not a vendor’s default drip.
• Drafts that quote the estimate, the vehicle, and the last human note.
• A person in the loop until you turn sending on.
• A write-back so the next advisor sees the attempt.
• No second system of record. The CRM that has the lead keeps the lead.

What we saw in the field

At Detail Driven, GoHighLevel held the conversations. Tekmetric held the repair orders. Those are not the same object. A lead that never became an RO is a CRM job. An RO that went quiet is a shop-system job. Mixing them up is how you follow up on a car that is already in a bay, or ignore an estimate that never got a ticket. The operator OS keeps inbox and quotes next to shop views so a person can see both without becoming the integration.

We will not tell you that every four-day-old estimate is worth tens of thousands of dollars. The film says you may discover leftover work in that neighborhood when we walk marketing, sales, the website, and the journey. May. The audit is where the number becomes yours, or does not.

The CRM is watching every open estimate. Nobody is assigned to do anything about it.

Estimates versus repair orders

If the $1,800 lived only in GoHighLevel, it is a CRM follow-up. If it also became a Tekmetric estimate or RO, it is a shop-system follow-up, and the two must not double-text. That mapping is the whole infrastructure article on connecting GHL to Tekmetric. On this page the point is simpler: silence has a clock. Four days is already too long for a written total. Next Tuesday is how you donate the job to whoever called them back first.

If you can picture a name, a total, and a number of days without opening the CRM, you already know the stall. Put it on the audit. We will look at the pipeline, not at a template campaign.