Batch Imports to Protect Meta Account Health
What “batch importing” means in Coco
When you import subscribers into Coco for WhatsApp messaging, Coco typically imports them in smaller batches (often 10,000–20,000 contacts at a time) instead of pushing your entire list in one go.
This approach is intentional: it helps protect your WhatsApp sending reputation and reduces the chance that Meta flags your account for unusual or risky activity.
Batch size can vary based on your list makeup, prior sending history, and what Meta is seeing on the account. Coco may adjust batch size and pacing to keep your account stable.
What “account health” means (in plain language)
Account health is a practical way to describe how “trusted” your WhatsApp messaging setup appears to Meta based on signals like:
Message quality signals (blocks, reports, negative feedback)
Engagement signals (replies, reads, continued conversations)
Behavior patterns (sudden spikes in activity, abrupt audience changes)
Compliance confidence (whether the imported audience looks consistent with explicit opt-in expectations)
In short: a healthier account is more likely to maintain stable deliverability and avoid restrictions. A stressed account is more likely to see reduced delivery, slower throughput, or additional review.
This page focuses on why imports are paced. For consent requirements and the proof Coco needs, see the consent-focused pages in your Subscriber Imports section.
Why large, sudden imports can look risky
From Meta’s perspective, a WhatsApp business that suddenly adds (and then messages) a massive number of contacts can resemble high-risk behavior. Even if your list is legitimate, the pattern may still trigger extra scrutiny.
Common risk patterns that can hurt deliverability
Sudden large import (for example, importing 100k+ contacts all at once)
Messaging immediately after a big import without warming up volume
High mismatch between audience and message content (leading to blocks/reports)
Repeated re-import attempts (multiple uploads/changes in a short window)
Lists with mixed intent (contacts who expected SMS/email but not WhatsApp)
If your first sends after an import generate a high rate of blocks or “stop” signals, Meta may reduce delivery quickly. Batching gives you smaller checkpoints so issues are easier to detect and contain.
How batching reduces flags and improves deliverability
Batching is a risk-reduction strategy. It helps your account look consistent and controlled while also giving you time to validate outcomes (delivery, engagement, opt-out rate) before scaling.
What batching does for you
Smoother activity growth: Instead of a sudden spike, your audience grows in visible steps.
Early warning signals: If a batch performs poorly (high blocks/complaints), Coco can pause and adjust before the next batch.
Better learning and targeting: You can start with your most engaged or most recently opted-in segments to establish strong engagement signals.
Reduced operational risk: If there’s a data issue in a file (formatting, duplicates, country codes), it’s isolated to a smaller set.
When possible, import and message your “highest-intent” contacts first (recent purchasers, recent sign-ups, highly engaged segments). Strong early engagement helps stabilize account health before you scale.
What to expect during a batched import
In a batched approach, you’ll see your total imported subscribers increase over time rather than all at once. Coco will typically:
Import an initial approved batch (often 10–20k)
Wait for stability signals (delivery and early feedback patterns)
Continue with additional batches once the account looks stable
Coco begins with a smaller import batch so Meta sees a normal growth pattern and you can validate that the audience behaves as expected.
After the first batch is active, Coco watches for risk indicators like blocks, complaints, and unusually low engagement.
If the first batch looks healthy, Coco proceeds with the next batch. If it doesn’t, Coco may slow down, adjust sequencing, or request changes before continuing.
Why Coco may slow down (even if your list is compliant)
Compliance is necessary, but deliverability is also affected by how the account behaves. Coco may slow or stagger imports when it sees conditions that commonly precede restrictions, such as:
Very large total import size compared to the account’s prior messaging history
Signs the audience may not expect WhatsApp messages (leading indicators in early behavior)
Volatility from recent changes (new number, new business setup, new messaging patterns)
Batching isn’t a penalty, it's protective pacing designed to keep your account able to send consistently over the long term.
FAQ
10–20k is often a practical range: it’s large enough to make progress quickly, but small enough to limit risk if Meta detects unusual activity or if early recipient feedback is worse than expected. Coco may use smaller or larger batches depending on your situation.
Batching can extend the time it takes for all subscribers to be imported, but it typically improves the odds that your WhatsApp setup stays stable and deliverable. A fast import that triggers restrictions usually costs more time than a paced import.
Coco may pause the next batch and help you adjust your approach (for example, changing which segments you import first or slowing initial messaging). This limits impact to a smaller portion of your audience instead of your entire list.
They’re related but not identical. Batch importing controls how your list is added. Warm-up controls how you message after subscribers are available. Together, they reduce risk and help maintain stable deliverability.
Related pages in this section
Step-by-step workflow and what to expect at each stage.
Recommended sending patterns after your subscribers are imported.
Common causes of delays and how to avoid repeated risk during retries.