Solutions
Reactivation & Retention Systems
Past relationships drift when no re-entry path exists.
Some contacts are not lost; they are inactive, lapsed, waiting for the right cycle, or ready for a future reason to return. Orbiis turns dormant relationship state into governed re-entry logic across recall, repeat service, renewal, seasonal demand, long-cycle consideration, and past-customer return paths.
The Dormant Relationship Gap
The relationship may still have value. The system has stopped carrying it.
A relationship does not usually disappear in one moment. It leaves the active path, time passes, and the business loses the signal for when that contact should return.
Entry state
Relationship existed → active path ended → time passes → re-entry condition becomes unclear
Dormancy is not always failure. Sometimes the customer is waiting for the next relevant moment. The operational failure is not knowing when that moment exists.
Without reactivation logic
Past contacts remain in records.
Staff remember some people manually.
Timing depends on habit, urgency, or campaign pressure.
Repeat-cycle opportunities are missed.
Dormant contacts are hard to distinguish from closed contacts.
With reactivation logic
Dormancy becomes visible.
Eligibility is checked before outreach begins.
Timing is based on lifecycle or relationship context.
The re-entry route is defined.
Response, no-response, suppression, and future-cycle states remain visible.
The relationship is not the problem. The missing re-entry path is.
Not Leftover Follow-Up
Follow-up carries active interest. Reactivation reopens dormant opportunity.
Follow-up belongs to the active decision window. Reactivation begins after that window has ended, or after a customer, patient, client, buyer, or inquiry has left the active path. The system should not simply send another message. It should know why the relationship is eligible to re-enter.
Operating distinction
Follow-up continues an active opportunity.
Reactivation starts from dormant or past relationship state.
A campaign does not prove eligibility.
A reactivation system preserves timing, context, route, and outcome state.
The question is not who should receive another message. The question is which dormant relationships have a valid reason to return.
Re-Entry Model
The system must know who is dormant, why they are eligible, and what path should reopen.
Reactivation is not a broadcast. It begins with relationship state, checks eligibility, applies lifecycle timing, and routes the contact back into the correct operating path if they respond.
Re-entry path
Dormant state → Eligibility gate → Re-entry prompt → Active path or remains dormant
The system does not treat old contacts as a list to message. It turns dormant relationship state into an eligibility-based return path with visible outcomes.
Dormant state
Contact inactive, lapsed, completed, or cycle-ready
The relationship is no longer handled as active follow-up. It is readable as dormant, past, lapsed, or waiting for a future cycle.
Eligibility gate
Why should this relationship re-enter now?
Recall, repeat service, renewal, replenishment, seasonal demand, long-cycle consideration, or prior intent determines whether a valid re-entry reason exists.
Return path
Response returns the contact to the active operating path
When the contact responds, the system routes the relationship back into the correct active path instead of creating another manual conversation.
No response
Remains dormant with visible state
The contact does not disappear again. The dormant state remains readable for reporting, future review, or the next eligible cycle.
Suppressed / closed
Wrong fit, opted out, resolved, or irrelevant
The system distinguishes dormant opportunity from relationships that should not be contacted again.
Future cycle
Scheduled re-entry window remains governed
Some relationships are not ready now, but they have a future reason to return. The next window remains governed.
Reactivation Path in Motion
What happens when a relationship leaves the active path.
The system does not treat inactivity as disappearance. It preserves dormant state, checks whether a re-entry reason exists, and keeps the outcome visible after the attempt.
01
Dormant state identified
Contact becomes inactive → dormant state becomes visible
The contact is no longer treated as active follow-up. The system marks the relationship as dormant, past, lapsed, completed, or cycle-based according to its context.
02
Eligibility selected
Lifecycle, service cycle, recall, renewal, season, or prior intent determines re-entry logic
The reactivation path is based on why the contact has a valid reason to return, not simply on how much time has passed.
03
Re-entry path opens
Message, task, campaign, or human route begins from context
The system opens the correct re-entry route: recall, repeat service, renewal, seasonal prompt, long-cycle inquiry, re-enrollment, or past-customer return.
04
Outcome resolved
Returned active, no response, suppressed, or future cycle state remains visible
The business can see whether the relationship returned, remained dormant, should be suppressed, or should re-enter at a future cycle.
Beyond Campaigns
Campaigns create outreach. Reactivation systems govern eligibility, timing, and re-entry state.
A campaign can send a message to old contacts. That does not mean the relationship is eligible, the timing is right, the reason for return is clear, or the outcome will remain visible. Reactivation requires the system to preserve dormant state, context, suppression, and future-cycle logic.
Reactivation is not outreach to the past. It is a governed path back into the operating system.
A campaign does not know whether the contact is eligible.
A campaign does not distinguish dormant from closed.
A campaign does not know the correct re-entry reason.
A campaign does not preserve returned, no-response, suppressed, or future-cycle state.
Inside the Wider System
Reactivation begins when a relationship has left the active path but still has a reason to return.
Follow-up, completion, and reputation create the upstream relationship state. Reactivation governs what happens later, when a contact becomes dormant, lapsed, cycle-ready, or eligible for a future return.
01
Follow-Up / Completion / Reputation
02
Dormant State
03
Reactivation & Retention
04
Active Path
05
Pipeline Visibility
Follow-up and reputation are upstream. Reactivation completes the lifecycle layer by turning inactive relationships into readable re-entry opportunities instead of forgotten records.
Deployment Entry
Dormant relationships should not depend on memory to return.
If past clients, lapsed inquiries, recall cycles, repeat-service opportunities, renewal conversations, or seasonal return paths still live in old records and staff memory, the re-entry layer is not governed. A Revenue Audit shows where dormant relationships should become visible operating state again.