How to Use BAND Number Checker for Bulk List Checks

BAND lives in a specific corner of the messaging world: Korean community commerce. Group buys, seller circles, neighborhood networks — the audience that coordinates inside Naver BAND is the audience Korean-market campaigns want, and everyone else on the list is reachable somewhere else. The BAND Number Checker splits a phone list into those two groups. This page is the operating procedure: file prep, the check itself, reading what comes back, and routing each slice.

Quick answer

Normalize the numbers to E.164, upload with a record ID per row, run the check, export. Each row returns a status — on BAND, valid but not on BAND, invalid, or unknown. On-BAND rows feed the community workflow. The valid-but-not-on-BAND rows are your fallback list, and in Korean lists that fallback is usually KakaoTalk or SMS. Invalid rows are repair work; unknowns retry once before any decision.

Step 1: Prepare the file

The Korean-market details decide the result quality more than anything else in this workflow.

Numbers: fix the leading-zero problem

Korean mobile numbers circulate in three shapes: domestic 010-1234-5678, stripped 821012345678 (no plus, no zero), and correct E.164 +821012345678. The stripped shape is the trap — it came from systems that dropped both the plus and the leading zero, and re-adding the zero before the check is what makes those rows checkable. Mixed formats in one file produce avoidable unknowns, so normalize the whole column first. If the list includes non-Korean numbers, normalize those to E.164 too; BAND audiences occasionally include overseas Korean communities, and their numbers are real rows, not noise.

Record ID

One column, text format, whatever your source calls it: customer key, order reference, CRM row. It joins the export back to your system. Without it you get answers with no addresses.

Duplicates: leave them in

The same number under two record IDs is information about your source — a person in two campaigns, a household on one number, an import that ran twice. Let the check report per row and look at the duplicates afterwards. Deleting them pre-check destroys the finding.

Step 2: Run the check

Upload and run. The check works from availability signals and sends nothing to any number — no SMS, no app notification, nothing a recipient could see. A few thousand rows runs in minutes.

Step 3: Read the export

A worked read: 8,900 numbers go in; the export shows roughly 61% on BAND, 26% valid but not on BAND, 9% invalid, 4% unknown. (Illustrative split — Korean consumer lists usually run higher on-BAND than international ones, but it depends entirely on who collected the list.)

The segment teams get wrong is the 26%. It reads like failure and it is the opposite: a quarter of the file is alive and reachable, on channels those people actually open. In Korean-market work the fallback is predictable (KakaoTalk for most consumer segments, SMS where consent covers it), and routing the fallback slice there is what separates a fully-used list from one that only monetizes its majority.

Step 4: Route the export

Step 5: Re-check on the campaign calendar

Group-buy cycles have a rhythm, and the check should follow it: fresh run before each cycle, not once a year. App presence drifts as people change phones and communities migrate. Keep every export with its timestamps — comparing this cycle's on-BAND percentage against last cycle's is the earliest signal you will get that the audience is shifting channels.

What this looks like across a season

A Korean e-commerce team running monthly group buys checks the master list before each cycle. Month one: 61% on BAND. Month three: 58%. Month five: 54% — and the fallback slice has grown by the same points. Nothing dramatic happened; a seller community migrated part of its activity off BAND. Because every export was kept, the team saw the trend instead of discovering it in a flat campaign report. The routing absorbed the shift without a crisis, which is the entire point of keeping the workflow boring and regular.

Mistakes to avoid

• Uploading stripped-format numbers as-is. The missing leading zero is the most common Korean-list defect and the cheapest to fix. Fix it before the check, not in the export.
• Treating valid as on-BAND. Format checks and channel checks answer different questions. Campaigns route on the second one.
• Deleting the fallback rows. A quarter of the file, gone, in a typical split. They are the other channel's campaign list.
• Deciding on unknowns. One retry minimum. Unknown is a queue, not a verdict.

The file-format details (column tables, export fields, the checked_at discipline) are covered step by step in the companion Bulk BAND Number Checker CSV guide. For checking a single number instead of a list, see how to check if a number is on BAND.

FAQ

What number format should Korean lists use?

E.164: +821012345678. The stripped 8210... shape needs the leading zero restored first, or the row risks an avoidable unknown.

Does the check message anyone?

No. Availability signals only — nothing reaches the recipient's device.

What is the difference between valid and on BAND?

Valid means the number is well-formed and live. On BAND means it is likely tied to a Naver BAND account. Campaigns route on the second signal.

Where should the not-on-BAND rows go?

To whichever channel those people use — in Korean consumer lists, usually KakaoTalk or SMS, subject to the consent your list carries.

How often should I re-check?

Before each campaign cycle at minimum, quarterly as a floor. The on-BAND percentage moving between runs is your audience-shift signal.

Related ZelNum pages

• How to Check If a Number Is on BAND for single-number lookups.
• BAND Number Checker — the bulk tool this walkthrough covers.
• Bulk BAND Number Checker: CSV import & result export for file format details.