Article summary
Prepare +239 phone lists from São Tomé and Príncipe, preserve island-level source data, and interpret WhatsApp registration results without confusing them with identity or activity.
São Tomé and Príncipe is a small market, but a +239 list is not automatically simple. Customers, shops or projects may need to be reported separately for São Tomé island and the Autonomous Region of Príncipe, while their telephone numbers still belong to one national numbering plan. Adding an island label to the number, treating every telephone line as mobile, or inferring WhatsApp status from a district field will damage the dataset.
The numbering material published by the ITU assigns country code +239 and generally uses seven-digit national numbers. Number normalization answers whether a record has a plausible +239 structure. WS registration screening answers whether that record returns a WhatsApp registration status. Those two steps should remain visible and separate.
One country code, separate island provenance
Records from either main island use +239. Island, district, branch and acquisition campaign belong in their own fields rather than inside the telephone string. This makes geographic reporting possible without inventing a regional telephone format.
| Field | Controlled content | Keep out |
|---|---|---|
| Normalized phone | +239 plus seven national digits | Island name, free-text notes or customer name |
| Source location | São Tomé, Príncipe or another evidenced value | A location guessed from the number |
| Screening status | Task date and registration result | Unsupported activity or permission claims |
Apply the seven-digit check carefully
A normalized candidate has +239 followed by seven national digits. A value starting with 00239 uses an international dialling prefix; for storage, convert it to +239 and then validate the remaining length. Example digits should only illustrate the shape and must not be presented as live subscriber numbers.
A bare seven-digit value still needs country evidence. Country selection, form locale or a trusted acquisition source should establish that it belongs to São Tomé and Príncipe. Short codes, service numbers, fixed lines and mobile ranges can have different purposes, so length alone does not prove suitability for a mobile WhatsApp workflow.
Resolve Portuguese form fields before merging the CRM
A Portuguese-language form may distinguish telemóvel, telefone and WhatsApp, while an international CRM imports all three into a generic Phone column. Map the fields before merging. When a customer supplies a mobile and an alternate number, create linked phone records instead of concatenating both values in one cell.
Accents and local spelling do not change the telephone number, but they can split country or district reporting. Normalize the reporting value while retaining the original language label for provenance. That gives analysts a consistent grouping without erasing what the customer entered.
Registration status is not identity verification
WhatsApp’s official registration flow confirms control of a number through a code delivered by SMS or phone call. WS registration screening returns a registration status; it does not receive that code and does not authenticate the name in a customer database. A registered result must still be connected to identity, relationship and purpose through the organization’s own records.
An unregistered result is not evidence that the telephone line is dead. It may be a working telephone, a fixed line, an unregistered mobile subscription or simply have no corresponding account at the task date. Telephone validity and WhatsApp registration need separate fields.
Produce a minimal +239 TXT upload
- Copy the received telephone column and leave the original unchanged.
- Remove spaces, parentheses and hyphens from the working value.
- Convert an established 00239 prefix to +239.
- Require seven digits after the country code and quarantine exceptions.
- Split cells containing several numbers and deduplicate the complete international values.
- Export only the final phone column as UTF-8 TXT, one number per line.
AppShai does not accept Excel or CSV as the task upload. The internal workbook remains the place for customer, island source and contact-basis fields; the TXT contains only what is needed for number screening.
Select the WS task that matches the actual question
Open the AppShai WhatsApp Number Checker, upload the TXT file and select WS registration screening. The resulting Excel workbook contains the submitted phone number and whether it is registered. If recent use matters to a justified workflow, WS activity screening is a separate task; do not infer activity from registration.
Compare input and output row counts, isolate exceptions, and join results back on the normalized number. Where several customer records legitimately share a business line, retain the many-to-one relationship rather than deleting customer history in the name of phone deduplication.
Read island-level summaries without overstating a small sample
Before comparing registration rates between São Tomé and Príncipe, confirm that the source samples, collection periods and customer types are comparable. A handful of numbers can shift a percentage sharply in a small dataset, so show the underlying counts beside every rate. The location comes from the customer or project record, never from +239 alone.
If one source group produces many unregistered results, inspect fixed-line contamination, list age and formatting errors before attributing the difference to local WhatsApp adoption. A technical outcome is not automatically a market behaviour finding.
Let official plans govern format and business records govern use
The ITU resource for the São Tomé and Príncipe numbering plan provides the country-code and numbering context. The official WhatsApp registration instructions describe full international format and code verification. Check for numbering updates before a fresh acquisition or major screening run.
Retain the source snapshot, normalization rules, task date and untouched export. A +239 record can then show where it came from, how it was prepared and what the task returned, without turning a registration signal into an unsupported claim about location, identity or permission.
