Can You Run an RCS System Check with Only Phone Numbers?

Can you submit an RCS system check with only phone numbers, without knowing customers’ handset brands, models or operating systems? Under AppShai’s current manual workflow, a phone-number list is the input. You do not need to supply the unknown system information first. System and ID are returned fields, not extra columns you must fill before uploading.

Confirm the task on the RCS system-check service page before using the dashboard. If not knowing each customer’s handset has prevented you from starting, separate two questions: whether you have complete numbers you are entitled to process, and what this particular task can return.

Reduce the submission to the phone-number column

Your original sheet may contain names, customer IDs, companies, countries and sales notes. You do not need to combine those details into the TXT input or ask every customer to provide a handset model. Put one complete number on each line and keep customer information in your original sheet.

First line: one complete phone number
Second line: another complete phone number
Numbers only, without name, model or system columns

This is a description of the file layout, not a ready-to-submit number sample. Check international calling codes and original digits, retaining the source file. Confirm records with unknown origins or missing country information instead of inferring a number’s country from a name, language or company address. Renaming an Excel file with a .txt extension is not a format conversion.

If you already have device information, keep it in your own sheet for a later comparison. It is not an additional requirement for a number line in this task.

Select system checking rather than automatically choosing validation

Both tasks begin with phone numbers, but they answer different questions. Choose an RCS system check when you need its system results, or a validity check when you need registration status. The shared input does not make their outputs interchangeable.

Confirm the task name before submitting. If the downloaded file contains registration results only, first check whether a validity task was selected. Adding guessed system values to the TXT file is not the fix. The existing phone number, system and ID explanation covers the returned fields.

A simple input does not guarantee a definite answer for every number

Submission requirements and result completeness are separate matters. Acceptance of a file does not promise a usable system value for every row. System checking is not a local calculation of handset model from a phone prefix. Ask for the task’s interpretation of unfamiliar values rather than filling in a system yourself.

If you need an exact handset model, operating-system version or IMEI, explain that requirement to support before ordering. The current phone number, system and ID fields cannot be expanded into arbitrary device information. In particular, a column named ID must not automatically be treated as an IMEI.

For missing columns, missing rows or blanks in a completed result, follow the RCS result troubleshooting guide. Resubmitting more personal details about the customer will not necessarily resolve a task-result problem.

Confirm two things before the first submission

1. Can you match the result to your original list? Extract the numbers to be checked, retain the source sheet and match the returned Excel by complete number rather than assuming row order never changes.
2. Which result will you use? Confirm a system task and clarify the system values relevant to your purpose. Do not promise colleagues device details that have not been confirmed.

To see the actual output format, use the RCS service page’s registration and trial options and submit a permitted subset of your existing numbers as a separate task. The manual workflow uses TXT uploads and Excel downloads. For programmatic access, contact support for API documentation; the manual file format is not an API parameter specification.