Complete Guide to Exporting WhatsApp Check Results: CSV Format, Field Descriptions, and Downstream Usage Tips

In daily WhatsApp lead generation operations, number screening is just the first step. What truly determines conversion efficiency is understanding and using the export results. Many users, after completing the check, face the exported CSV file but don’t know what each column represents, how to filter valid numbers, what wsid is useful for, or even encounter data corruption due to encoding issues, wasting the cost of detection. This article focuses on the export of WhatsApp check results scenario, thoroughly explaining the CSV export format and field meanings, and providing a complete guide from data cleaning to downstream usage.

---

Why Pay Attention to the Export Format of WhatsApp Check Results?

The export format determines the speed and accuracy of subsequent data processing. Most number screening platforms offer CSV or TXT formats, among which CSV is widely supported for its versatility—Excel, Google Sheets, and Python Pandas can all read it directly. However, different platforms may have different field definitions and column orders. If you don’t understand the field meanings in advance, you might mistakenly treat invalid numbers as valid ones, or use wsid as an ordinary number, leading to failed bulk messaging and skyrocketing costs.

The core value of understanding the export format lies in:

• Quickly filtering valid numbers to avoid manual verification.
• Using wsid for precise deduplication and API message sending.
• Calculating ROI for different channels by combining detection costs and source fields.
• Providing standardized data interfaces for cross-tool data integration (e.g., CRM, marketing automation).

---

Steps to Export WhatsApp Check Results (Using KK-DATA as an Example)

The following process is based on the operational logic of the KK-DATA platform. Other platforms are similar, with slight differences in field names, but the overall steps are comparable.

Step 1: Submit a WhatsApp Number Screening Task

Log in to the KK-DATA App Console, and select the number source:

• Number Generation: Use the global number generation feature to select a country and number prefix, generating a list of target numbers.
• Batch Import: Upload a CSV/TXT file containing the numbers to be checked (in international format, including country code).
• Manual Input: Enter numbers line by line in a text box (suitable for a small number of numbers).

Before submission, the system will display an estimated cost (charged per check, specific prices can be found on the official billing page). Confirm and submit the task. A single task can support up to approximately 1 million numbers.

Step 2: Receive Notification or Manually Check Upon Task Completion

After the task is completed, you can receive a completion notification via Telegram (you need to bind your Telegram ID in the console). You can also check the status on the “Task Records” page; once the status shows “Completed,” you can proceed.

Step 3: Select the Export Format and Download CSV/TXT

Click the “Export” button on the right side of the task, and choose CSV (recommended) or TXT format. The CSV format includes all field columns for easy subsequent processing; TXT usually contains only the number list, suitable for quick import into bulk messaging tools.

---

Field Descriptions of Export Results: What Does Each Column Represent?

The following field descriptions are based on KK-DATA’s CSV export format. Different platforms may add or remove fields, but the core fields are highly consistent. Understanding these fields is essential for correctly cleaning and utilizing the data.

Number Field: phone / phone_number

The original phone number in international format (e.g., +8613912345678), including the country code. This field is the only unchanged identifier, used for deduplication and matching with external data sources. Note: A few tools may omit the ”+” sign or lack the international prefix, so you should unify the format before importing detection data.

Detection Status Field: status / result

Detection result, common enumerated values:

Value	Meaning	Downstream Suggestion
valid	The number has registered a WhatsApp account and is usable	Can be used for bulk messaging, direct messages, group joining, etc.
invalid	The number is not registered on WhatsApp or has been deactivated	Discard directly to avoid wasting sending quotas
unknown	Detection timed out or other anomaly, result uncertain	Recommend rechecking once, or manual spot check
blocked	The number has been banned by WhatsApp (very rare)	Do not use, only for record

⚠️ Note: valid only indicates that the number has a WhatsApp account; it does not guarantee that the user is active or willing to receive messages. For further filtering, you can combine with activity detection from other platforms (e.g., Telegram).

Platform Identifier Field: wsid / whatsapp_id

WSID stands for WhatsApp ID, a unique identifier assigned by WhatsApp to each account, usually formatted as [email protected]. Its main value:

