“Qualified SSDI call” is one of the most overloaded phrases in disability-marketing conversations.

A source may use it to mean that a caller completed a short screen. A law firm may use it to mean that intake wants a follow-up. A call buyer may use it to mean that the call met a commercial rule. An attorney may use it informally to describe a matter worth reviewing. A vendor may use it to imply that a claimant will retain the firm or prevail in a case.

Those are not the same thing.

For a disability practice, the useful question is not, “Was this call qualified?” It is, “Qualified for which decision, under whose definition, using which evidence, and what happens next?”

A serious buyer should define the answer before calls arrive. The definition should be narrow enough for a source, exchange, and intake team to apply consistently; humane enough that callers are not treated as bad traffic merely because they need a different path; and cautious enough that no one mistakes a marketing or intake screen for an SSA decision.

This article is for disability law-firm owners, managing attorneys, practice leaders, intake directors, legal call-center leaders, established non-attorney representatives, and advocacy organizations that can operate a real buyer campaign. It is operational education, not legal advice or an SSDI eligibility tool. The Social Security Administration, not a call source, exchange, or intake script, determines program eligibility. Counsel should review an organization’s actual intake, advertising, privacy, recording, representation, and follow-up practices.

For the broader buying process—capacity, service area, test volume, source review, and reporting—read How to Buy SSDI Calls. For the dual-audience vertical foundation, see SSDI / Disability Calls: What Buyers and Publishers Should Know. This guide focuses on the definition that makes that process workable.

Start by separating six different outcomes

A single “qualified” status hides too much. Before a buyer accepts any SSDI traffic, its operating documents should separate at least these events.

Event	Buyer-side meaning	What it does not establish
Relevant inquiry	The caller appears to be asking about a disability or Social Security matter the organization may review.	SSA eligibility, a viable case, a commercial charge, or representation.
Routeable inquiry	The call fits an active target’s stated service area, hours, call type, language path, and capacity rules.	That the organization will accept the matter after intake.
Buyer-defined qualified intake opportunity	The call meets the buyer’s documented intake-policy criteria or belongs on a specified review path.	That SSA will approve benefits or that the caller must become a client.
Commercially qualified or billable event	The call meets the event defined in the commercial agreement for the buyer price.	A representation agreement, an earned publisher payout, or a successful claim.
Retained or represented matter	The organization has completed its own approved representation or engagement process.	A favorable SSA determination or case outcome.
Successful case outcome	The result defined by the practice or claimant’s matter, often decided much later.	Whether the original call should have been accepted, qualified, billed, or paid.

The words matter because they assign responsibility.

A source can be responsible for accurately describing the consumer journey and passing agreed, non-sensitive screening information. The buyer owns its acceptance policy and its intake handling. The commercial agreement owns the billable-event definition. The organization’s representation process owns the decision to accept a matter. SSA owns the benefits determination.

The general operating distinction between routed, qualified, and billable calls is explained in The Difference Between a Routed Call, a Qualified Call, and a Billable Call. SSDI campaigns need the same discipline, with an additional boundary: a buyer’s intake definition must never be presented as a government eligibility result.

The broader buyer framework in The Buyer’s Guide to Qualified Inbound Calls is useful here, but an SSDI buyer needs to name the additional separation between intake policy and SSA determination.

“Qualified for SSDI” is not a valid intake conclusion

SSDI is a federal program with its own legal and administrative requirements. SSA states that SSDI eligibility involves covered work and a medical condition meeting the agency’s definition of disability; it applies its own process to make that determination. SSA’s current eligibility guidance explains the program criteria and decision process.

That is why a source should not tell a caller, “You qualify for SSDI,” merely because the caller answered a handful of questions about work, treatment, or claim stage.

A law firm or representative organization may reasonably decide that it wants to speak with a person who reports certain facts. It may decide that another person should be routed to a different intake team, given an appropriate explanation, or not placed into the buyer’s current campaign. Those are buyer-owned operational decisions.

They are not the same as any of the following:

