Short answer
Bouncer is a list-cleaning and email-verification option. SoftSync adds the operating context around it: where the list came from, who reviewed it, which records were suppressed, and what the seller should do next. Start with a sample rather than assuming a provider result is universally accurate.
The situation
A small team wants to send a useful campaign without building a deliverability department. It needs a simple gate before sending, and it needs the rejected records to stay understandable when someone asks why a prospect was not contacted.
Connected workflow
- Import a small prospect sample into a SoftSync group with CSV import.
- Validate the sample in Bouncer and compare result categories with the original source.
- Bring back status, reason, source, and checked-at date through a verified export, API, or bridge.
- Use a view for “approved,” “risky,” “unknown,” and “do not contact.”
- Review the approved group before using email campaigns.
Human control and boundaries
Catch-all and unknown addresses require judgement. A clean result does not establish a lawful basis for outreach, good message quality, or a healthy sending domain. Keep data-processing and retention decisions with the team that owns the campaign.
What to measure
Measure invalid and unknown rates by list source, manual-review rate, duplicate suppression, bounce rate, and time from import to approved campaign.
Sources and further reading
FAQ
Is Bouncer an outbound sequencer?
No. It belongs before the sending step. SoftSync can hold the approved audience and the resulting relationship context.
Why keep rejected addresses in SoftSync?
Keep only the minimum information needed for suppression and auditability. The reason matters when the same address appears in another import or a future request.