How to Sell AI Builds to Appliance Repair Companies (The Second Trip Pitch)

The Short Answer

Sell to an appliance repair company by selling first-visit fixes and fewer wasted calls, not more leads. When a fridge stops cooling or a washer will not drain, the homeowner calls down the list until someone answers, and the company that picks up gets the job. The person who would answer is often the owner, on their knees behind a dryer. And when a call does get booked, it often arrives with nothing more than 'my dishwasher is broken,' which means the technician shows up, finds the fault, orders a part, and has to come back.

That is the Second Trip Pitch: two questions - how many jobs last month needed a second visit, and how many calls went to voicemail while your technicians were out? - followed by a demo of an assistant that books visits in the company's own words and collects the model number and symptom before anyone drives anywhere. If you have read the pitch for [HVAC companies](/blog/sell-ai-builds-to-hvac-companies) or [plumbing companies](/blog/sell-ai-builds-to-plumbing-companies), the shape is familiar. The difference with appliance work is the part. Better information at booking can turn some two-trip jobs into one-trip jobs, and that is worth as much to the owner as the extra calls answered.

What an Appliance Repair Company Actually Pays For

Every appliance repair job has the same rhythm: a call comes in, a technician visits, the fault is found, and either it is fixed on the spot or a part is ordered and a second visit is booked. The owner's margin lives in that rhythm. In my view, the first build worth pitching sits on one of four leaks in it.

• Intake while the crew is out: an assistant on the website, in messages, and behind a missed-call text that answers the company's own questions about service area, brands they work on, and their service call fee, then collects the appliance type, brand, model number, and what the customer is seeing, and books the visit or hands the conversation to a person.
• Model number capture: a simple guided step that asks the customer to send a photo of the appliance's model and serial label, in the wording the owner approves, so the technician can look it up before the visit. The assistant only collects the photo. It does not read anything into it.
• Parts status updates: when a part has been ordered, an update to the customer from the company's own records when the part arrives, with a link to book the return visit. This replaces the 'is my part in yet?' calls that interrupt the office all day.
• Review requests: a short thank-you after the repair that asks for a review, since homeowners searching in a hurry pick the company with the most recent good reviews.

Notice what is not on the list: any judgment about the appliance itself. Customers ask 'is it the compressor?', 'should I just buy a new one?', and 'can I fix this myself if you tell me which part?' Those are questions for a technician who has seen the machine. The assistant should say so, in the owner's words, and get a visit on the calendar.

Work inside the company's own scheduling and invoicing tools wherever you can, and keep payment details out of chat. Job records hold home addresses and notes about who will be home, so treat them as private. [Is it safe to use Claude Code with client data](/blog/is-it-safe-to-use-claude-code-with-client-data) covers how to handle that side of the build. You can build and test all of this in the Claude Code desktop app; the terminal is optional.

How to Pitch the Appliance Repair Owner

Before you reach out, call the company in the middle of a weekday, when the technicians are usually on jobs, and note what happens. Does a person answer? Does it ring out to voicemail? Does anyone text back? Then send a request through their website and time the reply. Read their public reviews too. Comments about waiting days for a call back, or about a technician who had to come back twice, tell you which half of this pitch will land hardest.

Then ask the two Second Trip questions. 'How many jobs last month needed a second visit?' Most owners know this number roughly, and it stings. 'How many calls went to voicemail while your technicians were out?' Then [demo, do not describe](/blog/the-demo-first-close). On your phone, send 'my fridge stopped cooling, can someone come out this week?' and show the assistant asking for the brand, the model label photo, and the symptom, then offering open times. Then send 'I smell gas near the stove, what should I do?' and show it telling the customer to call emergency services right away and alerting a person at the company. That second message is what wins the owner's trust. It shows the build knows where it stops.

[Qualify before you build](/blog/qualify-a-lead-before-the-call). Ask what they use for scheduling and invoicing, whether parts orders are tracked anywhere a build can read, and whether their service call fee, service area, and brand list are written down. A company that already logs parts orders against jobs is a fast build, because the status updates have something to work from on day one. A company that tracks parts on sticky notes is a different project, and setting up that tracking is its own scoped job. The best first fit is a small owner-led company with steady call volume and no one dedicated to the phones.

How to Price the Build

Price against first-visit fixes and booked jobs, not your hours - the frame [value-based pricing](/blog/value-based-pricing-stop-charging-hourly) exists for. The owner knows what a typical repair is worth, what a wasted trip costs in technician time and fuel, and how many calls they miss. Do the math out loud with their numbers: take the second visits from last month, assume only some of them could be avoided with better intake, and add the missed calls that would have booked. If those jobs cover the build within a few months, a scoped first build priced in the low thousands is easy to justify.

Then attach the monthly plan, because brands, prices, and service areas change, and the intake questions need tuning as you see which details actually help the technicians. Structure it the way [packaging a maintenance plan for AI builds](/blog/package-a-maintenance-plan-for-ai-builds) lays out, and report what the owner cares about: calls answered while the crew was out, bookings that arrived with a model number, parts updates sent, and reviews collected. If they hesitate, a small paid parts-update build on their existing records is a fine first step. It shows results without touching the phones.