A finding that the caller has enough work credits.
A finding that the caller’s work activity meets SSA rules.
A medical conclusion.
A prediction about a claim or appeal.
A promise that the buyer will represent the caller.
A statement that the caller will receive benefits.

A practical way to keep the boundary clear is to use intake language that describes the next step, not the outcome:

“The caller is seeking help with a Social Security disability matter.”
“The caller reported information that meets this buyer’s initial review policy.”
“The caller should be evaluated by the buyer’s trained intake team.”
“The caller falls outside the buyer’s current service or campaign policy.”
“More information is needed before an intake disposition can be made.”

Avoid source labels such as “SSDI-approved,” “guaranteed case,” “eligible claimant,” or “qualified for benefits.” They overstate what a short screen can know and can confuse the caller about the role of a private law firm, representative, or marketing source.

Define relevance before defining qualification

A buyer should first decide what it means by a relevant inquiry.

That definition answers one modest question: is the caller asking about a kind of matter this organization may handle?

For example, a buyer may distinguish among:

Help with a potential SSDI application.
A pending SSDI claim.
A denial, reconsideration, hearing, or appeal-related inquiry.
An SSI inquiry.
A retirement inquiry.
A private long-term-disability policy.
Veterans-disability, workers’ compensation, or another benefit question.
A general SSA-status or administrative question.
An existing-client request.

The goal is not to interrogate the caller on the transfer or to settle a legal question before the buyer answers. The goal is to avoid forcing materially different inquiries through the same call path.

SSDI, SSI, and retirement should be named separately when the buyer’s service design treats them differently. SSA describes SSI as a separate program for people with limited income and resources who are disabled, blind, or age 65 or older. SSA’s SSI overview is a useful orientation resource for intake teams. A caller may use “disability,” “Social Security,” and “benefits” interchangeably; a buyer should not assume that the program, intake route, or representation path is interchangeable too.

A relevant inquiry is therefore an opening classification, not a promise. It tells the routing system and intake team which conversation may be appropriate next.

Buyer-defined qualification should be a documented intake policy

After relevance comes the buyer’s own qualification policy.

A buyer-defined policy is not a universal SSDI screen. It is a written statement of what that specific organization can currently receive, review, and route. It should reflect the organization’s actual practice, coverage, staffing, ethics rules, and intake workflow—not a vendor’s generic template.

The policy should name four categories for every material signal:

What the caller or source may state.
What the signal means operationally.
Who decides the next step.
What disposition is recorded.

Here is a buyer-side example. It is hypothetical and intentionally does not establish eligibility.

Intake signal	Operational use	Appropriate disposition examples	Not a conclusion about
Requested help	Distinguish a disability inquiry from an unrelated benefit or insurance question.	Continue, re-route, or explain that the current campaign does not cover the topic.	Whether the caller has an SSDI claim.
Service area	Confirm whether the organization can serve the caller under its current operating policy.	Route to an active team, create an approved callback, or do not accept through this target.	The claimant’s right to seek representation.
Claim stage	Send initial, pending, denied, or appeal-related inquiries to the team that handles them.	Initial-intake route, appeals route, information-only path, or further review.	The merits of the claim or appeal.
Existing representation	Apply the organization’s counsel-approved policy for callers who say they have a representative.	Specialized routing, respectful close, or a documented review path.	Whether the caller can change representatives or whether a representation is valid.
Work history or recent work	Identify whether trained intake should explore the topic further or whether a specialized path is needed.	Continue intake, flag for trained review, or record that the current campaign excludes the path.	Work-credit sufficiency, substantial gainful activity, or benefit eligibility.
Current work activity	Help the buyer determine whether its intake workflow needs a different conversation.	Escalate to trained intake, request a callback, or apply the buyer’s stated policy.	Whether SSA will find the caller disabled.
Communication need or language	Choose an accessible, appropriate intake path.	Language team, relay-compatible handling, accommodation process, or callback arrangement.	Call quality or a caller’s credibility.
Call type and source	Apply the buyer’s delivery and source-review rules.	Accept, route to test path, hold for review, or reject under an agreed delivery rule.	The caller’s legal case.

This format does two useful things.

