# How to Decide What to Send vs Hold

There is no single “always correct” export.

Deliverability is **dynamic**.\
It changes based on timing, copy, offer, list quality, ESP mix, and sending infrastructure.

CSVgo gives you structured options.\
Your job is to deploy them intelligently.

***

### Start With a Baseline Strategy

If you want the safest default:

**Send first**

* Deliverable (Outlook Removed)

**Hold initially**

* Outlook-based deliverables
* Risky catch-all emails

This approach protects sender reputation while letting you validate performance signals quickly.

***

### When to Send Outlook Emails

Outlook emails are not bad.\
They are just more sensitive.

Send them when:

* Your domains are warmed
* Your copy is already converting
* You have stable inbox placement
* You are pacing volume properly

Practical approach:

* Start with Gmail and Others
* Add Outlook gradually
* Monitor replies and bounces closely

***

### When to Test Catch-All Emails

Catch-all emails often:

* Receive fewer inbound emails
* Reply better when messaged correctly
* Perform differently depending on timing and offer

Best practice:

* Test catch-alls in controlled batches
* Separate them from core campaigns
* Compare reply rates against standard deliverables

Do not assume risk. Measure it.

***

### What to Always Hold or Segment

Hold or isolate leads when:

* Launching brand-new inboxes
* Testing aggressive copy
* Sending high daily volumes
* Running cold infrastructure for the first time

Segmenting reduces noise and protects learning quality.

***

### Testing Is Not Optional

Deliverability is affected by:

* Time of year
* Market saturation
* Offer relevance
* Copy tone
* Domain age
* ESP-specific throttling

This means:

* What works today may not work next month
* What fails once may work later

CSVgo gives you the structure.\
Testing gives you the truth.

***

### A Simple Testing Framework

1. Start with Deliverable (Outlook Removed)
2. Measure opens, replies, and bounces
3. Introduce Outlook in small batches
4. Test catch-alls separately
5. Scale what performs, pause what doesn’t

Repeat continuously.

***

### Key Takeaway

CSVgo does not force decisions.\
It gives you clean data and control.

The teams that win are not the ones avoiding risk.\
They are the ones **testing it deliberately**.