Link Leads Blog · October 28, 2026
"Wrong number" isn't on the CTIA's opt-out keyword list, so the platform that auto-suppresses a STOP usually does nothing with it. That gap is where agents keep texting or calling a number after being told, in plain English, that it isn't the person on the record. Why the reply needs its own handling, and the three-step fix.
This is a practical workflow guide, not legal advice. Confirm your own obligations with counsel familiar with telemarketing law before building a texting or calling program around this post.
The CTIA's short code and 10DLC keyword set — STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT — is what most 10DLC-registered texting platforms scan for and act on automatically at the carrier level. See SMS opt-out compliance for the full keyword list and how that carrier-level block works. A reply that says "wrong number," "you have the wrong person," or "who is this, I don't know you" contains none of those words. It isn't a complete message matching a keyword, so most platforms don't flag it, don't suppress the number, and don't stop the next scheduled touch in your cadence from going out to the same record two days later.
That's the specific gap this post is about. A wrong-number reply gets read by a human and then, because it didn't trip an automated rule, often gets no action at all beyond that one glance — the record just sits in the list, waiting for the next send.
A record that just doesn't answer carries some uncertainty — maybe the number's fine and the person is busy. A "wrong number" reply removes the uncertainty: someone who isn't your lead confirmed, in writing, that the number reaches them instead. Continuing to contact that number after that reply isn't a wasted dial anymore — it's contact with a person who told you directly they're not who you're trying to reach. On an aged list specifically, this reply is also one of the clearest signals you'll get that the number has been reassigned since the record was captured, which is exactly the exposure the reassigned numbers database check is designed to catch before the fact. A wrong-number reply is the same finding arriving after the fact, from the person who'd know best.
A clean reassigned-numbers-database query run inside the required window gives you a safe harbor if a number turns out to have been reassigned — but that protection is built around good-faith reliance on a "no" or "no data" result at the time you checked. A wrong-number reply is new information that arrives after that query, and it's hard to argue good-faith reliance on a database result once a human being has told you directly that the number isn't theirs. Whatever the database said going in, the reply is the more current and more specific fact. Treat it that way operationally: it overrides the database result for that one number, immediately, no re-query needed.
None of this needs new software. It needs a rule that gets followed every time a reply comes in that isn't a scripted yes/no.
1. Build a keyword catch wider than the CTIA list. Most texting platforms let you define custom auto-tags on top of the required STOP handling. Add a second rule that flags any inbound reply containing "wrong number," "wrong person," "don't know you," "who is this," or similar — not to auto-reply, just to route the message into a manual review queue the same day it lands. A simple keyword-contains rule catches the great majority of real wrong-number replies without needing anything more sophisticated.
2. Suppress the number the same way a STOP gets suppressed. Once a human confirms it, write the number to the same standing "do not contact" table your STOP replies go into — phone number, the date, and the reason, logged as its own category so you can tell a wrong-number suppression apart from an opt-out if the two ever need to be reported separately. Suppress across every channel, not just the one the reply came in on: a number that texted back "wrong number" and then gets a cold call from the same campaign a week later is the same mistake as ignoring a STOP on one channel while still calling on another.
3. Pull it before the next list touches a dialer or SMS platform, not after. The suppression table only does its job if every new batch — including a fresh purchase — gets checked against it before the first send, the same discipline covered in SMS opt-out compliance for STOP replies. An aged list is sold non-exclusively, so the same phone number can resurface in a later batch pulled from the same or a different source; the suppression check is what keeps a number you already got burned on from coming back around.
If you're logging outcomes with a code set like the one in call disposition codes for aged insurance leads, don't fold a wrong-number reply into "no answer" or a generic "bad data" bucket. Give it the same WN treatment that post describes for a live call — permanent removal from the calling and texting pool, not a recycle — and keep the raw reply text alongside the timestamp. If a question ever comes up about why a number stopped getting contacted, the actual words someone sent back are a better record than a code alone.
On any list captured 30 to 90 days before you work it, some share of numbers will have changed hands in that window — the same churn that makes a reassigned-numbers-database check worth running at all. A wrong-number reply is that churn surfacing on its own, after the fact. Running both the database check before the first send and a live catch rule for replies afterward covers more of it than either alone, since a number can slip past a "no data" result and still get caught the moment its new owner replies.
None of the above helps with a number that was never going to deliver a text in the first place. A landline picked up as a text-only record won't generate a "wrong number" reply — it just won't receive the message, which is a different failure with a different fix. Run a wireless/landline check and a DNC scrub before the first send, as covered in how to DNC scrub an aged lead list. We point our own buyers at Landline Remover (disclosure: that's an affiliate link and we may earn a commission) for that pass — upload the CSV and it strips landlines and DNC-listed numbers before anything loads into a dialer or SMS platform. That step and the wrong-number catch rule solve different problems: one keeps bad numbers out before you send, the other catches the ones that only reveal themselves after a person replies.
This is a practical workflow guide, not a compliance opinion. TCPA exposure, reassigned-numbers safe-harbor rules, and carrier keyword requirements change and carry real penalties — confirm your platform's handling and your own suppression process with counsel before scaling a texting or calling program. Link Leads sells aged data leads — not consented insurance-form leads — and is not DNC-scrubbed; the buyer is responsible for all dialing and texting compliance.
Build a state-and-age filtered order in the order builder, or pull the free 100-row sample first to see the column layout before you buy.