Source
Establish where the records came from and the prior relationship.
Dormant customer reactivation · Australia
Dormant customer reactivation is a planned attempt to reconnect with an eligible cohort of prior customers. Gibson reviews the relationship evidence, exclusions, consent and suppression position before defining the cohort, approved message, reply ownership and outcome record.
This page is for operators with a genuine prior-customer relationship who need to assess whether a controlled campaign is appropriate. A past transaction does not by itself guarantee eligibility, contactability or a result.
Last reviewed 2 August 2026 · By Albert Triolo, Founder and Managing Director
Gibson evidence-to-action method
Establish where the records came from and the prior relationship.
Review consent, suppression, complaints, exclusions and uncertainty.
Define who belongs in the controlled campaign and who does not.
Approve the message, response handling, escalation and stop conditions.
Record sends, delivery, replies and matched outcomes within the agreed boundary.
Inspectable proof
Gibson tested the method on 130 of its own contacts who had genuinely dealt with the business and had not been spoken to in more than a year. Thirty-five returned as confirmed jobs, producing $9,415 in total value.
Questions before a campaign
Database reactivation is a planned attempt to reconnect with an eligible dormant cohort from an existing business database. It begins with source, relationship, consent and suppression evidence, then defines the cohort, approved message, send controls, reply owner and reporting boundary.
No. Demand Reactivation is a planned campaign for an existing dormant database. Demand Recovery follows a current agreed missed-call event. They use different triggers, eligibility evidence, timing, message controls and proof trails.
Start with aggregate information: database source, approximate cohort size, age, prior relationship, consent and suppression records, services, likely exclusions, reply owner and the system that should hold agreed outcomes. Do not upload personal records through the general brief.
Price and timing depend on data readiness, eligibility review, cohort size, message approval, platform, send volume, reply handling, integration and reporting. Any initial period, payment trigger, inclusions and continuation terms are confirmed in the written proposal.
None. List quality, eligibility, prior relationship, offer, timing, deliverability, message, reply handling and market conditions affect the result. Reporting can describe observed campaign events and matched outcomes within the agreed evidence boundary.
Next decision
Review the canonical service first. If the database may fit, send only high-level context through the brief. Albert or the senior team will confirm the next useful evidence step.