Reconnect with Suitable Contacts Already Known to Your Business
Existing enquiries, candidates, prospects and previous customers may still contain relevant opportunities—but any re-engagement must begin with understanding the data, its history and whether further communication is appropriate.
Old Contact Data Needs Assessment Before Action
Before any message is sent, the data itself must be understood. Five questions shape whether reactivation is appropriate at all.
A contact appearing in a spreadsheet or CRM does not automatically mean that marketing communication should be sent.
From Dormant Record to Appropriate Next Action
Records move from a subdued dormant state into clearly labelled response routes—one connected processing flow, not a bulk send.
Data reviewed
The client identifies the source, age, purpose and known communication history of the records.
Suitable segments defined
Contacts are grouped by previous enquiry type, service interest, candidate status or customer relationship.
Communication basis confirmed by the client
The client remains responsible for confirming which contacts may appropriately receive each type of communication.
Relevant outreach prepared
Messages are written for the specific segment, with clear sender identity and an appropriate reason for contact.
Responses are classified
Replies, objections, opt-outs and renewed interest are recorded and directed towards the correct next action.
Human follow-up begins where appropriate
Interested or uncertain responses can create a task, pipeline opportunity or consultant notification where configured.
Every Response Should Change What Happens Next
One outreach node branches into five database-status routes, each with its own next action.
sent
Create or update an active opportunity and notify the appropriate person.
Record the preferred timing and create an appropriate future task or follow-up route.
Send or assign an approved response rather than forcing an immediate booking.
Update the record to prevent inappropriate continued follow-up.
Stop the relevant communication and record the preference appropriately.
No response should not automatically trigger indefinite communication. The agreed sequence should have a clear stopping point.
Different Databases Require Different Conversations
Three compact examples of how segments and purposes vary by business type.
Possible segments
- Dormant candidates
- Previous applicants
- Former clients or hiring contacts
- Contacts associated with earlier vacancies
Possible purposes
- Confirming current availability
- Updating candidate information
- Understanding present hiring requirements
- Inviting an appropriate conversation
Reactivation should complement the agency's existing ATS and communication rules. It should not make hiring or suitability decisions.
Possible segments
- Previous enquiries
- Quotations that did not progress
- Existing customers
- Contacts associated with a relevant previous service
Possible purposes
- Confirming whether a previous requirement remains
- Relevant seasonal or maintenance communication
- Follow-up on an earlier quotation where appropriate
- Inviting a new service enquiry
Possible segments and purposes depend on the original relationship, sector, service and communication history.
Examples may include
- Previous consultation enquiries
- Lapsed appointment-led customers
- Earlier commercial prospects
- Established contacts with a relevant service update
Not all listed contacts can legally or appropriately be messaged.
Reactivation Must Connect to a Managed Process
Reactivation is not simply a bulk message. The value comes from giving each response a visible status, owner and next action.
- Data-source and process review
- Import and field mapping
- Segmentation structure
- Message preparation
- Reply and opt-out handling
- CRM stages and response routing
- Internal notifications and tasks
- Controlled testing before wider release
Data condition, contact volume, messaging costs, platform limitations and the required review process affect the final scope.
Relevant Communication, Clear Boundaries
Client-confirmed basis
The client must confirm the appropriate communication basis, permissions and sector requirements for the intended audience.
Accurate identity
Messages should clearly identify the business and avoid misleading or manipulative wording.
Preferences respected
Objections and opt-outs should be recorded and acted upon appropriately.
Controlled frequency
Every sequence should have a defined purpose, frequency and stopping point.
LeadAI can support the operational setup but does not provide legal advice or independently determine whether a database may be used.
Could Your Existing Database Contain Relevant Conversations?
Book a Growth System Audit to review the condition, structure and operational potential of your existing contacts before deciding whether reactivation is appropriate.