First, it keeps a source from improvising legal or medical conclusions. A source can collect only the information it is authorized to collect and pass it as reported information, not as adjudicated truth.

Second, it prevents a buyer from hiding an undefined preference behind “not qualified.” If a buyer does not accept a particular claim stage, geography, call type, source, or representation status, it can state that policy upfront and record the result honestly.

Do not let commercial rules impersonate intake rules

A buyer’s commercial qualification rule and its intake policy may overlap. They should still be written separately.

For example, a campaign may define a buyer price around an answered, connected, or duration-based event. That can be an objective way to determine whether the buyer is charged. It says nothing by itself about whether the caller was appropriate for representation.

Likewise, a buyer may consider an inquiry worth a trained intake review even when it does not become billable under a particular delivery rule. A buyer may speak with a caller, decide the caller belongs in a different service path, and still owe the agreed commercial charge if the event met the contract definition.

Separate these four questions:

Question	Owner	Example of a clear answer
Should this call route now?	Routing policy	“This target is open for this geography, call type, source, and capacity level.”
Should intake continue or escalate?	Buyer intake policy	“A trained team will review this stated claim stage and work-activity signal.”
Does the event meet the buyer-price rule?	Commercial agreement	“The call met the defined connection and duration event, subject to agreed exclusions.”
Should representation be offered?	The organization’s approved representation process	“The organization made its own decision after its intake and conflict procedures.”

A buyer should not reverse-engineer its billable rule from whether a caller later becomes a client. That shifts an ordinary intake outcome into a retroactive traffic dispute. It also makes sources and operators unable to understand what the buyer actually purchased.

The same discipline applies to publisher payout. The buyer price is what Dependable Calls charges the buyer; the publisher payout is what Dependable Calls pays the publisher. Neither label should be used as a substitute for an intake disposition, representation result, or successful case outcome.

Capacity is part of a qualified call path

A call can meet every caller-side intake signal and still be unfit for delivery at that moment because the buyer cannot serve it.

That is not a flaw in the caller.

A serious definition includes buyer readiness:

Is the intended target open in the applicable time zone?
Is a trained intake person available to answer or own the callback?
Can the team support the caller’s language or communication needs?
Is the target under its relevant cap and concurrency limit?
Is the appropriate claim-stage team open?
Does the buyer have an approved overflow path that preserves the same boundaries?
Does the destination work and reach the intended team?

When the answer is no, the routing system should record a buyer-side reason such as closed schedule, cap reached, no eligible intake path, or destination problem. It should not label the caller unqualified merely because the buyer was unavailable.

This distinction matters when evaluating a source. If a source produces relevant inquiries that are routinely sent to an unanswered phone, the buyer has learned more about its capacity configuration than about the source’s quality.

The broader framework in Call Caps, Schedules, and Filters: The Controls Serious Buyers Need explains why eligibility and capacity controls belong in the routing decision. For SSDI buying, the policy should make the buyer-side no-route reasons visible.

Existing representation needs a respectful, explicit path

Existing-representation status is a common SSDI intake signal. It should not become a careless yes/no filter.

SSA explains that a representative is appointed by a claimant to act on the claimant’s behalf in the claim or appeal process, and it provides specific appointment and representation procedures. SSA’s representation guidance is a useful baseline for understanding why this status should be treated carefully.

A buyer’s policy should answer operational questions such as:

Which team receives an inquiry from a caller who says they already have a representative?
Does the organization require a specific intake review before discussing a new relationship?
Which team can answer a caller who is asking only for status help?
What information may a source collect or pass before the buyer’s own intake handles the conversation?
How should the system prevent an existing-representation signal from being shared more broadly than necessary?

The correct policy varies by organization and jurisdiction. What matters for a call buyer is that the policy exists before the call arrives and that its dispositions are not later rewritten as “bad lead” reasons.

Caller-initiated inbound calls and live transfers need different evidence

A caller-initiated inbound call and a live transfer can both be relevant. They are not the same delivery event.

For a caller-initiated inbound call, the buyer should understand:

