How to Identify Landline vs. Mobile Numbers in Customer Data

The short answer: route on current line type, then apply consent rules

To identify landline vs mobile number records in a US customer database, use a current phone line-type lookup after you normalize the number. Treat a result of mobile or wireless as an SMS candidate, a landline as a non-SMS route, and VoIP as a category that needs a deliberate policy rather than a guess. A lookup is useful operational data, but it does not establish who owns the number, whether the person opted in, or whether a message will be delivered.

The practical sequence is simple: validate the number format, enrich it with current line-type data, preserve the result and its timestamp, then combine that signal with consent, opt-out, reassignment, and platform controls. This prevents wasted sends to obvious landlines without turning a data field into a compliance claim. For a broader intake framework, see HVSMS’s guide to validating mobile numbers before texting.

What a phone line-type lookup can tell you

A phone line-type lookup queries a data source for the present classification of a telephone number. Major lookup providers commonly return a type, carrier information where available, and an error or unknown state. Twilio’s current Line Type Intelligence documentation lists landline, mobile, fixed VoIP, non-fixed VoIP, toll-free, personal, and unknown among its classifications. It says landlines generally cannot receive SMS and mobile numbers generally can. [1]

The labels are classification data, not a universal guarantee of message capability. They can vary by provider and can change when service changes. In particular, distinguish a lookup provider’s category from your messaging platform’s support matrix and its risk controls. The first identifies a line type; the latter determines whether and how your specific sender may attempt a message.

How to identify landline vs mobile number records reliably

Do not classify US phone records from an area code, exchange, or a customer’s form label. Local number portability lets a customer keep the same telephone number when changing among wireline, IP, and wireless providers. [2] The number’s digits therefore describe numbering geography, not a permanent service type. Interconnected VoIP providers are also subject to Local Number Portability rules. [3]

1. Store the raw entry, then normalize the number into E.164 format, such as +14155550123. Keep parsing failures separate from a valid number with an unknown line type.
2. Run basic mobile number validation first. Syntax validation tells you whether a number is structurally plausible; it is not a line-type result. HVSMS explains the distinction in mobile-number validation versus verification.
3. Request a line-type lookup from a reputable provider. Save the returned type, provider, lookup timestamp, and any error code rather than overwriting your original customer record.
4. Apply a routing rule that requires more than line type: active permission for the message, no opt-out, no internal suppression, a permitted sender, and a usable route.
5. Refresh data when it matters: at new capture, before a high-value automated flow, after a hard delivery failure, and on a defined recurring hygiene cycle.

For batch cleanup, make enrichment idempotent: the same input and date should create an auditable update rather than a new duplicate contact. For live checkout or support flows, use a timeout and a conservative fallback. A temporary lookup failure should not be interpreted as permission to send.

Fixed VoIP vs. non-fixed VoIP: use category, not stereotypes

VoIP means voice over Internet Protocol: voice communications carried using Internet protocol rather than traditional analog systems. Depending on the service, calls may be made from a computer, a special VoIP phone, an adapted traditional phone, or a wireless phone. [3] That technical range is why “VoIP” is too broad to be a single CRM decision.

A fixed VoIP classification generally means the virtual number is associated with a physical device. Non-fixed VoIP generally means the virtual number was obtained online without a physical device. [1] Neither label proves that the listed customer is the present user, that the number belongs to a consumer rather than a business, or that it can receive your intended SMS program. It also should never substitute for consent evidence.

• For transactional programs, define the acceptable use case and confirm the platform’s current support for the destination and sender type before enabling any VoIP route.
• For promotional programs, keep fixed and non-fixed VoIP in separate reporting segments until you have enough compliant, program-specific performance evidence to set a defensible policy.
• For fraud-sensitive flows, do not reject a customer based only on VoIP. Use risk signals appropriate to the transaction and give legitimate customers a reasonable alternate path.
• For every VoIP decision, retain consent, opt-out, source, and lookup-time fields. The category is a routing attribute, not a customer-quality score.