• API Message Sending: When sending messages via the WhatsApp Business API, you can use WSID directly as the recipient, eliminating the need to parse number formats each time.
• Deduplication: The same user may have multiple numbers bound (e.g., one for work, one for personal use). WSID deduplication is more accurate than number deduplication.
• Data Linking: Can be mapped to custom ID fields in CRM.

When WSID is empty: WSID only has a value when status=valid; for invalid or unknown numbers, WSID is empty. If a large batch of numbers has empty WSID after export, first check whether the task correctly selected WhatsApp detection, or if some detection nodes were abnormal, leading to incomplete results.

Additional Information Fields: source, timestamp, cost, etc.

• source: Number source identifier, e.g., generated (generated via KK-DATA), uploaded (manually imported). Can be used to evaluate number quality by source.
• timestamp: Completion timestamp of the detection (UTC/GMT+0), used for recording data timeliness or time series analysis.
• cost: The balance deducted for this number’s detection (unit: yuan or USDT). Can be used for internal accounting, grouping statistics by source.
• error_code (available in some versions): Error code when detection fails, normally not appearing. If it appears frequently, contact customer service @kkdata_cc to confirm service status.

---

What Practical Value Do These Fields Have for My Downstream Work?

Fields are not just for “looking”; they can directly drive operational decisions. Here are three typical scenarios to help you convert data into action.

Use status to Filter Valid Numbers for Direct Bulk Messaging or Private Messages

This is the most common usage. In Excel, filter the status column for valid, then copy the phone number column into your bulk messaging tool. If using a Python script, one line of code does it:

import pandas as pd
df = pd.read_csv('wa_results.csv')
valid_df = df[df['status'] == 'valid']
valid_df['phone'].to_csv('valid_phones.txt', index=False, header=False)

This avoids importing invalid numbers into the messaging system, saving sending costs and reducing the risk of account bans.

Use wsid for Deduplication and Precision Targeting

Suppose you obtain numbers from two different channels, both detected as valid, but they actually belong to the same WhatsApp account (e.g., a person registered two numbers and later swapped one). If you deduplicate only by number, you would think they are two different numbers and send two messages, wasting resources and potentially triggering WhatsApp’s anti-spam policy.

Using WSID for deduplication is more accurate: Compare the wsid of the two records; if they are the same, consider them the same account, and keep only one number for messaging. In CRM, you can map WSID as a custom field for easy API calls later.

Combine cost and source for ROI Calculation

If one source has only a 20% valid rate but a relatively high cost per detection, the overall ROI may be lower than another source with a 40% valid rate. By grouping statistics:

• Group by source, calculate the number of valid numbers, total detection cost, and average cost per number for each source.
• Combine with downstream conversion data (e.g., join rate, reply rate) to evaluate the value of different channels and optimize budget allocation.

---

Common Pitfalls and Best Practices After Export

Even with the correct fields exported, improper operations can still waste data. Below are common pitfalls and solutions.

• Garbled text when opening CSV in Excel: If you double-click the CSV file directly, Excel may open it with GBK encoding, causing garbled Chinese text. Solution: Open the CSV file with Notepad, save it as UTF-8 encoding, then open with Excel; or directly import it into Google Sheets (which automatically recognizes UTF-8). If still garbled, check if the file has been double-encoded (e.g., saved multiple times).
• Accidentally importing invalid numbers into bulk messaging tools: Adding if status == "valid" in your script is a basic requirement. If you use TXT format (only number list), you need to filter valid numbers on the platform before exporting (KK-DATA supports exporting only valid numbers when exporting).
• What to do when wsid is empty: An empty wsid means the number is not registered on WhatsApp. Do not force an empty wsid into API or CRM systems. Also note: Even if status=valid, in rare cases wsid may be null (detection node returned an anomaly). It’s recommended to retry that batch of numbers.

---

How to Batch Process and Integrate These Exported Data?

The exported CSV is not the end but the starting point of a data pipeline. Depending on your tech stack, you can choose the following methods for batch processing.

