Practical GuideNovember 17, 2026 · 12 min read

Call Suppression with Extended Carrier Context: A Practical Guide

Every dialer and SMS gateway needs the same three answers before it spends money: is this number reachable, what kind of line is it, and who is behind it. The standard lookup answers the first two. The extended lookup adds the third — and that is where suppression decisions get smart. This guide shows how to build a real-time routing layer with working code you can drop into production.

What the extended lookup returns

One GET request to /v1-get-phone-extra-details returns the full carrier identity of the number's block:

curl "https://api.phone-check.app/v1-get-phone-extra-details?phone=%2B12122031567" \
  -H "accept: application/json" \
  -H "x-api-key: YOUR_API_KEY"

// Response (abridged)
{
  "type": "MOBILE",
  "carrier": "AT&T",
  "ocn": "4036",
  "ocnType": "WIRELESS",
  "ocnHolding": "AT&T Inc",
  "isWholesaleHosted": false,
  "portable": "Y",
  "olsonTz": "America/New_York"
}

The routing decision layer

Here is a complete suppression and routing function. It answers should we call this number, and if so, how? using only fields from the extended lookup:

// suppression-router.ts — drop into your dialer or CRM pipeline
import { getPhoneExtraDetails } from './phone-api';

interface RoutingDecision {
  action: 'BLOCK' | 'VOICE_QUEUE' | 'REVIEW' | 'ALLOW';
  reason: string;
  sendWindow?: string;
  corporateFamily?: string;
}

async function routeNumber(phone: string): Promise<RoutingDecision> {
  const r = await getPhoneExtraDetails(phone);

  // 1. Compliance gate — block what TCPA prohibits
  if (r.type === 'VOIP') {
    return { action: 'BLOCK', reason: 'VoIP number — TCPA high-risk for cold calls' };
  }
  if (r.type === 'PAGER') {
    return { action: 'BLOCK', reason: 'Pager — not a voice or SMS destination' };
  }
  if (r.type === 'FIXED_LINE') {
    return { action: 'VOICE_QUEUE', reason: 'Landline — voice only, no SMS' };
  }

  // 2. Wholesale-hosted mobile → reseller infrastructure
  if (r.isWholesaleHosted) {
    return {
      action: 'REVIEW',
      reason: 'Reseller-hosted block — elevated churn and prepaid concentration',
    };
  }

  // 3. Corporate family grouping
  const family = r.ocnHolding || r.ocnCommonName;

  return {
    action: 'ALLOW',
    reason: 'Host-MNO mobile — clean wireless block',
    sendWindow: r.olsonTz,
    corporateFamily: family,
  };
}

Form and signup screening

The same endpoint works at the door. Before a number enters your CRM, check validity, disposable status, and line type in one call:

// signup-screen.ts — block bad numbers at the door
async function validateSignup(phone: string) {
  const r = await getPhoneExtraDetails(phone);

  if (!r.valid) return { reject: true, reason: 'Invalid number' };
  if (r.isDisposable) return { reject: true, reason: 'Disposable/burner number' };
  if (r.type === 'VOIP') return { reject: true, reason: 'VoIP — not accepted for SMS verification' };

  return { reject: false, type: r.type, carrier: r.carrier };
}

The wholesale-hosted flag explained

isWholesaleHosted is true when the number's block is operated by a wholesale or enabling carrier — Onvoy, Bandwidth.com, Neutral Tandem, Peerless, Inteliquent, iBasis, Voxbeam — or by a wireless reseller (OCN class WRSL). These are the blocks where MVNO SIMs, VoIP apps, and second-number services concentrate. The flag marks the infrastructure segment where that traffic runs — a block-level signal, not a per-number MVNO lookup. Use it to route to review, not to auto-reject.

When to step up to Full Data

Extended answers what is this number? When the question becomes what kind of exchange is this number in? — how reseller-heavy is the surrounding thousand-number segment — the full-details lookup adds nxxCarrierMix and nxxSummary at 6 credits per number. For per-number suppression and routing, extended at 3 credits is the right tier.

Related articles