Article summary
Clean Central African Republic +236 lists by separating legacy seven-digit records, current eight-digit structure and WhatsApp registration status before CRM use.
Central African Republic phone data carries a less obvious risk than ordinary punctuation errors. Older sources may contain numbers from the country’s seven-digit era, while newer records use eight national digits. English databases may also shorten the country name to “CAR,” a label that can collide with vehicle, region or internal customer codes. If every row is sent directly to WhatsApp registration screening, failures will mix legacy structure, truncation and genuine unregistered status.
ITU operational bulletins document the Central African Republic’s move from seven to eight digits. A sound +236 workflow therefore begins with record age, country attribution and complete length. Missing digits should never be invented merely to make a row pass validation.
Identify which numbering era produced the record
The Central African Republic used a seven-digit scheme before adopting an eight-digit national plan. A short record in an archived address book, humanitarian project or old event list may be historically complete rather than one character away from a current number. The additional digit can depend on service and migration rules, so the modern value cannot be reconstructed safely from the old string alone.
| Observed value | Likely issue | Action |
|---|---|---|
| Eight digits after +236 | Candidate current structure | Continue character and provenance checks |
| Seven digits after +236 | Legacy record or truncation | Return to the source; do not pad |
| Country stored as CAR | Ambiguous abbreviation | Confirm with country code and acquisition source |
| 236 without a plus sign | Spreadsheet formatting loss | Check that the digits were not rounded |
Keep +236 separate from the two Congos
The Central African Republic uses +236, the Republic of the Congo uses +242, and the Democratic Republic of the Congo uses +243. Country names can be abbreviated or translated inconsistently across Chinese, English and French source systems. Search-and-replace operations based on “Congo” or “Central Africa” can therefore move valid records into the wrong plan.
Where country and telephone fields are stored separately, generate a conflict list first. A row labelled Central African Republic with a +243 number requires evidence from the acquisition source. Changing the prefix to +236 would create a different number, not repair the record.
Eight digits can still conceal spreadsheet damage
A lost plus sign, retained international exit code, full-width numeral, invisible space or two numbers pasted into one cell can defeat matching even when the visible length appears plausible. Preserve the received field unchanged, then normalize a working copy. That separation makes every correction reversible.
- Convert display numerals to standard ASCII digits and remove separators.
- Change 00236 to +236 only after country attribution is confirmed.
- Require eight digits after the country code and quarantine all other lengths.
- Split multiple numbers into separate records without losing the customer relationship.
- Deduplicate the complete international values and route conflicts to manual review.
Registration screening has a deliberately narrow answer
WhatsApp’s official registration process asks the user to select a country, enter the full international number and confirm possession through a code delivered by SMS or phone call. WS registration screening checks registration status; it does not perform that ownership verification and cannot prove who controls an account. The basic export contains the phone number and whether it is registered.
Do not place malformed rows in the same bucket as unregistered rows. The first group represents unresolved input quality. The second represents a platform result for a structurally acceptable number. Separating those causes shows whether the remedy is better source data or a different operational channel.
Create a TXT input from the controlled cleaning table
After normalization in the internal system, export only the phone column as TXT with one value per line. Do not upload names, regional notes or the spreadsheet itself. Open the AppShai WhatsApp Number Checker, select WS registration screening and download the resulting Excel workbook when processing is complete.
TXT is the accepted input and Excel is the output for the selected service. Join the returned workbook to the internal table on the normalized number, while retaining the received value, cleaning disposition and source date. That structure explains both excluded rows and later status changes.
Four outcome buckets preserve more information than two
- Structurally accepted and registered: proceed to relationship and contact-basis review.
- Structurally accepted and unregistered: retain as a telephone record; do not label it a dead number.
- Format unresolved: includes seven-digit legacy values, truncation and country-code conflicts.
- Duplicate or unknown source: merge controlled profiles or pause use until provenance is known.
If recent account use later becomes relevant, activity screening can be run on the registered bucket as a new task. The original raw list does not need to be resubmitted.
Modernize archives without erasing their history
Do not overwrite an old project dataset. Store the original snapshot and generate a current working version under the eight-digit rules. Unresolved seven-digit records should remain quarantined. When a customer supplies a current number through a trustworthy channel, add it as a new linked record rather than pretending the archived string always had that value.
Every repeat screening run needs a date. Numbers may be recycled and platform registration can change, so two dated results can both be accurate for their respective moments.
Use official references for the facts they can establish
The ITU bulletin on the Central African Republic numbering transition establishes the structural history. The official WhatsApp registration instructions establish the international-format and verification boundaries. Neither source grants a business permission to contact a person.
Once format, registration status, customer identity and contact basis live in separate fields, a +236 list becomes explainable. Even records that cannot be repaired have an explicit disposition, rather than disappearing into a generic “failed” result.
