A car waiting for a yes costs you twice

A car on a lift with unapproved work holds a bay that another paying job could use. Meanwhile your advisor leaves a voicemail, waits, and calls again between everything else the counter needs.

Start with the bay. Suppose six estimates a day each wait two hours longer than they need to, which is twelve bay-hours a day. If a third of those hours could have been billed at $100 an hour, that is four hours, or $400 a day. Across a five-day week, it comes to $2,000.

Now the advisor. Say each approval takes three calls of five minutes, and ten cars need one that day. That is 150 minutes of phone chasing, two and a half hours of a working day. If a text handles two of every three approvals without a call, the advisor gets back 100 minutes.

These are example figures, so swap in your own labor rate and your own count of estimates. Be skeptical about the filled-hours share, because not every freed hour finds work. The shape still holds: slow answers cost capacity, and capacity is what a repair shop sells.

This guide covers the text-to-approve flow from the advisor's side. It shows what the customer receives, which approvals still need a call, how to handle silence and how to measure the result. It assumes your shop writes estimates in a shop management system and your techs run a multi-point inspection.

What the customer sees on their phone

Picture the customer at work when the shop's text arrives. It names the shop and the car. It links to a page with each recommended line: a photo from the multi-point inspection, one plain sentence and a price.

The customer taps approve or decline on each line, and the total updates as they choose. A third choice, call me, sends a question straight to the advisor. The page needs no app and no login. It cannot change a price or add work, so anything new goes back to the advisor.

The first text might read like this: Hi, this is the service desk. Your estimate is ready, with photos from the inspection. Tap to review each item and approve what you want done. Reply here with any questions.

From inspection to a car back on the lift, the steps run like this. Each step has one owner.

  1. The tech finishes the multi-point inspection and attaches a photo to each finding.
  2. The advisor prices the work, edits the lines and approves the estimate to send.
  3. The system texts the customer a link to the estimate, with photos and plain explanations.
  4. The customer approves, declines or asks to talk, line by line.
  5. Each decision writes to the repair order with a time stamp, and approved lines move to ready-to-work.
  6. The tech and the parts counter are notified, and the bay keeps turning.

Advisors get a notice when a customer opens the page, when they decide and when they ask to talk. A call me tap puts that customer at the top of the advisor's list with the estimate already open.

The advisor's judgment sits at step two and the customer's decision sits at step four. Everything between them is carrying and recording. Once the work is approved, status updates can keep the customer informed through pickup.

Declined lines do not vanish. They flow into the follow-up queue with their reason attached, which is where declined work follow-up picks up. If the customer calls the shop, a voice assistant on the line can find the open estimate and answer simple questions. It hands the call to an advisor with the estimate on screen.

Compare the ways shops get approvals

Shops already use more than one method, and texting does not replace the phone. It changes which approvals need a call at all.

How approval methods compare
MethodWorks well whenFalls short when
Advisor phone callThe job is large or sensitive, or needs explaining in conversationThe customer is at work and the call goes to voicemail
Text with a link to photos and line itemsThe findings are routine and a photo makes the caseThe customer has questions the page cannot answer
Email with a PDF estimateThe customer wants a document to keep or forwardThe email sits unread and nobody sees the photos
Approval at drop-off or pickupThe customer is already standing at the counterThe car needs more work than the first estimate showed

A sensible split uses the text for routine findings and the call for large or safety-related ones. The counter works when the customer is already there. The automation chooses the route from rules you set, and an advisor can override it at any point.

Line-by-line approval fixes a quiet problem. A phone call can end with one answer for the whole estimate, while the customer may want the brakes today and the rest later. Capturing that partial yes means the brakes start now and the rest is re-quoted on a schedule.

Email deserves a note. A PDF is a fine record, but photos inside an attachment are easy to miss. If a customer prefers email, send the same link to the same page.

Some cars have two people in the picture: the driver who dropped it off and the person who pays. Store the authorized approver on the account, and send the text to that number. If the approver is someone else, the advisor sets it once at check-in.

Some customers cannot or will not use the page. The advisor reads the line items over the phone and records the answer on the same repair order. The page is the default path, and the phone stays open for anyone who needs it.

Decide who approves what before anything sends

Approvals are consequential, so the rules come first. The system never invents a price, a promise date or a discount. It sends what the advisor approved and records what the customer chose.

  • The advisor approves every estimate before it sends, at least at the start.
  • Any added cost after approval needs a new approval from the customer, sent the same way.
  • Estimates over a set amount get an advisor call on top of the text.
  • Customers marked as preferring the phone get a call first.
  • Negotiation, goodwill pricing and promise dates stay with the advisor.

