Skip to main content

Reactivation

Database Reactivation

Database reactivation is identifying quieter relationships that are worth reconnecting with, and giving the agent a relevant, human reason to do so.

Quick answer

Reactivation works best when it is relationship-based, not a blast to everyone who has not been touched recently. Look for people you already have real history with, who have not had a genuine conversation in months, and who show recent, meaningful activity. Then reach out about them and their situation, not about what the software noticed.

Why it matters

Past clients and sphere contacts are often the most valuable relationships in a database, and the easiest to neglect. A thoughtful reconnection at the right moment can lead to a listing, a referral, or simply a stronger relationship.

Done badly, reactivation burns goodwill: generic blasts, outreach triggered by a single click, or messages that make people feel watched.

Reactivation is not the same as a request

SituationWhat it calls for
Quiet past client with a recent home-value viewA personal or home-value check-in when it fits
Quiet past client who asked for a CMAA direct response, not ordinary nurture
Quiet contact with one email clickUsually nothing yet; one click is light engagement
Active client or open dealNot reactivation; they are already being served

How it works in practice

  1. 1

    Define quiet by real conversation

    Look for the absence of genuine human interaction over a meaningful period, not just an old last-contact date.

  2. 2

    Require a recent, meaningful reason

    A recent homeowner or buyer signal on a relationship you already have is a reason to review. Old or weak signals are not.

  3. 3

    Let a person decide, then close the loop

    The agent chooses the approach. Once the person has been reached, the episode closes instead of resurfacing as new.

Common mistakes

  • Blasting the whole database with the same message.
  • Treating one email click as a reason to call.
  • Mentioning click counts or dashboard visits in the outreach.
  • Auto-enrolling people in campaigns without anyone reviewing the reason.
  • Showing the same reactivation reason again and again after it was handled.

How SAM approaches it

  • SAM's Database Reactivation intelligence surfaces review candidates. A relationship counts as quiet when there has been no recorded human interaction in the last six months, the starting point of SAM's six-to-twelve-month reactivation playbook, and a provider signal only counts when it is recent, within about 90 days.
  • SAM does not enroll anyone or send anything on its own. A direct request from a quiet relationship is labeled as needing a direct response. Internal reasons are kept separate from customer-safe wording, and a closed episode waits 90 days before an ordinary new one can return.

Explore:Client retention solutionRoutinesFello integration

Frequently asked questions

Database reactivation is the process of identifying older or quieter relationships that may be worth reconnecting with and giving the agent a relevant reason to do so. It should be relationship-based, not a blind blast to every contact who has not been touched recently. In SAM, reactivation surfaces review candidates with an explainable reason. A person still decides what outreach, if any, should happen.

Related:Client retention

SAM looks for recorded human interaction, such as a connected call or real conversation, not just a last-contact date. A relationship counts as quiet for reactivation when there has been no such interaction in the last six months. That window is the starting point of SAM's Past Client Reactivation playbook, which suggests reconnecting after roughly six to twelve months of quiet.

There is no universal rule. The right cadence depends on the relationship and your business strategy, and plenty of past clients deserve regular contact long before they go quiet. SAM's reactivation check starts at six months without a real conversation, and it only treats a new signal as a reason to review when the signal is recent, within about 90 days.

Related:Client retention

A quiet relationship becomes more interesting when there is recent, meaningful evidence, such as homeowner engagement or buyer behavior, that fits the existing relationship. The person should already have real context with you, such as a past client or sphere contact, and the signal should not conflict with an active client or deal path. Address enrichment alone does not create that relationship.

Usually not. A single email click is light engagement. It can support a broader reactivation reason, but stronger evidence, such as a home-value view or other homeowner activity, should be present before treating the person as a reactivation candidate. In SAM, a click, dashboard view, or postcard scan can support a candidate but does not qualify one on its own.

Related:Homeowner Intent and Behavioral Signals

Reactivation is a reason to reconnect with a quieter relationship. A direct request means the person explicitly asked for help, such as a CMA or a callback, and deserves a response rather than being treated like an ordinary nurture opportunity. SAM labels a request from a dormant relationship as needing a direct response and keeps it out of the ordinary reactivation queue.

Use it as context for a better conversation. A past client viewing their home value or completing a check-in may be worth reviewing, but the activity does not mean they are moving. You should see both the relationship history and the new evidence before deciding what to do, and the outreach should be about them, not about what the software noticed.

Related:Client retention

Some tools do. SAM's Database Reactivation intelligence does not automatically enroll people, send messages, or create a separate campaign list. It identifies people worth reviewing and suggests an approach, such as a personal or home-value check-in. You then decide what should happen and can use the routine builder to set up the follow-up.

Related:Routines

Outreach should sound like a human relationship, not surveillance. SAM keeps the internal reason, which may mention provider activity, separate from a customer-safe reason that can appear in a draft. That way an agent can use the insight without telling someone a system counted their clicks or dashboard visits.

Related:Homeowner Intent and Behavioral Signals

A genuine human response or completed handling should close the current reason for reactivation. The system should not keep presenting the same episode as new just because the underlying event is still stored. In SAM, a completed episode stays closed, and ordinary reactivation waits 90 days before the same person can come back for a new reason. An explicit request is not held back by that wait.

Yes, when the signal is recent and belongs to a quiet relationship you already have, such as a past client or sphere contact, and there is no conflicting active client or deal path. The signal provides the reason to review. It does not enroll the person in outreach, and the agent decides what happens next.

It should remember the relationship, meaningful conversations, important dates, property context, past transactions, commitments, preferences, and what kind of follow-up fits the person. Retention is stronger when the system helps the agent stay relevant instead of sending the same message forever.

Related:Client retention

Homeowner tools can surface useful moments: interest in value, market activity, check-ins, financing questions, or direct requests. When those signals are connected to the existing relationship, the agent can choose a more relevant conversation instead of making a generic database call. SAM brings Homebot and Fello moments back to the contact your team already works.

Related:Homebot integrationFello integration

A single date is ambiguous. Imports, automation, provider activity, and inconsistent logging can all change it without a real conversation taking place. SAM's relationship intelligence uses evidence of actual human interaction for decisions like whether a past client has gone quiet or whether a request was answered, instead of assuming every last-contact date proves someone talked to the person.

Related:Relationship Intelligence

Search all answers

See it in your own business

Book a walkthrough with Workflow Secrets to see how SAM handles this with your contacts, deals, and team.