How do past-client reactivation and referral campaigns work for agents?
Past-client reactivation for real estate agents is a long, low-frequency sequence of home-anniversary notes, neighborhood market updates and referral asks sent to closed clients, and it differs from other industries because the client will not buy again for years, so the goal is the referral in between, not a repeat sale.
Why is reactivation different for a real estate database?
A dental patient comes back in six months; a home buyer comes back in seven to ten years. Reactivation in real estate therefore has almost nothing to do with the client’s next transaction and everything to do with the people they know who are moving this year. The sequence exists to keep the agent’s name attached to the word “house” in the client’s mind.
The database itself is unusual. It splits into past buyers, past sellers, expired or lost leads, and sphere contacts who never transacted, and each group needs a different reason to hear from the agent. A buyer wants to know what their home is worth now; a seller who moved away wants to know the old street sold high; a lost lead wants to know the market shifted.
The trigger is the calendar, not a visit. Home anniversaries, tax-assessment season, spring listing season and a rate change are the moments a message is welcome, so the sequence is built around dates stored on the contact, not around a last-visit field.
- Years between transactions, so referrals are the measurable output
- Four database segments, each with a different message reason
- Date-driven triggers: closing anniversary, assessment season, rate moves
- Home-value updates are the one message almost every past buyer opens
Which message goes to which past client and when?
| Segment | Trigger | Message | Referral ask | GoHighLevel handling |
|---|---|---|---|---|
| Past buyer, year one | Closing anniversary | Happy home anniversary plus a one-line value estimate | Soft: who do you know planning a move this year | Anniversary date field, workflow on date plus 0 days |
| Past buyer, years two plus | Quarterly market update | Three recent sales on their street or ZIP | Soft, every other message | Smart list by ZIP, workflow every 90 days |
| Past seller who relocated | Anniversary of sale | What the old neighborhood sold for since | Direct: friends still in the area | Tag Seller-relocated, separate branch |
| Lost or expired lead | Rate change or season | Market has moved, is timing better now | None until re-engaged | Pipeline Nurture stage, AI text with one question |
| Sphere, never transacted | Twice a year | Short personal note, no listing pitch | Direct, referral link | Tag Sphere, low-frequency workflow |
| Investor client | Rent or price data quarterly | Yield and inventory snapshot for their area | Direct: other investors | Tag Investor, branch with data table |
| Any segment replying | Inbound reply | Agent takes over from the Conversations inbox within the hour | Handled by the agent | Workflow pauses, task created, AI stops |
How is the reactivation and referral engine built in GoHighLevel?
Each step is a GoHighLevel object configured for a brokerage database.
Segment the database
Every closed contact gets a custom field for closing date and property ZIP, plus a tag for Buyer, Seller-stayed, Seller-relocated, Investor or Sphere. Smart lists are built from those fields so nobody gets a message meant for another segment.
Anniversary workflow
A workflow fires on the closing-date field each year, pulls the address and sends a text from the agent’s number with a home-anniversary note and a value-range line the agent approves in a task before it goes out.
Quarterly market-update workflow
Every 90 days a branch sends recent sales for the contact’s ZIP. The content comes from a custom values sheet the agent updates monthly, so the numbers are the agent’s own research, not generated.
Referral capture
Every other message ends with a referral question. Replies land in the Conversations inbox; a reply containing a name or phone number creates a new contact in the Referral stage of the Buyers or Sellers pipeline and tags the referrer.
Re-engaged lead routing
A lost lead who replies to a rate-change message moves from Nurture to New enquiry, which starts the speed-to-lead sequence, so reactivation feeds the same pipeline as a fresh portal lead.
What consent and advertising rules apply to reactivation messages in the US?
Every text in the sequence is a marketing message under the TCPA of 1991, with statutory damages of $500 to $1,500 per message when consent is missing. Consent recorded at the original enquiry or closing covers the anniversary and market-update texts only if it was for marketing, not just transactional updates, so the closing paperwork includes an explicit text-marketing opt-in.
The National Do Not Call Registry applies to the lost-lead segment. A lead who enquired years ago and never became a client can be on the registry, and the established-business-relationship exception expires, so lost leads older than the exception window are contacted by email only or removed.
Fair Housing Act of 1968 rules shape the market updates. Sales data is reported by street or ZIP, never with commentary about who is moving in or out, and every message identifies the brokerage as most state commissions require for advertising.
- Marketing-text consent captured at closing, not assumed from transactional texts
- Lost leads checked against the Do Not Call Registry before any text branch
- Market updates report prices and days on market, not demographics
- Brokerage name and opt-out line on every message
How do you check whether your past-client database is working?
- Count closed clients in the CRM and how many have a closing date and ZIP stored
- Count referrals received in the last year and which client sent each one
- Find the last time a past buyer heard from you other than a holiday card
- Check whether marketing-text consent exists for closed clients
- Check lost leads against the Do Not Call Registry status field
- Confirm market-update numbers come from a source you can name
Common questions about past-client campaigns for agents
How often should a past client hear from me?
Four to six times a year: the anniversary note, two or three market updates and one or two personal touches. More than that in text form reads as spam; less than that and the referral goes to whichever agent the client saw on social media last week.
Should the home-value estimate be automated?
The message is automated; the number is not. The workflow creates a task for the agent to confirm a value range before the anniversary text sends, so the client receives the agent’s judgment, not a generated figure the agent has to walk back.
Do referral asks in a text actually work?
They work when they are specific and rare. A question such as who do you know who is thinking about moving this spring, sent once or twice a year after a useful market update, produces replies. A referral link in every message trains the client to ignore it.
What happens when a past client replies?
The workflow pauses for that contact, the reply appears in the Conversations inbox, and a task tells the agent to answer within the hour. If the reply contains a name or number, a new contact is created in the Referral stage and the referrer is tagged.
Can lost leads from years ago be added?
Only with a consent and Do Not Call check first. Leads who opted in to marketing texts and are not on the registry enter the Nurture branch; the rest receive email only or are removed. The re-engagement message is one question about timing, not a listing pitch.
Turn a closed-client list into a referral engine
Bring your CRM export and last year’s referral count. We map the segments and the calendar on the call.
Book a Free Strategy Call