Multi-Trade Cross-Sell Texts: The One-Visit Second Job

Your tech is already in the house, already trusted, already looking at the other systems. Turn that observation into a second booked job — with licensed-trade rules, a clean handoff script, and dispatch logic that never sends the wrong trade.

System 7 from the Leveraged Owner Starter Pack

The plumber is under the kitchen sink when the homeowner mentions the water heater sounds like a kettle. A disposal hums wrong, and a breaker trips every rainy week. None of that was on the ticket — all of it is real work, in a house that already trusts you. With no system for that moment, the second job goes to chance, and she usually calls somebody else next month. This post builds the system, inside the same discipline behind appointment confirmation texts that keep a calendar full: notice it, ask permission, text it clearly, route it to the right licensed trade.

The rule that runs everything: licensed scope first

Before any script, fix the boundary in writing. A cross-sell text may only offer work the person who would do it is licensed and qualified to perform. Spotting a problem does not create permission to sell the fix.

Sort every possible second job into three buckets, posted where dispatch and techs can both see it:

Make this a standard operating procedure (SOP) — a written routine the whole team runs the same way — and keep each property's list in your CRM (customer relationship management software — where you keep customer records and job history). Concrete takeaway: if a job cannot be placed in Bucket 1 or 2 in ten seconds, it is an observation, not an offer.

Observation first, offer second

The strongest cross-sell starts as a specific observation she can verify herself: the disposal hums but does not spin, the water heater rumbles, the breaker trips in wet weather. Vague warnings sound like sales. Specifics sound like care, because they are.

Teach techs a two-sentence pattern on the visit:

Then stop talking. She decides. Concrete takeaway: grade techs on observations logged, not pressure applied, and the honest ones convert on their own.

Step one on the visit: ask permission before any text

The text lands well because it was invited in the room. Before leaving, the tech asks one short question and records the answer:

Before I go — I noted [Item] while I was here. Would it help if [Business Name] texted you the options for getting it looked at, with the price range first? No obligation. — [Tech Name]

A yes is permission for that follow-up about that item — not a blank check for promotions. A no ends it, and the note goes in the record so nobody texts it later. Concrete takeaway: one item, one permission, one text thread.

Step two: the cross-sell text itself

Send it the same day, while the visit is fresh — but once, from one place. Duplicate texts from a tech and a dispatcher make a careful system look like a sales floor. Your FSM (field service management software — the program that runs your schedule and job records) should show it as a task with one owner.

Hi [First Name], it's [Your Name] from [Business Name]. [Tech Name] was at your home today for [Original Job] and noted: [Item and Observation]. That's [Trade] work — [Tech Name] doesn't do that part. I can book a check by our [Trade] tech for [Two Time Options], price range [Price Range] before any work starts. Reply YES for a time, or NO and we'll leave the note on your file. Reply STOP to opt out.

Notice what the script does: it names who saw the problem and the correct trade, gives the price range before booking, and makes NO a complete answer. Concrete takeaway: hiding the handoff to get a yes is how a cross-sell turns into a complaint.

Why same-day matters: a typical business takes 42–47 hours to respond to new inquiries (2026 benchmark studies of 250K+ inbound leads), while responding within an hour makes you 7x more likely to qualify a lead (Harvard Business Review, 2011).

Step three: the handoff script between trades

Most cross-sells die between the trades. The plumber mentions the panel, means to tell dispatch, gets a callback, and the note evaporates. Fix it with a written handoff in the job record, never in someone's memory.

HANDOFF — From: [Tech Name], [Trade A]. Property: [Address]. Observed: [Item, Sign, Location in Home]. Bucket: [1 — my trade / 2 — shop, other trade / 3 — not our work]. Homeowner permission to text: [Yes / No]. Access notes: [Gate, Pets, Parking]. Photo attached: [Yes / No].

Then the receiving trade confirms receipt in writing:

Got it — [Receiving Tech Name], [Trade]. I've read the note and photo. I can take it [Day / Time Window] or [Day / Time Window]. Quote range to confirm first: [Price Range]. If it's [Likely Bigger Issue], I'll stop and re-quote before doing anything.

Two rules make it trustworthy. The receiving tech works from the note and photo, so she never re-explains her house. And if he finds something different, he stops and re-quotes before starting — the observation was a starting point, not a promise. Concrete takeaway: a written handoff with a named receiver is the difference between a system and a rumor.

Step four: dispatch logic that routes the second job

Dispatch routes the second job with a fixed logic, in this order every time:

When she replies YES, book it like any other job: confirm the trade, tech's name, arrival window, and price range. Concrete takeaway: the second job gets the same discipline as the first, because to her it is simply her next job.

A worked example, start to finish

Example: an HVAC tech on a tune-up finds a drain line backing up toward a water heater with corrosion at the base. Plumbing is Bucket 2 for his shop. He says what he saw, asks permission, and logs the handoff with a photo. Dispatch texts that afternoon, naming the trade and the price range. She replies YES. The plumber arrives two days later knowing the layout, re-quotes the larger fix in writing before starting, and does the licensed work.

Example, the other direction: the same tech notices a breaker that trips in wet weather, and his shop has no electrician. Bucket 3 — no text offer. He tells her what he observed, suggests a licensed electrician, and dispatch notes the file. The shop earns nothing on that item, and keeps the trust that makes every Bucket 1 and 2 text welcome.

What never goes in a cross-sell text

Compliance notes: texting about a second job

Related guides in this series

This system lives inside Appointment Confirmation Texts That Cut No-Shows in Half — the Pillar D system for a full, calm calendar. For another permission-based one-visit add-on, see Smart Thermostat Upsell Text: The 10-Minute Add-On, and for building the household relationship over the first year, see New-Homeowner Welcome Campaign: The First-90-Days Sequence.

Get System 1 free: the complete Missed-Call Safety Net

The full setup SOP, all four copy-paste scripts (including the owner notification), the "Your Numbers" missed-call worksheet, and the step-by-step setup guide — free, no catch. Fix your missed calls this week.

Free. The full 8-system Starter Pack is $27 if you want everything else.

The done-for-you version

This post is System 7 from the Leveraged Owner Starter Pack — the done-for-you version with the full SOP, every script, the worksheets, and screen-by-screen setup instructions for all 8 systems. It includes this cross-sell system pre-written — bucket list, permission ask, text and handoff scripts, dispatch rules — ready to load with your trades and price ranges.

Stats sourced as labeled: response-time benchmark from 2026 studies of 250K+ inbound leads; qualification figure from Harvard Business Review (2011). Worked examples labeled as examples; not real customer results.

Keep building your systems

Related guides from the Leveraged Owner blog: