How to reuse a CSV lead audience without sending duplicate texts
Re-enroll eligible CSV leads in a later campaign while preserving source history, suppressions, appointments and existing campaign activity.
·3 min read
A lead file is often reused after the original campaign finishes. Re-uploading the entire file can create duplicate records or restart outreach to people who replied, booked or opted out since the first upload.
The safer approach is to treat the file as a source cohort: a stable set of contacts with a history. The next campaign should use a reviewed subset of that cohort, not a fresh interpretation of the old spreadsheet.
Preserve the original upload identity
Record the file name, vendor, upload time, batch identifier and original campaign. Keep those values attached to contacts even when their owner or campaign changes. If a vendor sends overlapping files, store its individual lead IDs as well.
This history answers an important question later: which contacts came from this purchase, and what happened to them? It also prevents a reactivation campaign from being reported as a new vendor delivery.
Create the later audience from current CRM state
Filter the original cohort using current facts: opt-out status, last reply, appointment state, active campaign, wrong-number flag and last completed outcome. The old CSV cannot tell you what happened after import.
For example, a 1,000-row file may contain 850 unique usable contacts. A later review might exclude 100 with replies, 40 with appointments, 30 suppressed records and 80 still in an active sequence, leaving 600 candidates. These are illustrative counts; make the categories mutually exclusive before subtracting them.
Preview the new campaign before assignment
Select the eligible group and inspect the intended campaign, first message, sender and timing. The opening should reference the appropriate earlier context instead of pretending the prospect has just submitted a new form.
Decide whether a current campaign must end before a later one starts. Campaign reassignment should be deliberate; two sequences chasing the same lead can create confusing messages and difficult attribution.
Use deduplication as a second guardrail
When a file really must be imported again, normalize numbers and match existing records before creating new contacts. Retain suppression and previous activity. A blank status in the incoming file should not erase a known opt-out.
Review the import summary for new, updated, duplicate, rejected and skipped rows. Keep the rejected-row reason so the team can fix source data without repeatedly attempting the same bad records.
Report reactivation separately
Measure the later campaign's eligible contacts, successful deliveries, new replies and booked conversations independently of the first sequence. Keep the same source attribution, but add a distinct campaign label.
This allows an agency to see whether the vendor's leads produce value over time without giving the new-lead campaign credit for a much later result. It also shows whether repeating outreach is adding useful conversations or simply more activity.
Key takeaways
- →Reuse an upload as a source cohort rather than recreating every record.
- →Build the later audience from current replies, appointments and suppression.
- →Avoid overlapping active sequences.
- →Measure reactivation separately while preserving original attribution.
Put this into practice with Text2Sale
Import leads, create follow-up campaigns, organize replies, and connect texting, calling, and appointments in one workspace.
Frequently asked questions
Does adding a lead to a new campaign mean it is a new contact?
No. It is usually a new campaign enrollment for an existing contact. Preserve the contact identity, prior messages, source history and opt-out state.
What if the CRM only supports another CSV upload?
Export a reviewed eligible subset, confirm its deduplication behavior and test a small import first. Ensure a re-import cannot overwrite suppression or create a second active sender for the same person.