Article summary
Run the RCS check your list actually needs. Compare the validity and system result fields, prepare a TXT phone list and understand what the Excel export can establish.
Before running a bulk RCS number check, decide what the result must tell you. Choose RCS Validity Check for the registration result; choose RCS System Check for the returned system information. The two tasks produce different Excel columns, and one cannot replace the other.
AppShai supports both tasks. The manual dashboard accepts a TXT phone list and exports Excel results. It does not send messages, and completing a check does not produce delivery, read or conversion data.
Match the question to the RCS task
| Your question | Task | Current output fields |
|---|---|---|
| What registration result does each submitted number return? | RCS Validity Check | Phone number, registered status |
| What system information is returned for these numbers? | RCS System Check | Phone number, system, ID |
If a list has never been checked and registration is the immediate missing fact, start with validity. If the next decision needs the system column, select the system task instead. There is no mandatory sequence requiring both checks for every list.
The AppShai RCS Number Checker describes the supported services. Replace a broad request such as “check the RCS list” with the specific question you need answered before submitting it.
Move from the existing list to a useful Excel result
- Prepare the numbers. Keep the source file, standardize formatting using known country information and remove blank lines and obvious duplicates. Do not guess a country from length alone.
- Create TXT. Put one phone number on each line. Keep names, order references and notes in the original business record.
- Select the task. Choose validity or system according to the missing information. Run a limited sample to confirm the accepted format and returned columns.
- Download Excel. Match results to source numbers. Investigate missing rows, exceptions or unexplained values before assigning a negative result.
You do not need a new database architecture to start. Keep a reliable source-number match, know which task ran and retain the checking date. The RCS task-choice guide provides a more detailed comparison.
A registration result is not a delivery report
Google documents RCS capability checks separately from message interaction[1]. Its documentation explains the official RCS for Business context; it does not establish AppShai’s output schema or technical implementation.
A two-column registration export cannot be expanded into four asserted categories such as business-message capable, SMS-only, disconnected and inactive. Those conclusions need their own evidence. Likewise, a system result is not automatically a carrier name, exact handset model or verified identity.
Read actual delivery and reply outcomes in the sending service and conversation records. Google’s acceptable-use policy also covers notice, consent and opt-out[2]; running a number check does not supply that permission.
Know what you will do with the result before increasing volume
If the spreadsheet will simply be filed away, pause before expanding the job. If it will fill a missing RCS status on an existing customer list, or organize records that need system information, use the sample to complete that real task first.
For recurring programmatic checking, contact AppShai support for private API documentation and confirm the task and response format. Another provider’s endpoint or parameters do not describe AppShai’s API.
References
- Google: Capability checks — official capability-check background, not AppShai field documentation.
- Google: RCS for Business Acceptable Use Policy — notice, permission and responsible messaging.