What message, page, listing, or ad prompted the call.
What the caller reasonably expected from the organization that answered.
Whether the call was routed while the buyer was open and available.
What source, campaign, and call-type record follows the call.

For a live transfer, the buyer should additionally understand:

What the caller was told before the handoff.
Which high-level questions were asked.
Whether the caller agreed to be transferred.
What the receiving team was introduced as.
How the upstream agent records an incomplete or declined handoff.
Which records are available for a defined QA or dispute process.

Neither call type should be collapsed into one generic traffic label. The caller may have initiated the original inquiry in either flow, but a live transfer includes a separate assisted handoff. The buyer’s qualification rule needs to reflect that difference.

A transfer may reduce delay between the caller’s request and the buyer’s intake. It does not turn an upstream screen into a case decision. An inbound call may be highly relevant. It does not prove that the buyer had capacity to handle it.

Build the qualification policy around actions, not labels

A policy works only when the team can act on it consistently.

Instead of a single field called “qualified,” use a controlled set of dispositions. For example:

Relevant disability inquiry — buyer intake review.
Relevant but wrong program for this target.
Relevant but outside current service-area policy.
Relevant but wrong claim-stage route.
Existing-representation policy path.
Needs trained intake review.
Buyer unavailable — schedule, cap, concurrency, or destination reason.
Delivery-rule exception.
Commercially qualified under the agreed call event.
Not enough information to classify.

The goal is not to create an oversized form. It is to preserve why the caller reached a particular next step.

The best policy has one owner for each decision:

Decision	Recommended owner
What categories the target receives	Buyer practice or intake leadership
What questions an upstream source may ask	Buyer, source-review owner, and counsel where appropriate
What data is passed to routing	Buyer and technical or operations owner
What makes the buyer price billable	Commercial owners and written campaign terms
What counts as a representation	The organization’s authorized representation process
What disposition is recorded in intake	Intake leadership and CRM owner
What a source may see in feedback	Operations and privacy owners
What changes after a recurring problem	Buyer owner, exchange operator, and source-review process

This avoids a familiar failure: the source believes it sent a qualified call because a screen passed, while the buyer thinks the call was not qualified because no retainer was signed. Both parties are using the same word for different events.

Source evidence should support a review, not create a black box

A buyer should ask how the source came to label a call relevant or intake-qualified.

Good questions include:

Is this caller-initiated inbound traffic or a live transfer?
What did the consumer see, hear, or agree to before the call?
What exact questions are asked before a transfer, if any?
Which answers are passed as caller-reported information?
Which signals are source observations, system events, or buyer dispositions?
Is the SSDI/SSI/retirement classification captured separately?
What claim-stage labels are available, and how are they defined?
Which source, subsource, campaign, and creative records can be reviewed?
What happens when marketing, scripts, or screening questions change?
What evidence supports a dispute without unnecessarily sharing sensitive claimant information?
Can one source or subsource be paused without disrupting every other buyer path?

The full buyer checklist in What Buyers Should Ask Before Accepting Publisher Call Traffic is a useful foundation. For SSDI, the buyer should add one key rule: an upstream source should pass only the minimum information necessary for routing and the agreed review path.

A source does not need to collect a medical file, Social Security number, or detailed case documents to determine that the caller wants a disability-intake conversation. Collecting more sensitive information too early can create privacy, security, accuracy, and consumer-experience problems without improving the buyer’s decision.

Three hypothetical calls show why the labels must stay separate

Example 1: Relevant and routeable, but not yet intake-qualified

A caller reaches a disability-practice campaign after searching for help with a Social Security disability issue. The caller is in a state the buyer serves, the target is open, and the call reaches the buyer’s trained initial-intake team.

That makes the call relevant and routeable. It may be billable if the agreed commercial event is satisfied.

The intake team may still need to learn which program the caller is asking about, the claim stage, whether representation already exists, and whether the organization’s policy has an appropriate path. Until that review occurs, no one should label the caller eligible, retained, or a successful outcome.

Example 2: Relevant inquiry with an existing-representation signal

A caller is transferred after stating that they are seeking help with an SSDI matter but already have a representative. The buyer’s policy requires a specialized intake route for that situation.

