Article summary
Understand AppShai’s RCS System Check and its three output fields. Distinguish system results from RCS registration, carrier lookup and device-model information before checking a list.
If you need system information associated with a submitted phone list rather than a registration result, consider RCS System Check. AppShai currently returns phone number, system and ID for this task. RCS Validity Check is a separate service returning phone number and registered status.
The word “system” can sound broader than the result actually is. One returned value does not automatically provide a handset brand, exact model, carrier or location. Start by understanding the three columns before adding other tasks.
Read each RCS system field within its definition
| Field | Practical use | Do not reinterpret it as |
|---|---|---|
| Phone number | Match the result to the submitted number | Verified customer identity or number ownership |
| System | Use the system information according to the current task definition | Exact handset model, OS version, carrier or location |
| ID | Retain and review it according to the field instructions | An IMEI, identity-document number or universal cross-platform user ID |
Ask support about any unfamiliar system value or ID before relabelling it. Share the actual headings and a redacted example, and confirm the allowed values, meaning of blanks and what the ID identifies. Without that definition, describing it as a particular device identifier would be speculation.
Do you need system information or an RCS registration result?
A system task has a clear purpose when the returned system column changes how you organize an existing list. If you only need the registration result, choose RCS Validity Check instead. A registration export without a system column may be entirely correct for the task that was selected.
Review the AppShai RCS system and validity services before submitting numbers. If you need both, keep the task identities separate; a system ID is not a registration status.
Why system, carrier and iOS checking are separate questions
Carrier lookup concerns network information supplied by that service. An iOS check has its own task definition. RCS System Check supplies its specified fields. None of those labels authorizes filling in an exact model or OS version that was not returned.
If carrier information is the real requirement, use a carrier service rather than deriving it from system values. The system-versus-carrier explanation develops that distinction.
Google’s official capability documentation concerns RCS for Business[1]. It does not establish that every third-party “RCS system checker” returns the same data, or that Google’s response structure is AppShai’s Excel schema.
Start with actual returned values
Keep your source list and prepare TXT with one phone number per line. Select RCS System Check in the dashboard. When the task finishes, download Excel and review the phone number, system and ID columns against the confirmed field instructions. Keep blank and exceptional results unresolved until their meaning is clear.
A limited set of existing numbers you are entitled to process can show whether these fields are useful before you commit a larger list. The bulk RCS checking guide covers file preparation and task selection.
For programmatic access, contact official AppShai support for private API documentation. Three manual export fields are not an API parameter specification. Nor does a system result grant messaging permission; business communication remains subject to applicable policies[2].
References
- Google: Capability checks — official RCS capability context, distinct from third-party product schemas.
- Google: RCS for Business Acceptable Use Policy — permission and messaging-use requirements.
