Prepare input
Keep the source identifier, use one record per row and verify the format with a small sample before a larger task.
Use NumSift to classify phone records by available RCS, carrier and device-capability signals before rich-message planning. Interpret RCS capability by carrier, device and observation time; provisioning changes can move a number between RCS and SMS fallback states.

Accurate data. Global reach.
PRODUCT SCOPE
RCS capability check for classify phone records by available RCS, carrier and device-capability signals before rich-message planning.
Keep the source identifier, use one record per row and verify the format with a small sample before a larger task.
This page focuses on RCS capability signal, Carrier and line type, Reachability classification, Device compatibility, rather than applying unrelated fields from another product.
Export task time, unknown values and exception states so the result remains reviewable.
SUPPORTED CAPABILITIES
Fields can vary by task. Select only the capabilities the workflow needs and validate a small batch before submitting a full dataset.
Classify returned RCS capability signals by check time and keep SMS fallback records visible.
Add available carrier and line-type data without replacing the source phone number.
Keep reachable, unreachable, unknown and exception states separate instead of forcing a binary result.
Separate available device-family or compatibility signals from records where the device cannot be determined.
RESULT GROUPS
Every result group should remain linked to its source record. Unknown, empty and task-exception values should stay separate instead of being converted into a negative result.
RCS state, fallback state and observation time
carrier, line type and network region
reachability state, check time and exception code
device signal, compatibility and unknown state
THREE-STEP WORKFLOW
Preserve source values, normalize obvious format differences, remove exact duplicates and prepare a small sample.
Choose the required items from RCS capability signal, Carrier and line type, Reachability classification, Device compatibility; avoid adding fields the decision will not use.
Check field meaning, task time, unknown values and exceptions before importing structured output into another system.
PRACTICAL USE
Create a dedicated RCS dataset for rich-messaging readiness, with source identifiers and task timestamps kept beside every result.
Use rcs capability signal, carrier and line type, reachability classification, device compatibility as separate review fields so one missing value does not erase the rest of the record.
Export the original identifier, selected result fields, unknown values and exception states together so another team can reproduce the decision.
FAQ
It explains how to classify phone records by available RCS, carrier and device-capability signals before rich-message planning, including the supported signal groups, input preparation, result interpretation and review boundaries.
Prepare authorized phone or account records. Keep one source record per row, preserve the original value and normalize obvious formatting differences before a larger task.
This product page covers rcs capability signal, carrier and line type, reachability classification, device compatibility. The exact fields available depend on the selected task and may include unknown or empty values.
Use them to separate RCS-capable signals from SMS fallback and unknown records. Check task time, field meaning and exception states before importing results into another system.
No. Screening organizes returned technical or account signals. It does not prove a person's identity, create marketing consent or replace the rules that apply to the source data.