The call can be relevant. It can be correctly transferred under an approved policy. The source can accurately record the caller’s stated representation status.

The buyer should not use the raw fact of existing representation to tell the caller what legal choice to make. It should follow its authorized policy, record the path, and avoid treating the caller’s situation as a generic source-quality failure.

A caller asks about retirement benefits or a private disability-insurance policy. The buyer accepts only certain Social Security disability matters.

The caller may be sincere and may need help. The inquiry is simply outside this target’s defined scope. The right disposition is a clear out-of-scope or alternate-path result—not a claim that the caller is unqualified for benefits.

These examples are hypothetical. They demonstrate the discipline of classification, not a script or a case-selection rule.

Measure the definition against source-level performance and intake dispositions

A buyer’s definition should become more precise after a controlled test, not looser after a disagreement.

The reporting view should distinguish at least:

Source and subsource.
Call type: caller-initiated inbound or live transfer.
Program or inquiry category as defined by the buyer.
Claimed stage or intake route.
Target and delivery time.
Route, answer, and connection result.
Buyer-side capacity or no-route reason.
Intake disposition.
Commercial qualification and billable status.
Duplicate, dispute, credit, or adjustment status.
Later representation or outcome data only when the buyer is authorized to use it and the model requires it.

Raw volume cannot explain what to improve.

If a source delivers many relevant calls but a buyer target has low answer rates, fix the target before calling the source poor. If one transfer path produces repeated category confusion, review its script and the introduction. If a particular intake disposition appears frequently from one subsource, compare the source’s consumer journey with the buyer’s stated policy.

This is the SSDI version of a broader principle: evaluate a call source before scaling it by tracing where the result changes, not by treating every non-retained caller as evidence of bad traffic.

A buyer-side definition to use before a test

Before enabling an SSDI source, a buyer should be able to complete this checklist.

We have defined the specific SSDI, SSI, retirement, and adjacent inquiries this target may receive.
We have written a definition of relevant inquiry, routeable inquiry, buyer-defined intake qualification, commercial qualification, representation, and outcome.
We have stated which of those terms the source may use publicly and which belong only to buyer intake.
We have documented service area, schedule, answer capacity, overflow, callbacks, language, and communication-accommodation paths.
We have identified the claim-stage routes the team actually handles.
We have written a counsel-aware policy for existing-representation signals and sensitive information.
We have defined which work-history and work-activity signals may trigger review without treating them as SSA conclusions.
We have separated caller-initiated inbound calls from live transfers.
We have defined the buyer-price event separately from a retained matter or successful case outcome.
We have agreed on the evidence and reason codes used for duplicates, delivery exceptions, disputes, credits, and reconciliation.
We can review results by source and subsource before increasing volume.
We have named who can pause a source, lower a cap, change intake criteria, or approve a material policy change.

If the team cannot complete that list, the right next step is not more filtering. It is to finish the operating definition before more calls arrive.

How this fits Dependable Calls

Dependable Calls is a controlled, operator-led, beta-stage pay-per-call exchange being built around reviewed sources, buyer-selected source enablement, target-level routing controls, source-level visibility, and explainable operating records.

For a buyer, the source-enablement model has two separate gates:

Dependable Calls decides which reviewed sources are appropriate to offer to that buyer.
The buyer decides which offered sources to enable for a specific target or call path.

Both gates must be satisfied before a curated source routes.

That model does not decide whether a caller qualifies for SSDI. It does not promise call volume, eligible claimants, signed clients, exclusivity, compliance, or case outcomes. It creates a controlled place to apply the buyer’s documented rules, inspect source-level performance, and pause or refine a path when the evidence says it needs attention.

A source can be reviewed and still be a poor fit for a particular SSDI target. A caller can be relevant and still require a different intake path. A billable call can still fail to become a retained representation. Separating those facts is how a buyer avoids turning intake ambiguity into an unproductive argument about traffic quality.

If your organization can define its intake policy, capacity, service area, source-review needs, and reporting requirements, you can apply to discuss a potential buyer relationship. Any campaign remains subject to availability, review, and operational fit.