Salesforge Email Validation Credits: What They Cover and How to Verify the Rest

Salesforge's included validation credits cover only part of a full sequence, so verify your CSV before you upload it. On its pricing page today, Pro lists 300 email validation credits a month against 1,000 contacts in active sequences, and Growth lists 1,000 credits against 10,000 contacts. Run the whole file through an email verifier first, upload only the valid rows, and save Salesforge's credits for leads you add one at a time. You can check a sample free at /verify.

Estimate your bounce rate before sending →

What Salesforge includes

From the Salesforge pricing page, read on 9 November 2026:

Plan	Active contacts in sequence	Emails a month	Email validation credits a month
Pro	1,000	5,000	300
Growth	10,000	50,000	1,000

The page defines validation credits as the "number of credits you can use each month to validate emails in your lists." On Growth, it says you can buy more of each in the app. Prices on the page change with billing period and add-ons, so check it directly for the current figure.

The page also says you can upload contacts "via .CSV or connect a Google Sheet."

The gap, in plain numbers

Plan	Contacts a full sequence can hold	Included validations	Contacts left unchecked if you fill it
Pro	1,000	300	700
Growth	10,000	1,000	9,000

That assumes every contact is new each month. If your sequences turn over faster, the gap is bigger.

You have two options: buy more credits in the app, or verify the list before it gets there. Which is cheaper depends on your volume. If you verify more than a few thousand leads a month across Salesforge and other tools, a flat verification plan usually is; put your numbers into the verification cost calculator.

Why verification matters more in a sequencer

Cold email sequences send from inboxes you set up yourself, usually on secondary domains. Bounces hurt those inboxes directly:

• Mailbox providers notice. A high share of unknown-user bounces is a sign of a bought or scraped list.
• Your inbox provider notices. Google Workspace and Microsoft 365 can limit or suspend accounts that bounce a lot. See Google Workspace suspended for cold email.
• Bounces repeat. In a multi-step sequence, a bad address can be tried again on each step unless the first bounce stops it.

Our bounce rate thresholds by platform guide lists the limits several sequencers publish. Aim to stay well below the lowest limit any of your tools publish.

How to verify before uploading

1. Export your leads to one CSV

Wherever they come from (Apollo, Clay, Sales Navigator, a scraper, your CRM), get them into one file. Add a "source" column so you can trace bounces back later. Find which list source caused bounces shows why that's worth the extra column.

2. Clean the file

• Remove duplicates with the duplicate email remover.
• Fix common domain typos with the email typo corrector.
• Remove role addresses like info@ and sales@ with the role-based email filter, unless you mean to write to them.
• Limit how many people you contact at one company with limit contacts per company. Ten people at the same company getting the same email on the same day is a common way to get reported.

3. Verify

Upload the file at /verify. You get three groups:

Result	Meaning	What to do in Salesforge
Valid	The mail server confirmed the mailbox	Upload to your main sequence
Risky	Reachable but not confirmable, usually a catch-all domain	Upload to a separate, smaller sequence
Invalid	Rejected, no mail server, or broken syntax	Don't upload; keep as suppression

4. Upload by CSV or Google Sheet

Upload the valid file as you normally would. If you work in Google Sheets, paste the valid rows into the sheet you connect.

Keep the column names simple: email, first name, last name, company, plus any personalization columns. Clean CSV columns before import covers the common mapping problems, and personalization lines from CSV columns covers custom fields.

5. Run the risky group separately

Risky leads are mostly on catch-all domains, where the company's server accepts every address. Some of those mailboxes are real and some aren't. Handle them like this:

1. Create a second sequence with fewer daily sends.
2. Start it after the valid sequence has been running for a few days.
3. Check bounces after the first step. If they are high, pause it.

You can check a domain list yourself with the bulk catch-all checker. What is a catch-all domain explains the trade-off in more detail.

Using Salesforge's own credits wisely

Verifying before upload doesn't make the included credits useless. Good uses for them:

• Leads you add by hand, one at a time, between bulk uploads.
• Leads from a Google Sheet that someone else keeps updating, if you can't control when rows are added.
• A spot-check on a file someone tells you is "already verified."

Before you hit send

Bad data is only one cause of bounces. Check the rest of the setup:

• Domain records. Make sure SPF, DKIM and DMARC are in place on every sending domain with the bulk email authentication checker.
• Domain readiness. The cold email domain checker flags common setup problems.
• Daily volume. The cold email volume calculator works out how many inboxes you need for your target. Cold emails per day per inbox explains the usual limits.

After the campaign

1. Export bounces and unsubscribes from Salesforge.
2. Merge them with your invalid rows using the suppression list merger.
3. Check that suppression file against every new list before you verify it. There's no point checking an address you already know is dead.
4. Re-verify any list older than a few weeks before you reuse it. Addresses decay as people change jobs.

A one-page checklist

Before each upload to Salesforge:

1. Merge all lead sources into one CSV with a source column.
2. Remove anyone on your suppression list.
3. Dedupe, fix typos, drop role addresses you don't want.
4. Cap contacts per company.
5. Verify the file.
6. Upload valid rows to the main sequence.
7. Upload risky rows to a smaller, later sequence, or hold them.
8. Add invalid rows to suppression.
9. Check SPF, DKIM and DMARC on every sending domain.
10. After the first step sends, check the bounce rate before the next step goes out.

It takes a few minutes per list and protects inboxes that took weeks to warm up.

Quick answers

• Can I skip verification if my lead tool says the emails are verified? You can, but a second check right before sending catches addresses that went bad since. It is cheap insurance for your inboxes.
• Does a valid result guarantee no bounce? No. It means the server confirmed the mailbox at the time of the check. Bounces can still happen later, which is why you verify close to sending.

Verify your next Salesforge list

Upload a sample at /verify. The first 100 checks are free with a Google sign-in, no card.

Pro, $39 a month: Unlimited email verification.* Never metered, never cut off. See pricing.

*Fair use: the first 100,000 checks a month at full speed, then slower, never cut off.

More: Smartlead list verification, Instantly and Smartlead list hygiene checklist, email verifier for cold email.