Guide
Past-client reactivation: a practical CRM workflow
Choose who to contact, write a relevant message, and track the result through to a new engagement.
How do you reconnect with past clients?
Review the previous engagement, confirm the current contact and their preferences, and identify a specific reason to reconnect. Assign one owner, send a short message, and record the response. Create a new opportunity when there is a current need to discuss.
Build a shortlist from the engagement history
Start with completed work and the reason the relationship paused. An old customer record gives you context to check; the client may now have different needs or people.
Check the previous outcome
Read the closeout notes, unresolved issues, and any promised follow-up. If the work ended badly, address the known problem before proposing another engagement. Record what has actually changed.
Confirm fit and ownership
Check whether the service you now offer matches a current need. Choose one person on your team to own the conversation and check for active discussions with colleagues.
Keep contact choices visible
Check requests to stop, pause, or use a specific channel before outreach. Mailchimp frames its re-engagement guidance around subscribed contacts and relevant content. Verify eligibility for the channel you plan to use; a past purchase alone is not a channel preference.
Verify the reason to reach out now
Use a date or need the client shared, a follow-up you promised, or a confirmed change that relates to your work. Record the source and date so the next owner can check it.
Use agreed follow-up dates
A buyer-requested review after a launch gives you a specific topic. Keep the date linked to that request. Avoid applying a fixed six-month wait to every former client.
Check role changes
Confirm the current role and employer before writing. Keep prior project context attached to the old engagement and avoid sharing its confidential details with a new company.
Review the available CRM history
Check activity links, sync status, and access before relying on a timeline. In Lumenbase, LumenScore depends on workspace scoring rules. Read those rules and the recorded activity before interpreting a low score as a reason to contact someone.
Use one real detail and one clear next step
Keep the message specific enough that the recipient can place the conversation. Use a small request and leave room for their plans to have changed.
Fictional message example Subject: Support review after the portal launch Hi Jo, When we wrapped up the portal work, you asked us to check back after the September launch. Would a short support review be useful now? If the timing has changed, let me know and I will update our notes. Alex
Check every detail
Confirm names, dates, project references, and any claimed result against the record. Remove details you cannot verify. Use only information that is suitable to share with this recipient.
Decide what happens after sending
Record the message and owner. A request to return later gets an agreed date; a decline or stop request updates the contact instructions. Handle delivery failures before another attempt.
Keep new work separate
When a current need is confirmed, create or qualify a new opportunity linked to the existing company and contacts. Preserve the original engagement outcome so past revenue and new pipeline remain distinct.
Measure replies, opportunities, and completed work separately
Define the group, time period, and outcome before comparing results. A reply can be a decline, a timing update, or interest in a new project. Count those outcomes separately.
Show counts beside rates
In a fictional group of 20 contacted accounts, 5 human replies give a 25% account reply rate. If 2 accounts have a confirmed new need, the opportunity rate is 10% of contacted accounts. Those figures describe this example only.
Track revenue when it is earned
Record proposals, signed work, and recognized or collected revenue using your reporting policy. Keep repeat projects, renewals, and expansion distinct. A conversation or quoted amount is not proof of new revenue.
Test the workflow before rollout
Use sample records to check ownership, history access, contact exclusions, dated reminders, and reporting. If you use automated outreach, test reply and stop-request handling before enrolling clients. Confirm which steps still need manual review.
Frequently asked questions
Sources
Sources checked on 19 September 2026. Examples are fictional; checklists are suggested workflows.