Access stays narrow. The system needs to read estimates, photos and contact details from your shop management system and write decisions back to the repair order. It does not need your payment records. Every action it takes is logged.

Start in approval mode. For the first weeks, an advisor reads each outgoing text before it goes. Once the wording matches how your shop talks, move to approving exceptions only: large tickets, flagged customers and anything unusual.

Added work found mid-job is the most delicate approval. When a tech finds a second problem, the advisor writes a supplemental estimate and the same flow runs again. The first approval never covers the new work.

Your state may have rules about written estimates and customer authorization for repairs. Check yours. Make sure the record shows exactly what the customer was shown and what they approved.

Nudge once, then call

Customers go quiet for ordinary reasons: a meeting, a phone in a locker, a text that scrolled away. One polite nudge helps. More than that starts to feel like pressure.

A workable cadence, for example: the first text goes out the moment the advisor approves the estimate. A nudge follows after two hours of silence during business hours. If there is still no answer, a call task lands on the advisor's list with the full history. Nothing sends after closing, and the clock resumes the next morning.

Give the advisor a simple board with four columns: sent, opened, decided and needs a call. The board shows who is waiting on whom, and the call list builds itself. Cars dropped off at night get their text when the shop opens.

Write the nudge in your shop's voice and keep it light. A good one says the car is on the lift, the photos are one tap away, and the customer can reply with questions. It never mentions a deadline the shop cannot keep.

A nudge might read: Your car is still on the lift and your estimate is waiting. The photos are one tap away, and you can reply here with any questions. Texting also needs permission, so collect the customer's agreement at check-in and honor STOP the first time.

Fix the inspection before you fix the text

The text is only as good as what the tech attaches to it. A finding with no photo and a vague note makes a customer ask questions, and questions stall approvals.

Set the multi-point inspection so every recommended line needs a photo and a one-sentence note in plain words. Skip jargon. Say what the part does, what the tech saw and what happens if it waits. Advisors can edit the wording, but they should not have to write it from scratch.

Group findings the way a customer scans them: needs attention now, will need attention soon, and looks fine. The grouping also helps later. A soon item declined today is the item you re-quote when it comes due.

Here is a plain line a customer can act on: front brake pads are worn thin, photo attached, replacement includes parts and labor. Compare that with a note that says front pads low. One gets approved, and the other gets a phone call.

Train the techs once, with real examples from your own shop. A good photo shows the part and enough around it to find it. A bad one is dark, blurred or too close to read.

Measure approvals by time and by outcome

Start with two numbers: the time from estimate sent to decision, and the share of estimates that get any decision the same day. Your shop management system already holds the time stamps, so you can baseline both before launch.

  • Time to decision, from estimate sent to customer answer, by advisor and by size of ticket.
  • Same-day decisions, and estimates that were never decided.
  • Approval by line type, to see which findings customers question.
  • Chase calls, meaning the calls the advisor made each day to get approvals.
  • Disputes about what was approved, which should sit near zero if the record is good.

Compare each number with your own baseline. If time to decision drops but disputes rise, the text is moving faster than customers can follow, and the page needs clearer wording.

Here is what a gain looks like. Say the baseline wait is three hours and it falls to an hour and a half. On the six estimates a day from the example at the top, that is nine hours of waiting removed from the day. Use your own counts, and the gain is yours to measure.

Take two weeks of baseline before launch. If your system keeps time stamps, pull them. If not, have the advisors jot down when each estimate went out and when the answer came back. A paper tally is enough.

Review the numbers monthly with your advisors, and ask them what customers keep asking. Those questions are your next edit to the page.

What to do this week

Start with the inspection, because everything else in the flow depends on what the tech captures. None of these steps needs a build.

  1. Pick one advisor and one week, and write down how long each estimate waits for a decision.
  2. Check what your multi-point inspection captures today, and note which findings arrive without a photo.
  3. Write the text you would send for a routine finding, in your own voice.
  4. Take the tech notes from a few recent inspections and rewrite each in one plain sentence, as a test.
  5. Decide the dollar amount above which an advisor calls as well as texts.
  6. Ask your shop management vendor whether estimates, photos and decisions can move through an integration.

That is a few hours of work, and it gives you the baseline and the rules a build needs. If you want it mapped, the free workflow walkthrough is the place to start. The customer approvals page shows what a finished build handles, and the auto repair guide covers the rest of the shop. A written quote and statement of work come before anything is built.