Contact lifecycle actions: archive vs GDPR erase vs hard delete
Lifecycle actions are the “point of no return” tools for contact operations. They are intentionally gated and should be used with clear intent.
At a glance
- Archive: remove from active contact lists and segments; history stays; future outbound calls are blocked.
- GDPR erase: redact PII, mark deleted, add to DNC; history stays but the person is anonymized.
- Hard delete: permanently remove the contact, only allowed when there is no history and backend permits it.
Watch out: lifecycle actions are not a “cleanup” hobby
If multiple operators use lifecycle actions inconsistently, reporting breaks and compliance risk increases. Assign an owner for archive/GDPR decisions.
Archive a contact
Archive is for operational containment:
- remove from active use
- keep campaign/call history for audit and learning
- prevent future outbound attempts
GDPR erase (redaction)
GDPR erase is for privacy compliance:
- PII is removed/redacted
- history remains for operational integrity
- contact is added to DNC to prevent future outreach
Hard delete
Hard delete is the strictest action:
- contact is permanently removed
- only allowed when there is no campaign/call history or backend blockers
When to use which
- Use Archive when the contact should not be contacted again but you want history intact.
- Use GDPR erase when policy requires personal data removal.
- Use Hard delete only when policy and backend allow it and there is no history.
Next: connect lifecycle to DNC and segments
Lifecycle and DNC decisions affect campaigns. Keep them consistent.