Million-Level Bulk Number Screening SOP: Standard Operating Procedure from Task Splitting, Notification to Export

When your overseas marketing team needs to verify hundreds of thousands or even millions of Telegram or WhatsApp numbers, traditional manual operations or scattered scripts simply cannot cope. Task timeouts, wasted balance, chaotic result files—once these pain points appear, they often mean marketing plan delays and cost overruns. Million-level bulk number screening SOP (Standard Operating Procedure) is precisely designed to solve these problems. This article will take the KK-DATA platform as an example to provide a complete operational process from task splitting, notification settings to export, helping you turn large-scale number screening into a repeatable, high-efficiency assembly line.

What is million-level bulk number screening? Why do you need an SOP?

Million-level bulk number screening refers to processing 100,000 to 1 million numbers in a single batch and detecting their activation status, activity, gender, etc. on multiple platforms such as Telegram, WhatsApp, iMessage. Without a standard process, common pitfalls include:

• Task timeout: Submitting too many numbers at once leads to long processing time or even failure.
• Wasted balance: Repeatedly checking the same batch of numbers, or paying unnecessary fees for inactive numbers.
• Chaotic results: Output files from different tasks and platforms are mixed; unable to quickly filter out effective targets.

A clear SOP helps you:

• Control the scale of each round of tasks to improve success rate.
• Save balance using deduplication mechanisms.
• Monitor progress in real-time via automatic notifications without constantly refreshing the console.
• Unify export formats for subsequent marketing use.

How to reasonably split million-level screening tasks?

Splitting is the first and most critical step in the million-level bulk number screening SOP. A reasonable splitting method ensures that single tasks are completed stably while maximizing cost-effectiveness.

Split by platform and detection type

Different platforms have different unit prices (Telegram, WhatsApp, iMessage, RCS, etc.), and detection types (active, valid, activity, gender identification, tgid/wsid export) also have their own pricing. It is recommended to group numbers by platform and submit only the required detection items for the same batch of numbers in one task.

For example, if your number library contains both Telegram and WhatsApp segments, do not mix them in one submission—submitting by platform not only facilitates budget management but also directly distinguishes data sources in the result files.

Split by number source or country code

Numbers generated by the global number generation function (KK-DATA supports random or prefix-based generation for 240+ countries/regions) often come from different countries. Detection speed and success rates may vary by country. It is recommended to first group numbers by country or prefix, keeping each group within hundreds of thousands to avoid affecting platform response speed due to excessive task size. This is particularly important in a large-scale screening SOP—because consecutive prefixes often have similar detection patterns, grouping can also help quickly locate abnormal prefixes.

Use the deduplication warehouse to avoid double billing

Large-scale screening often requires multiple rounds, and the same number may appear in different batches. KK-DATA provides a data deduplication warehouse: it automatically filters out already-checked numbers across tasks without deducting balance again. This means you don’t need to write your own deduplication scripts before submitting new tasks; just enable the deduplication option when creating a task, and the system will automatically skip already-checked records.

How to set up task notifications to know screening completion status in time?

The completion time of million-level screening tasks can range from a few minutes to several hours. Constantly manually refreshing the console is obviously unrealistic. KK-DATA supports sending task completion notifications via a Telegram bot: after binding your Telegram account in the console, whenever a screening task is completed, the bot will proactively push a message containing a summary of the task (number processed, valid count, balance consumed, etc.).

Setup steps:

1. Log in to the console and go to notification settings.
2. Click “Bind Telegram” and jump to the official bot.
3. Send /start and obtain the binding code.
4. Enter the binding code in the console.

After that, all task completion statuses will be automatically notified to your mobile phone, eliminating the need to stay in front of the computer. This is an important part of improving efficiency in the large-scale screening SOP.

Complete operational steps for million-level bulk number screening

The following steps are based on the KK-DATA platform; you can directly apply this set of SOP.

Step 1: Generate or upload target numbers

• Use global number generation: In the console, select “Number Generation”, choose a country, prefix, or random generation. Generation is free; you can generate any number of numbers on demand (recommended to generate no more than 500,000 each time).
• Import custom CSV: If you already have your own number list, you can import it via CSV or TXT file upload. The platform automatically parses and counts the numbers.

Regardless of the method, the platform will provide a preview of the numbers after generation/import. After confirming correctness, proceed to the screening module.

Step 2: Submit a screening task and estimate fees

1. Go to the “Screening Tasks” page and click “New Task”.
2. Select the source (generated numbers or uploaded CSV).
3. Choose the platform and detection type (e.g., Telegram active + activity + gender identification; or WhatsApp valid + wsid export).
4. The system will automatically calculate the estimated fee based on the selected type (displayed as count × unit price). Confirm that the balance is sufficient at this point.
5. You can enable the “Data Deduplication” switch to avoid double billing.
6. Submit the task. The task enters the queue, and the platform starts processing.

Step 3: View results and export

After the task is completed (you can be notified via Telegram), enter the task details to view the statistics panel:

• Total count, processed count, valid/active count, activity count, gender distribution, etc.
• If tgid/wsid export was selected, an export button will appear.

Supports CSV and TXT format export. It is recommended to name files by platform and detection type, e.g., telegram_active_30day_20250321.csv. After export, the data can be used for the next marketing step (adding to communities, bulk messaging, etc.).

Notes and best practices for large-scale screening

Task interruption due to insufficient balance

Million-level tasks require continuous deduction of fees until completion. If the balance runs out midway, the task will be paused, and part of the processed data may be lost. Ensure sufficient balance is reserved before submission; if the budget is limited, it is recommended to split into several smaller tasks and submit them in batches.

Reasonable setting of activity time window

Telegram activity detection supports 7-day, 15-day, 30-day, etc. time windows. For large-scale screening, if your marketing cycle is short (e.g., reach within 7 days), selecting the 7-day activity window will suffice. This allows you to filter out highly active users while reducing consumption (since checking 7 days is faster and cheaper than 30 days). For long-term operations, the 30-day window is more reliable.

Task concurrency limits

Submitting multiple tasks at the same time may cause queue waiting. It is recommended to submit tasks in order of priority, or stagger peak hours (e.g., submit at night). The KK-DATA console displays the current queue status of tasks.

Data security

All uploaded numbers and data are used only during the task; the platform promises not to retain users’ original numbers. After exporting, it is recommended to promptly delete redundant local files.

Frequently Asked Questions

Q: What is the maximum number of numbers supported in a single screening task?
A: Approximately 1 million. However, for stability and speed, it is recommended to split tasks exceeding 500,000 numbers by country or platform.

Q: How do I receive notifications after a task is completed?
A: You can set up Telegram notifications in the console; the bot will automatically send a completion message when the task finishes.

Q: Is the screening fee charged per number or per task?
A: Per number detected. Different platforms and detection types have different unit prices; please refer to the real-time prices in the console. No subscription plans.

Q: If a number has already been checked, can I avoid double billing?
A: Yes. The platform provides a data deduplication warehouse that automatically filters out already-checked numbers across tasks to avoid duplicate balance deductions.

Q: Which platforms are supported for detection?
A: Currently supports Telegram (active/valid/activity/gender identification/tgid export), WhatsApp (valid/wsid export), iMessage, RCS, etc.

---

We recommend that you log in to the console immediately and start your first round of screening according to the million-level bulk number screening SOP in this article. If you encounter any issues or need suggestions on splitting plans, you can get real-time help through the two-way customer service Telegram, or check the documentation for more feature details.

👉 Log in to the console to start screening
Two-way customer service: https://t.me/kkdata_robot
Documentation: https://docs.kkdata.cc/