Article summary
Convert Moroccan 06 and 07 mobiles to +212 without the domestic zero, then keep numbering, current-carrier evidence and WS Activity observations separate in a portable-number environment.
Moroccan mobiles are commonly written with a domestic 06 or 07 prefix. International representation removes the zero and uses +212 6 or +212 7. Contact databases often go further and assign a carrier from that prefix, even though number portability allows the network to change. A Morocco WhatsApp activity workflow should keep format, carrier and recency as three independent observations.
Quick verdict: 06 and 07 help identify a mobile-shaped domestic number; removing zero and adding +212 creates the international form; a dated carrier source—not the prefix alone—is required for the current provider.
Compare the domestic and international forms
Morocco’s National Telecommunications Regulatory Agency describes a closed ten-digit domestic plan. Country code 212 precedes a nine-digit national significant number in international form, while zero is the national prefix for domestic calls. The ANRT numbering resource publishes the framework and allocated ranges.
| Service shape | Domestic display | International storage |
|---|---|---|
| 06 mobile | 06 XX XX XX XX | +212 6 XX XX XX XX |
| 07 mobile | 07 XX XX XX XX | +212 7 XX XX XX XX |
| Fixed telephone | 05 XX XX XX XX | +212 5 XX XX XX XX |
| Incorrect international form | — | +212 06/07… retains a zero that should be removed |
Why 07 belongs in a modern mobile rule
ANRT notified the International Telecommunication Union in 2016 that +212 07 would open for mobile networks because of demand for additional resources. More recent ITU operational bulletins continue to introduce new mobile ranges beginning with 7. A legacy validator that accepts only 06 will discard genuine mobile records before screening begins.
Number-range validation must therefore use a maintained source. “It was not in our old prefix table” is not sufficient evidence that a current number is invalid.
Portability makes allocation tables historical
ANRT communications describe measures designed to make fixed and mobile number portability easier. Portability lets a subscriber retain a number while changing operators. An allocation table still explains original assignment and service category, but it cannot be treated as a live carrier database.
| Field | Source | Time boundary |
|---|---|---|
| Number format | ANRT/ITU numbering plan | Changes when the plan is updated |
| Original range assignee | Allocation table | Does not rule out a later port |
| Current carrier | Dedicated carrier lookup | Must include lookup date |
| WhatsApp activity | WS Activity job | Belongs to its execution date |
Normalize 06/07 without enriching the carrier
Phone cleaning should perform only deterministic changes: remove display separators, recognize a ten-digit domestic value, remove the first zero, add +212, validate the nine digits that follow and deduplicate on the result. Carrier enrichment is a separate process with its own source and date.
This separation matters later. A port changes the carrier observation without changing the normalized telephone or erasing historical activity tasks.
Submit WS Activity and preserve its four fields
Open the AppShai WhatsApp Number Checker, select WS Activity and upload a TXT file with one +212 number per line. The Excel output contains phone number, activity time, activity days and WhatsApp mapped phone number. Keep guessed carrier text out of the phone field and never overwrite the source phone automatically with a mapped value.
- Retain the original domestic 06/07 value.
- Create the normalized +212 number and conversion status.
- Deduplicate after normalization and export TXT.
- Execute the job and record its date.
- Append all four fields to task history.
- Send differing mappings and unavailable states to review.
Define activity through the relationship, not the carrier
Order updates, support cases and long-term accounts operate on different time cycles. Declare the recency threshold before opening the Excel distribution. Do not compare average activity by a presumed carrier prefix: numbers may have ported and the customer mix may differ.
| Relationship | Basis for recency | Companion evidence |
|---|---|---|
| Order in transit | Dispatch and expected arrival | Order state and selected channel |
| Open support case | Case SLA and last reply | Priority and contact authority |
| B2B account | Contract and repurchase cycle | Account-owner notes |
| Unknown source | No defensible window | Stop contact and restore provenance |
Unavailable, online and read are different conditions
WhatsApp’s official guidance says that online means the app is open and connected to the internet; it does not mean a message was read. Last-seen visibility can also be affected by privacy settings, contact relationships, blocking and connectivity.
Retain missing visibility as unknown, and do not translate online into buying intent. Genuine engagement belongs in company-controlled reply, case and order records.
Assign each Moroccan field one job
| Field family | Retained evidence | Prohibited shortcut |
|---|---|---|
| Telephone | Raw domestic value and normalized +212 value | Keep the domestic zero after +212 |
| Carrier | Lookup value, source and date | Hard-code it from 06/07 alone |
| Activity | Time, days, mapped number and job date | Fill blanks with zero or overwrite history |
| Authority | Order, case, consent and opt-out events | Use activity as contact permission |
Release review
- Convert domestic 06/07 to +212 6/7 and remove the trunk zero.
- Allow current 07 mobile ranges instead of relying on an old validator.
- Separate the normalized phone from a dated current-carrier field.
- Upload TXT and retain every WS Activity Excel field.
- Define the recency window before inspecting results.
- Keep unavailable observations unknown and mapped phones under review.
- Require a documented customer relationship for any follow-up.
Moroccan contact governance works when three facts are allowed to change on their own timelines: format follows the numbering plan, carrier may change through portability, and activity belongs to a particular screening date.