Quick Filtering with Excel or Google Sheets

• Data → Filter: Filter the status column for valid.
• Copy the phone column to a new sheet for bulk messaging.
• Use a pivot table to group by source and count the number of valid numbers and total cost, quickly calculating ROI.

Batch Cleaning and Transformation with Python (pandas)

import pandas as pd

df = pd.read_csv('wa_results.csv', encoding='utf-8')
# Filter valid numbers
valid = df[df['status'] == 'valid'].copy()
# Create new column: remove number prefix, keep only mobile number (for certain tools)
valid['phone_clean'] = valid['phone'].str.replace(r'^\+?(\d{1,3})', '', regex=True)
# Export new CSV
valid.to_csv('clean_valid_numbers.csv', index=False, encoding='utf-8-sig')

Integration with CRM/Marketing Automation Systems

• Create a “WhatsApp Contact” type in CRM, map fields: phone → phone number, wsid → custom ID, status → validity label.
• Pay attention to deduplication during import: If a record with the same phone or wsid already exists, update or skip.
• Some marketing platforms (e.g., HubSpot, Salesforce) support CSV field mapping preview; match fields one by one.

---

Why Choose a Professional Number Screening Platform for Export Results?

On the surface, all screening platforms offer export functionality, but in practice, the completeness, stability, and consistency of fields vary greatly. Taking KK-DATA as an example, the following features are particularly friendly for downstream data processing:

• Standardized Export Fields: All fields have clear documentation, and you won’t encounter “field name changed” or “a column suddenly missing.” You can always refer to the user documentation for the latest field definitions.
• Support for Large-Scale Exports: A single task can handle up to 1 million numbers; exported files will not be damaged or truncated due to large data volumes.
• Deduplication Repository: Before submitting a new task, deduplicate numbers to avoid repeated detection of the same number, saving costs and reducing redundant data after export.
• One-Stop Pipeline: From number generation, screening, export, to field viewing—all completed within the same platform, eliminating the need to transfer data between multiple tools.

If you want to truly use export of WhatsApp check results to drive lead conversion, rather than just “downloading a bunch of data without knowing how to use it,” we recommend logging into KK-DATA Console and experiencing the complete export process. If you have questions about field meanings or processing methods, feel free to contact official customer service @kkdata_cc.

---

Frequently Asked Questions

Q: All numbers in the exported CSV show as invalid. What could be the reason?
A: Possible reasons include: ① The numbers themselves are empty or not registered on WhatsApp; ② Incorrect number format (e.g., missing country code or area code); ③ Temporary service failure on the screening platform (try again or check the status page). It is recommended to first test a few numbers that you know are valid on WhatsApp to rule out format issues.

Q: After export, the wsid field is empty. What does that mean?
A: An empty wsid indicates that the number has not passed WhatsApp validity detection, meaning the phone number does not have a registered WhatsApp account. Only numbers with status=valid will have a value in wsid. If all valid numbers have empty wsid, please contact customer service to confirm whether the detection nodes are working properly.

Q: The exported CSV shows garbled text when opened in Excel. How to solve it?
A: It is recommended to open the CSV file with Notepad, save it as UTF-8 encoding (choose “UTF-8” format), then open with Excel. Or import it directly into Google Sheets, which usually recognizes the encoding automatically. If still garbled, check if the file has been double-encoded by another tool.

Q: Can I run WhatsApp detection again on the same batch of numbers?
A: Yes. However, it is recommended to first import the numbers into KK-DATA’s “Deduplication Repository.” The system will automatically skip numbers that have already been effectively detected, avoiding duplicate charges. If a number showed as unknown during the previous detection, rechecking can supplement the result.

Q: After export, I want to use wsid for sending messages via the WhatsApp Business API. Do I need any extra processing?
A: No extra processing is required. WSID is a complete ID in the @s.whatsapp.net format; you can directly use it in the to parameter of the API. However, note that when using wsid for sending, the number must have been confirmed valid and not expired in the system. If there is a long interval between two detections, it is recommended to perform a temporary verification first.