iMessage + RCS Joint Number Screening: Building a Multi-Channel Message Reach Pipeline for the US and Canadian Markets

The United States and Canada are two of the most valuable overseas markets, with iOS and Android user shares nearly evenly split. iMessage, as the ultimate messaging channel within the Apple ecosystem, directly reaches the trusted inbox of iPhone users, while RCS (Rich Communication Services) covers Android native messaging apps with read receipts and high delivery rates. Screening numbers on a single channel only reaches a portion of users. iMessage + RCS joint number screening has become the inevitable choice for maximizing message reach in the US and Canadian markets. This article details how to build a complete pipeline using KK-DATA: “Number Generation → Dual-Platform Detection → Data Deduplication → Export,” helping you efficiently filter a high-activity, high-reach number library.

---

Why Do the US and Canadian Markets Need iMessage + RCS Joint Number Screening?

• iOS vs. Android Share: The iPhone market share in the US is approximately 55%–65%, and nearly 50% in Canada. Screening only for iMessage misses a large number of Android users, while screening only for RCS fails to cover the Apple ecosystem.
• Message Delivery Rate Differences: iMessage is enabled by default on Apple devices and pushes messages directly; RCS replaces traditional SMS with enterprise-grade rich media capabilities but requires carrier support and user activation. Joint screening allows you to obtain “enabled/valid/active” labels for each channel separately.
• Avoiding Single-Channel Failure: Many overseas marketers screen only for iMessage, causing Android users to be ignored and reducing reach rates by over 40%. RCS detection fills this gap.

Core Conclusion: To achieve full user coverage in the US and Canadian markets, you must have both iMessage and RCS number lists. Joint screening is not an “either-or” choice—it is two parallel data pipelines.

---

Pipeline Design for Joint Number Screening

The pipeline consists of four steps:

1. Number Generation: Obtain the raw list of numbers to be screened (random generation, prefix generation, custom import).
2. Multi-Platform Detection: Submit iMessage detection tasks and RCS detection tasks separately in the KK-DATA console. The two tasks are independent and can be submitted in parallel.
3. Data Deduplication: Import the results from both detection tasks into a deduplication repository, automatically merging identical numbers to avoid duplicate purchases or sends.
4. Export: Export number files with different labels based on subsequent actions (bulk sending, direct messaging, retargeting).

Core Principle: Submit tasks by platform step by step, and manage results centrally. Do not mix iMessage and RCS numbers in a single task (currently KK-DATA supports separate detection), because the detection logic, pricing, and returned labels differ between the two platforms.

Distinguishing iMessage and RCS Detection Time Windows

• Submit iMessage detection first: iMessage detection is usually faster (approximately 10,000–20,000 numbers per second) and requires finer activity granularity (you can specify 7/15/30-day activity windows). After obtaining valid iMessage numbers, you can prioritize reaching iOS users.
• RCS detection can be submitted simultaneously or later: RCS requires interaction with the carrier side and is slightly slower. If the number volume exceeds 100,000, it is recommended to submit in the afternoon or during off-peak hours. The two tasks do not interfere with each other; the console will display progress separately.

Typical Scenarios for Multi-Channel Screening

Scenario	Applicable Condition	Operation Suggestion
Need both channels simultaneously	Clearly want full iOS + Android coverage	Submit iMessage and RCS tasks at the same time, merge and deduplicate results before export
Prioritize iMessage, then switch to RCS	Limited budget, cover iOS first	Export invalid iMessage numbers → Re-import them for RCS detection to find reachable Android users
Pure verification	Need to confirm if a number is available on both platforms	After separate detection, use the “intersection” logic in the deduplication repository (future field filtering can be used)

---

Step 1: Generate the Number Library to Be Screened

Three ways to obtain numbers, all free (only number screening charges per record):

• Global Random Number Generation: KK-DATA supports random generation for 240+ countries/regions. Select “United States (+1)” or “Canada (+1)” to batch generate random numbers. Suitable for initial testing.
• Global Prefix Generation: Generate numbers by country, carrier, MVNO, state prefix, etc. For example: California 310/818 prefixes, MVNOs like Ting, T-Mobile prefixes, etc.
• Custom CSV Import: Import existing number libraries or numbers exported from other platforms directly via CSV or TXT.

How to Determine Target Prefixes for the US and Canadian Markets

• By state/city prefix: Each US city has fixed prefixes (e.g., New York 212, Los Angeles 310). You can extract them from local mobile number lists or public prefix databases.
• MVNO prefixes: Numbers from MVNOs like Google Fi, Tello, Ultra Mobile tend to have higher activity and are less likely to be flagged as spam. Including these prefixes is recommended.
• Historical data optimization: If you have run screening before, you can extract prefixes from historically valid numbers for expansion. KK-DATA does not provide historical data export, but you can organize it yourself.

---

Step 2: Submit iMessage and RCS Number Screening Tasks

After logging into the KK-DATA Application Console, follow these steps:

1. Click “Create New Detection Task”.
2. Select the platform: iMessage or RCS.
3. Upload the number file (supports txt/csv, one number per line with country code, e.g., +1617xxxxxxx).
4. Choose the detection type:
   • iMessage Detection: Includes “Enabled Detection (whether registered for iMessage)”, “Activity Detection (optional 7/15/30-day activity window)”, “Gender Identification (based on avatar)”, “tgid/wsid export”.
   • RCS Detection: Includes “RCS Valid (whether RCS protocol is supported)”, “Carrier Identification”.
5. The system automatically calculates the estimated fee. Confirm and submit the task.
6. Once the task is completed, results will be pushed to your console. You can also receive notifications via Telegram (requires prior binding).

Understanding Detection Types and Fee Estimation