This approach is more durable than a blanket “block all VoIP” rule. It reduces uncertainty without discarding a valid contact method or making a claim the data cannot support. See our primer on phone line type intelligence for the fields worth preserving across systems.

Porting and reassignment are the limits every routing rule must respect

Porting changes the service behind a familiar number. The FCC states that a number can move between wireline, IP, and wireless providers, and that a simple port is generally processed in one business day. [2] A record classified as landline last quarter may now be wireless; a former mobile record may have moved in the other direction. Refresh cadence matters because line type is time-sensitive operational data.

Reassignment is a different risk. A permanently disconnected number may later be assigned to a different person. The FCC-created Reassigned Numbers Database (RND) contains permanently disconnected US geographic and toll-free numbers and the latest permanent-disconnection date. It is intended to help callers determine whether a number was disconnected from the consumer they intend to reach. [5] It is not a substitute for line-type intelligence, and a line-type lookup is not a substitute for reassignment screening.

Build a “last checked” policy into lifecycle automation. For example, re-enrich before reactivating a dormant SMS profile, after a carrier or platform failure, and before a large campaign sent from legacy CRM data. Pair that discipline with recycled-phone-number SMS compliance controls rather than relying on an old mobile flag.

Make routing decisions without confusing data quality and compliance

There are three distinct layers. Legal requirements govern the circumstances in which a text may be sent. The FCC has codified that National Do Not Call Registry protections extend to text messages and states that texters need prior express invitation or permission before sending a marketing text to a wireless number on the Registry. [4] Where prior express written consent is required under the TCPA, the FCC’s rule specifies a written agreement with clear and conspicuous disclosures, an identified seller, and a number authorized for the messages. [4] Applicable facts, technology, message type, and state law can affect the analysis; HVSMS provides strategy and implementation, not legal advice.

Carrier and platform policy is a separate operational layer. Your messaging provider, downstream carriers, and sender program may impose registration, content, throughput, destination, or opt-out requirements that are stricter or differently scoped than a line-type lookup. Confirm current requirements in your platform documentation and configure the sender accordingly. A mobile result is not a pass through that layer.

Conservative best practice is to hold a number out of promotional automation unless the record has a defensible consent state, a usable current line type, an active delivery route, and no suppression. Preserve the evidence needed to explain the decision later. Our SMS opt-in requirements guide and consent-record audit trail framework cover the data that should sit alongside the line-type field.

A CRM data model that supports clean SMS routing

Do not collapse lookup output into one Yes/No “textable” checkbox. A durable schema separates the raw phone record, normalized number, validation result, line-type result, lookup source and timestamp, consent scope and source, opt-out status, last delivery outcome, reassignment-screening status where used, and final routing state. The final state should be derived from those inputs so it can be recalculated when any one changes.

Run a small controlled pilot before changing a mature automation. Compare routing-state counts, lookup errors, stale records, delivery outcomes, opt-outs, and support contacts by line type. Use the findings to improve your SMS list hygiene process, not to lower consent standards in pursuit of a larger reachable audience.

Three practical examples

Example 1: ecommerce welcome flow. A new subscriber enters a number at checkout. The CRM normalizes it and confirms the form’s consent capture is complete. A live lookup returns landline. The automation does not send the welcome text; it retains the consent event but marks the SMS route as unavailable and offers email if the customer has chosen it. The team does not reinterpret the stored consent as permission to call.

Example 2: older loyalty list. A retailer’s list shows “mobile” from two years ago. Before a promotion, the business refreshes the line-type field and finds a mixture of landline, mobile, and unknown results. It suppresses landlines, holds unknowns, and separately evaluates whether each mobile record still has applicable consent and no opt-out. The refresh improves routing, but it does not repair missing consent evidence.

Example 3: non-fixed VoIP support number. A customer provides a non-fixed VoIP number for order updates. The team confirms that the intended sender and destination are supported by its current platform policy, then applies the same consent and opt-out controls used for other numbers. It reports the segment separately so a later deliverability issue is visible instead of being buried in aggregate results.