Phone lookup is not limited to 03 mobile numbers
A call from a business can display a landline, an area-qualified UAN or another supported contact format. Caller.pk’s current number system supports five classes: mobile, landline, UAN, toll-free and short code. Support for a format does not mean every number in that class has a public identity.
Keep the distinction between formatting and information. A successful format check means the input fits the supported rules; it does not prove the number is assigned, active or owned by a particular business. Public context comes from the available identity and report records.
For landlines, keep the area code
Use the complete number shown in the call log or published by the business. A local subscriber number without its area code can refer to different places, so do not add a city code based only on where you think the caller lives.
For a supported national landline format, Caller.pk normalises the leading trunk prefix into the international Pakistan format. For example, the structural pattern 021 + subscriber digits becomes +92 21 + subscriber digits. This is a formatting illustration, not a real number to dial or an instruction to invent missing digits.
If a copied number fails, compare it with the source for dropped digits or a missing area code. Removing spaces is different from changing the number itself. Repeatedly trying guessed variations risks finding an unrelated profile.
Why a bare UAN may not produce a reliable match
Business contact pages sometimes present a UAN without enough context to identify the complete supported number. Caller.pk requires an area-qualified form where its UAN rules require one; it does not guess the missing area.
A shared company number can serve multiple branches. Finding a matching UAN should not lead you to assume that every branch address belongs to the incoming caller. When a unique public identity cannot be selected safely, limited information is preferable to an incorrect branch label.
For an urgent business enquiry, use the organisation’s own published contact instructions. Caller.pk’s lookup is for context, not a replacement for the business’s routing or customer-support arrangements.
Toll-free numbers and short codes need their own handling
Do not convert every short number into a mobile number by adding 03 or +92. Toll-free and short-code formats are separate classes in Caller.pk’s normaliser. Paste the original number and let the supported rules determine whether it can be searched.
Some internal canonical keys may differ from how a number is displayed to a person. You should not have to construct those keys yourself: use the normal search field. If the service rejects an input, do not assume that the number is fraudulent; it may be incomplete or outside the supported formats.
Read the profile with the same care as a mobile lookup
A landline or UAN is not automatically trustworthy because it looks like an office number. Check the available identity, its verification status and any approved reports independently. A directory listing may provide a business address or website while remaining unverified.
You can report an experience involving a supported non-mobile number through Caller.pk’s reporting flow. Confirm the normalised display before submitting, describe what happened and leave out private documents or unrelated personal information.
If a public business listing has the wrong contact number, request a correction instead of posting a fraud allegation merely to get it changed. Accuracy matters as much for a shared switchboard as for an individual mobile number.