Home inspectors lose referring agents mostly by being slow to respond and hard to reach, not by doing bad inspections. A workflow in GoHighLevel can send the agent a status update after every inspection, and it should share the results only when the client has agreed. The bottom line: the update that keeps the agent is a fast, brief one, and the rule that protects the inspector is client consent.
Why agents stop referring
A 2001 NAR and ASHI study, still widely quoted, found 69 percent of home buyers chose their inspector on a real estate agent's recommendation. Spectora, an inspection software company, surveyed inspectors, agents, and buyers in January and February 2026. It reports that nearly 8 in 10 inspectors say agent referrals are their main source of new business, that clear reports (48 percent), professional communication with buyers (47 percent), and reliability and timeliness (46 percent) drive agent referrals, and that being slow to respond or hard to reach is the single biggest reason agents stop referring, cited by 25 percent. Another 15 percent cite reports too technical for buyers, and 15 percent cite poor buyer communication. Spectora also reports that 40 percent of inspectors close the relationship once the report reaches the buyer, although two thirds of buyers ask for repair advice afterward. It is a vendor survey, so treat the figures as an industry signal.
What the inspector may share
ASHI's Code of Ethics says inspectors shall not disclose inspection results or client information without client approval, with an exception for immediate safety hazards. InterNACHI's code bars releasing information about the inspection or the client to a third party unless needed to protect safety or comply with law, or the client has been told what will be released, to whom, and why, and has given prior written consent. The buyer is the client, so the agent is a third party unless the client says otherwise. Most inspection agreements let the client authorize sending a copy to the agent, so ask that question at booking.
| Client authorized the agent copy | Client did not |
|---|---|
| Send the agent the report link and a one line summary | Send the agent only: the inspection was completed and the report went to the client |
| Follow up on the repair request window | Do not describe findings |
The status update
| When | Message to the agent |
|---|---|
| Inspection booked | Booked for [date] at [time] for [client name] |
| Inspection complete | Inspection is complete, and the report goes to the client by tonight |
| Report delivered | Report was delivered to the client at [time]. Thanks for the referral |
| 2 days later | Offer to answer questions or re inspect after repairs |
| 30 days after closing | Review request to the client, and a thank you to the agent |
Build it in GoHighLevel
- Add a field to the booking form: Send a copy of the report to my agent (yes or no), plus the agent's name, email, and phone.
- Create the agent as a contact and link them to the client, for example with a custom field or a related contact.
- Build a workflow with the Appointment Status trigger set to Showed Up that sends the complete message to the agent.
- Add an If/Else on the copy authorization field. If yes, send the link and summary when you tag the report delivered. If no, send the generic delivered message.
- Add a Wait of 2 days and the follow up message.
- Turn on Stop on Response and set a Time Window.
HighLevel help center pages describe the Appointment Status trigger as firing when an appointment is created or its status changes, with statuses New, Confirmed, Cancelled, Showed Up, No Show, and Invalid, and with filters for calendar, calendar group, tag, user, and who made the change (customer, user, or API). The Update Appointment Status action can set the same statuses from inside a workflow. A third party agency guide adds that Appointment Status is now the main appointment trigger and the older Customer Booked Appointment trigger is being phased out, so use Appointment Status for new builds.
What the workload looks like
For example, at 30 inspections a month with 78 percent coming through agents, that is about 23 agent relationships touched a month (30 times 0.78). One updated status per inspection keeps each agent informed without a call.
Mistakes to avoid
- Sharing findings without consent. Both national codes forbid it.
- Slow replies. It is the top reason agents leave.
- Technical reports. Agents read them on a phone.
- Paying for referrals. ASHI forbids it.
How this was handled before
Inspectors handed over a report and moved to the next inspection. Agents learned the report had arrived from their buyer, if at all. A brief status update tells the agent the job is done and the report is out, which answers the question they would otherwise ask, and stays inside the client's confidentiality.
Check before you switch it on
US text messages sent from a standard 10 digit number need A2P 10DLC registration. The HighLevel support portal says registration is required for texts to US recipients from 10 digit long code numbers and that toll free numbers do not require it. HighLevel's opt in guidelines also say a person cannot be forced to agree to text messages in order to submit a form, so keep the consent box optional. One compliance guide separates informational texts, which need documented consent, from marketing texts, which need prior express written consent. Ask your attorney which category your reminders fall into. Agents and clients often prefer email for reports and text for scheduling, so ask them which they want. This is general information, not legal advice.
Questions people ask
Can I tell the agent what I found?
Only if the client has authorized it. ASHI's code requires client approval, and InterNACHI's requires prior written consent.
Why do agents stop referring inspectors?
In Spectora's 2026 survey, being slow to respond or hard to reach was the top reason, at 25 percent.
What can I always tell the agent?
That the inspection was completed and the report went to the client, without describing findings.
Ready to try it yourself? Start a GoHighLevel account here.
You can also see this in action in our GoHighLevel capabilities demo.