Vacant land replies moved into one pipeline
This was a land business, so the usual house-wholesaling CRM shape did not fit. The operator had county records and a price-per-acre model, but replies from mail and text were landing everywhere. VA Horizon set up the SMS campaign, handled number registration, prepared the list, and routed replies into HighLevel with the parcel fields a land buyer actually needs.
The replies looked simple until someone had to underwrite them
This was not a house wholesaler trying to force a residential CRM onto land. The operator bought rural vacant land and infill lots, mostly from county records. The math was different: acreage, access, APN, zoning notes, floodplain concerns, and price per acre mattered more than beds, baths, and ARV.
The operator had lists and a basic offer model, but responses were scattered. A seller might reply to a text, call the number, email after a mail piece, or send a photo of a tax bill. Some details landed in a spreadsheet. Some stayed on a phone. Some were written down and re-entered later. The pipeline depended too much on the owner remembering where the conversation started.
Land made the mess easier to underestimate because a short seller reply can look simple. "I have 5 acres in Smith County" is not enough to make a buying decision. The team still needs the APN, access notes, rough location, ownership situation, and seller expectation. Without those fields, every reply becomes a tiny research project.
The goal was not to make land investing look like residential wholesaling. It was to build a simple intake path for land sellers so every reply had the fields a land buyer actually needs before deciding whether to review the parcel.
What the house-style setup missed
- /County records were usable but not organized for outreach
- /Seller replies were split across phone, spreadsheet, and manual notes
- /Residential CRM fields did not capture APN, acreage, or land-specific review notes
- /No clean way to separate bad parcels from review-worthy opportunities
The campaign had to know it was land
Sending the texts was only part of it. The bigger risk was getting a reply and then losing ten minutes figuring out which parcel the seller meant, whether there was access, or where the APN had been saved. We built the reply path around the underwriting questions, not around generic lead capture.
Campaign setup and registration
VA Horizon handled campaign configuration, number registration, and A2P setup so the operator was not guessing through compliance screens.
List prep for land fields
We prepared records with county, APN, acreage, owner name, mailing address, and any available parcel notes. The data had to match the questions the buyer would ask later.
Reply routing into HighLevel
Seller replies created or updated a HighLevel contact and moved into a land-specific pipeline. The first goal was to capture the reply cleanly, not bury it in an inbox.
Review task for buyer-side decision
When a seller gave enough information, the system created a review task with acreage, APN, asking price, and notes. The operator could decide quickly whether the parcel deserved a deeper look.
What changed when every reply had a parcel record
Before: Replies
Phone, spreadsheet, email, and notes
After: Replies
HighLevel contact with parcel fields
Before: Data model
House-style CRM fields
After: Data model
APN, acreage, county, asking price, access notes
Before: Campaign work
Owner-managed setup and routing
After: Campaign work
VA Horizon-managed setup and back end
Before: Decision flow
Owner searched for context
After: Decision flow
Review tasks created from seller replies
Results that mattered
- +Seller replies stopped living in separate places. HighLevel became the place to review, route, and decide.
- +The operator could separate junk parcels from worth-reviewing parcels faster because APN, acreage, county, and asking price were visible in the same record.
- +The SMS campaign gave the land operator a repeatable channel without forcing him to manage list prep, registration, routing, and CRM setup himself.
Attribution Note
This case study is anonymized. The pricing references match VA Horizon SMS campaign packaging, not a private custom quote.
The CRM needed land fields, not prettier house fields
Land campaigns break when the intake system is built for houses. A parcel with no road access is a very different conversation than a tired landlord with a duplex. If the CRM does not store the right facts, every review starts from scratch.
The text got the reply, but the pipeline made the reply usable. That distinction mattered. A land seller saying yes is still only the beginning if the team cannot quickly find acreage, access, county, APN, and asking price.
The owner did not need a prettier spreadsheet. He needed fewer open loops. Once a seller replied, the system pushed the conversation toward the facts that affect land value: county, APN, acreage, access, asking price, and ownership status. That meant the owner could review parcels in batches instead of chasing one missing detail at a time.
The land-specific questions that matter
Run land outreach without losing the replies.
We can handle SMS setup, A2P registration, list prep, and a land-specific HighLevel pipeline for your seller responses.