Email validation in Salesforge checks whether your contacts' email addresses are valid before you add them to a Multichannel sequence. Learn how Safe, Catch-all, Role account and Unvalidated statuses work, how ESP and Anti-spam software filters apply, how credits are reserved and refunded, and how to use the Email Validation Status condition to route contacts.
How it works in Salesforge
Validate your contacts. You can run validation when you upload contacts or before you add them to a Multichannel sequence. Validation cannot be run on a contact once it has been added to a sequence.
Review the results. Each contact gets a validation status, such as Safe, Catch-all, Role account, or Invalid. Contacts that couldn't be checked appear as Unvalidated under the Unsafe tab.
Choose who to add. By default, Safe and Catch-all contacts are selected. You can change the selection before you add contacts to the sequence.
Re-run if needed. You can re-run validation on only the Unvalidated contacts.
Understanding the statuses
Safe: the mail server confirmed the address exists.
Catch-all: the domain accepts mail for any address, so the specific inbox can't be confirmed. These contacts can still bounce later. For cold outreach, we recommend excluding them or testing them in small batches.
Role account: a shared address such as info@ or sales@.
Unvalidated: the contact could not be checked. Re-run validation on these contacts.
Email provider (ESP) matters too
Validation status and ESP are separate filters. Contacts whose email provider is Anti-spam software (for example Proofpoint or Mimecast) are excluded by default, even when their status is Safe. These addresses are likely to bounce, so we don't recommend sending cold email to them.
Pay only for validated contacts
Credits are reserved when a validation run starts. If part of the run can't be completed, the unused credits are refunded automatically. If you don't have enough credits, the run is rejected before it starts.
Use validation in your sequence
Add the Email Validation Status condition to your Multichannel sequence and run validation when you add contacts. Contacts whose status matches your selected statuses follow the Yes branch. Contacts that don't match, or that were never validated, follow the No branch.
For API users
Validation runs are asynchronous, with statuses completed, partially_completed, and failed, plus finishedAt and failureCode fields. You can fetch partial results while a run is still processing. Insufficient credits return a 402 error.