• iMessage Detection: Checks whether a number has iMessage enabled and returns the number of recent active days (e.g., active within 7 days, active within 30 days). Fees are charged per record, and prices may vary slightly by country/region. Refer to the real-time price in the console. Enabled detection is usually cheaper than activity detection.
• RCS Detection: Checks whether the carrier of the number supports RCS and whether the number has RCS enabled. Some carriers (e.g., Verizon, T-Mobile) have fully enabled RCS, while AT&T supports it partially. Results include “Valid”, “Invalid”, and “Unknown” statuses.
• Pre-submission Estimation: The page will show “This task is estimated to deduct xx USDT”. Ensure sufficient balance before submitting.

Task Notifications and Result Retrieval

• After task completion, you can view the detailed results directly in the console. Supports filtering by status (Valid/Active/Invalid).
• Export formats: CSV, TXT. CSV includes the following fields: Number, Detection Type, Status, Active Days (iMessage), Gender (iMessage optional), Carrier (RCS optional), Detection Time, etc.
• It is recommended to export the result file immediately and back it up locally or in the deduplication repository.

---

Step 3: Export and Data Deduplication

After joint screening, the results from the two tasks may contain duplicate numbers (the same number was tested for both iMessage and RCS). Using them directly will cause duplicate charges (if sending subsequent messages) and confuse reach records.

Using the Cross-Task Data Deduplication Repository

KK-DATA provides a “Data Deduplication Repository” feature. Follow these steps:

1. Find “Deduplication Repository” in the left navigation of the console.
2. Upload the iMessage detection result file (CSV).
3. Upload the RCS detection result file (CSV).
4. The system automatically compares numbers, generates a unique number list, and retains multi-platform statuses for each number (e.g., “iMessage valid, RCS valid”).
5. Export the deduplicated file (you can choose to “keep only one status” or “merge all statuses”).

Deduplication Repository Record Retention Period: Usually 30 days. It is recommended to complete deduplication and export within 1 week of task completion.

Best Practices for Export

• Export different labels based on different subsequent actions:
  • For iOS bulk sending, export numbers labeled “iMessage valid + active”.
  • For Android bulk sending, export numbers labeled “RCS valid”.
  • For full dual-channel reach, export numbers labeled “iMessage valid OR RCS valid” (after deduplication).
• Keep fields complete: When exporting, check all required fields (status, active days, gender, etc.) to facilitate future segmentation.

---

Best Practices: Tips to Improve Joint Screening Efficiency

1. Submit two tasks in parallel: iMessage and RCS do not conflict; they can be submitted simultaneously. If you have 100,000 numbers, split them into two tasks of 50,000 each, or submit the same batch to both tasks (recommend batching to stay under the single-task limit of 1 million).
2. Set activity windows reasonably: What is the default iMessage activity window? The console allows you to choose “Recently Active (7 days)” or “Normal Active (30 days)”. For marketing purposes, it is recommended to select active within 30 days to avoid accidentally excluding potential users.
3. Use prefix generation to narrow down the range: Do not blindly generate millions of random numbers. First, use statistics or historical data to identify target prefixes (e.g., top 10 city prefixes in the US and Canada), then generate numbers. This can increase screening hit rates by 30%–50%.
4. Combine gender identification to optimize content: iMessage detection can include gender identification (based on avatars). After export, you can tailor copy for males and females to improve response rates.
5. Clean the deduplication repository regularly: Periodically export data from the deduplication repository and then clear it to avoid redundant records affecting performance.

---

Important Notes: Balance, Top-up, and Fraud Prevention

• Pay per record, no subscription: KK-DATA uses a balance top-up + pay-per-record model. The minimum top-up is approximately 50 USDT (USDT-TRC20). Balance updates automatically upon receipt.
• Insufficient balance cannot submit tasks: Before submitting a task, the console will show the estimated fee. If your balance is insufficient, you need to top up first. It is recommended to maintain at least 100 USDT balance to handle batch tasks.
• Official customer service channel: Support is only provided via the Telegram account @kkdata_robot. Any other account claiming to be “KK-DATA customer service” is fraudulent. If in doubt, please visit Contact Us for verification.
• No guaranteed pricing: Detection prices may fluctuate based on platform costs. Please refer to the real-time display in the console. See Billing Information for details.

---

Frequently Asked Questions

Q: Can iMessage and RCS detection be performed simultaneously?
A: Yes, you can submit two separate tasks (one for iMessage, one for RCS). The two tasks do not conflict, and the results can be merged and deduplicated. The console supports up to approximately 1 million numbers per task. It is recommended to upload in batches.

Q: How can I distinguish the status of the two channels after joint screening?
A: The exported results will include the detection type (iMessage or RCS) and corresponding status (e.g., enabled/valid/active/invalid) for each number, making it easy to filter by platform.

Q: Does RCS detection require the number itself to have RCS enabled to be identified?
A: RCS detection will determine whether the carrier of the number supports the RCS protocol and whether the number has RCS enabled. The specific detection results are subject to the console output.

Q: If a number is valid in both iMessage and RCS detection, will I be charged twice?
A: Yes, each detection is billed independently. However, it is recommended to use the “Data Deduplication Repository” function to merge and deduplicate the two detection results before export, to avoid duplicate purchases or sends.

Q: Which markets are suitable for joint screening?
A: It is especially suitable for markets where iOS and Android user shares are close, such as the United States, Canada, the United Kingdom, Australia, etc. In these markets, iMessage and RCS cover different user groups, and joint screening can maximize message reach.

---

Experience it now: Log in to the KK-DATA Console to create your first joint screening task. For assistance, contact official customer service @kkdata_robot. For more documentation, please visit Documentation.