Import Process: What You Send vs. What Coco Does
Overview: the 3-step import workflow
Subscriber imports into Coco AI follow a predictable sequence designed to keep your WhatsApp account in good standing:
You provide compliance proof + double opt-in verification in an email to the Coco Team.
You export and share your subscriber list
Coco imports in approved batches
Imports are intentionally staged. Coco may pause, slow down, or split an import to protect deliverability and WhatsApp account quality.
Typical timeline (at a glance)
Step 1 (Compliance review): typically 1–3 business days once all proof is received.
Step 2 (Export + file validation): typically same day to 1 business day depending on file readiness.
Step 3 (Batch importing): typically 2–5 days depending on list size, batching limits, and approvals.
These ranges are typical; your exact timing depends on list size, proof completeness, and batching requirements.
Step-by-step: what you do vs. what Coco does
Your goal: show that every subscriber you want imported gave explicit permission to receive marketing on WhatsApp, and that your opt-in flow meets double opt-in expectations.
What you send
Proof of consent collection (e.g., screenshots of opt-in forms, checkout opt-in language, sign-up flows).
Double opt-in evidence (what the user sees/does to confirm subscription, plus confirmation messaging where applicable).
Source context: where subscribers came from (e.g., SMS provider list, website pop-up, checkout).
What Coco does
Reviews your materials for WhatsApp marketing eligibility.
Confirms whether your proof is sufficient to proceed and whether any segments must be excluded.
Confirms the safest import approach (e.g., whether extra batching or a slower rollout is needed).
What to expect next
If approved: Coco will confirm you’re cleared to share your file for import.
If changes are needed: you’ll receive a short list of what’s missing or what must be adjusted before importing.
Fastest approvals happen when proof is “copy-pastable”: include the exact opt-in wording users saw and where it appeared (checkout, form, pop-up, etc.).
Your goal: provide a clean, import-ready file containing only the subscribers that meet the approved consent criteria.
What you send
A subscriber export file (most teams use
.csv).Only the approved audience (for example, excluding anyone without verified WhatsApp marketing consent).
Any helpful columns that support review/segmentation (e.g., signup date, source, tags), if available.
What Coco does
Validates the file structure and required fields.
Checks for common issues that can delay imports (duplicates, invalid phone formatting, missing country codes).
Confirms your total import size and proposes the batch schedule.
What to expect next
You’ll receive confirmation that the file is accepted for import or a list of fixes if it isn’t.
If fixes are needed, turnaround is usually quick once you resend an updated export.
This page focuses on workflow and expectations. Detailed file requirements and formatting are covered in your export checklist documentation.
Your goal: let Coco import gradually to protect WhatsApp account health and maximize long-term deliverability.
What Coco does
Imports subscribers in approved batches (rather than all at once).
Monitors results after each batch (e.g., delivery behavior and early quality signals).
Adjusts the pace if needed (speed up, slow down, pause, or request a smaller next batch).
What you do during batching
Be available for quick questions (e.g., confirming a segment or resending a corrected file subset).
Hold off on blasting the entire imported audience immediately—plan a gentle ramp after import completes.
What to expect after each batch
Status update: which batch completed and what’s queued next.
Potential pacing changes: if WhatsApp risk signals appear, Coco may reduce the next batch size.
Readiness for messaging: you can typically message imported subscribers only after they are successfully added in Coco and your sending plan is ready.
Trying to import too much too fast or repeatedly resubmitting problematic lists, can increase compliance and account health risk. Batching is there to protect your ability to send long-term.
What “done” looks like
All approved subscribers are present in Coco AI.
You have confirmation of completion (final batch imported).
You’re ready to move into a post-import sending plan (warm-up, segmentation, and pacing).
Common delays (and what happens)
What you’ll see: Coco requests specific missing items (e.g., exact opt-in wording, screenshots, or confirmation steps for double opt-in).
How it affects timing: Step 1 pauses until the missing proof is provided; once received, review typically resumes within the normal window.
What you’ll see: Coco returns a short list of file issues to correct (e.g., phone formatting, duplicates, missing required fields).
How it affects timing: Step 2 pauses until a corrected file is shared; imports start once validation passes.
What you’ll see: smaller batches, more time between batches, or a temporary pause.
Why it happens: the import schedule is optimized for account health and deliverability, especially on large lists or sensitive segments.
Related docs (recommended next)
Understand what proof is required and what counts as valid WhatsApp opt-in.
Export fields, formatting rules, and a checklist to avoid file rework.
Why Coco uses batches and how the schedule is determined.
What to do once subscribers are in Coco to keep quality high.