SSDI and disability calls are easy to label broadly and difficult to operate well.

A buyer may say it wants “disability calls.” A publisher may say it can generate “SSDI traffic.” Neither statement tells the exchange enough to decide whether the next caller belongs in that buyer’s intake path.

The caller might be considering an initial application. They might have received a denial and be trying to understand an appeal. They might already have a representative. They might be asking about Supplemental Security Income rather than Social Security Disability Insurance. They might need general information from the Social Security Administration rather than representation from a private firm. They may also have communication, mobility, vision, hearing, cognitive, or technology-access needs that affect how they use a landing page, complete a form, or speak with an intake team.

That is why an SSDI call should not be treated as a generic legal call with a disability label attached.

For buyers, the value of the call depends on fit, timing, claimant expectation, intake readiness, and the buyer’s ability to serve that person. For publishers, the durability of the traffic depends on truthful marketing, clear source packaging, accessible caller paths, and enough segmentation to show what is actually being sent.

This guide explains the operating questions buyers and publishers should answer before scaling SSDI or disability call traffic.

This article is for general educational purposes and is not legal advice. Social Security representation, advertising, privacy, accessibility, telemarketing, professional-responsibility, and state-law questions should be reviewed with qualified counsel.

Start with the program: SSDI is not a generic disability benefit

The Social Security Administration describes Social Security Disability Insurance, or SSDI, as a program that provides monthly payments to people whose disabilities stop or limit their ability to work. Eligibility generally depends on both a qualifying disability and enough covered work history.

That makes SSDI different from a broad consumer understanding of “disability.”

A caller may use the word disability to refer to:

SSDI.
Supplemental Security Income, or SSI.
A private disability-insurance policy.
Workers’ compensation.
Veterans disability benefits.
Short-term or long-term disability through an employer.
An accommodation or employment issue.
A general Social Security question.
A medical condition without a current benefits claim.

Those categories may sound related to a consumer, but they are not interchangeable intake paths.

SSA explains that SSDI is tied to disability and work history, while SSI is a separate program based on disability, age, income, and resources. A buyer may handle SSDI, SSI, or both. A publisher should not assume that any caller who says “I’m disabled” fits the same campaign.

The first quality control is therefore basic classification:

What kind of help does the caller believe they are seeking?

That question should be answered without pretending the publisher, exchange, or intake screener has made an eligibility decision.

A valuable call is not the same as an eligible claimant

Pay-per-call operators need to separate commercial qualification from legal or program eligibility.

SSA uses a detailed process to decide whether an applicant meets its definition of disability. The agency looks at issues such as covered work history, current work activity, the severity and expected duration of the condition, the applicant’s ability to perform prior work, and the ability to adjust to other work. SSA states that its program pays for total disability rather than partial or short-term disability, and that the condition generally must last or be expected to last at least 12 consecutive months or result in death.

For 2026, SSA says it generally considers monthly earnings above $1,690 to be substantial gainful activity for a non-blind applicant and above $2,830 for an applicant who is blind. Those figures change over time and should never be hardcoded into long-lived marketing or intake logic without a dated update process. The current official standards belong on SSA’s eligibility page, not in an unmaintained publisher script.

A buyer can define a call-acceptance rule. It cannot outsource the government’s eligibility determination to a media buyer or routing tree.

A practical call qualification might ask whether the caller:

Is seeking help with SSDI, SSI, or a related Social Security disability matter.
Is calling for themselves or has authority to speak for the claimant.
Lives in a geography the buyer serves.
Is at a claim stage the buyer accepts.
Is not already represented, unless the buyer has a lawful and appropriate process for that situation.
Can be reached and served by the buyer’s intake operation.
Understands that the buyer is a private organization and not SSA.
Has not been promised approval, benefits, or a specific outcome.

Those questions can help determine routing fit. They do not establish that the person will qualify for benefits.

That distinction protects everyone. It keeps publishers from turning intake questions into promises. It keeps buyers from paying for a definition that sounds precise but is impossible for an upstream source to prove. It also helps exchanges record why a call routed without pretending that routing was a legal judgment.

Claim stage changes the meaning of the call

Two callers can have similar medical conditions and still need very different help because they are at different stages.

An SSDI campaign should define which stages the buyer accepts.

Considering an initial application

The caller may have stopped working, reduced work, or begun researching benefits. They may not know whether SSDI or SSI applies. They may have medical treatment but no organized records. They may be early enough that the buyer’s intake team needs to educate before deciding whether representation is appropriate.

This traffic can be useful, but “interested in disability” is not enough. The buyer needs a clear policy for early-stage inquiries.

Application started or pending

The caller may have already filed and want help with a pending matter. The buyer needs to know whether it accepts claims at that stage, what information intake may request, and how it handles a caller who has already appointed another representative.

Denial or appeal

A denial changes urgency and workflow. SSA’s representative resources state that requests for disability and non-medical appeals generally must be received within 60 days after the claimant receives the decision.

That does not mean a publisher should give deadline advice. It means the campaign should recognize that an appeal-related call may need immediate, competent handling rather than a slow callback queue.

The call record should identify the stage accurately enough to support routing and urgency without collecting unnecessary case documents in the marketing layer.

Existing representation or case-status questions

Some callers are not seeking a new representative. They may already have counsel, want an update, be trying to reach SSA, or be confused about who is handling the matter.

These calls should not be forced into a “new case” category just because the caller mentioned disability benefits. The buyer and publisher should agree on how already-represented callers, existing clients, and general status questions are handled.

Non-SSDI disability inquiries

A caller may actually need help with a private policy, veterans benefits, workers’ compensation, employment rights, or another program.

A clean source does not hide these mismatches. It labels them, excludes them when possible, and gives the buyer enough information to understand whether the issue is targeting, creative, keyword breadth, or caller confusion.

Buyers need to define the case they can actually serve

A buyer should not start an SSDI campaign with only a payout and a duration threshold.

It should first document the operating boundaries of the intake practice.

Service area and representation model

The buyer should clarify:

Which states or territories it serves.
Whether it accepts initial applications, appeals, or both.
Whether it handles SSDI, SSI, or both.
Whether it accepts adult claims, child claims, disabled adult child matters, or other specialized categories.
Whether it is a law firm, an attorney representative, an eligible non-attorney representative, or another kind of intake organization.
Which languages and communication methods it supports.
When licensed or authorized staff are available.
Whether it accepts transfers, consumer-initiated inbound calls, or both.

SSA maintains registration and appointment processes for claimant representatives. Buyers should verify their own authority, registration, fee, advertising, and professional obligations. An exchange should not infer that every organization using the word “advocate” or “disability help” is authorized to handle every caller.

Intake capacity

A buyer may be commercially interested in 100 calls and operationally able to handle only a small number at once.

SSDI intake can require patience. Callers may need more time to explain medical history, work history, treatment, denials, dates, and prior representation. Some may need a relay service, interpreter, caregiver participation, slower pacing, or an alternate communication method.

The buyer should determine:

How quickly calls are answered.
How many trained intake staff are available by hour.
How long a normal first conversation takes.
Whether ringing calls consume capacity.
How callbacks are queued.
What happens after hours.
How urgent appeal-stage calls are escalated.
Whether intake can accommodate callers who cannot complete a standard phone flow.
How many simultaneous calls the team can handle without degrading service.

The same principles explained in how caps, schedules, and concurrency shape call flow apply here. A daily call appetite does not prove that an intake team is available for the next caller.

Acceptance and rejection reasons

A buyer should define rejection reasons before launch, not after invoice review.

Useful reason categories may include:

Wrong benefit or legal category.
Outside service area.
Claim stage not accepted.
Already represented.
Caller seeking SSA rather than a private representative.
Duplicate within the agreed lookback period.
Caller did not request the advertised help.
Publisher or transfer agent materially misrepresented the service.
No meaningful connection to the buyer.
Technical failure.
Buyer-side no-answer or handling failure.
Accepted for review but not ultimately retained.

The final category matters. A caller can be a valid, billable intake opportunity without becoming a client. If the commercial agreement pays for a qualified call, the buyer should not convert every non-retained matter into a traffic dispute.

That is one reason buyers should review what makes a qualified inbound call before setting SSDI call rules.

Publishers need to package SSDI traffic with more precision

Publishers should be able to explain the caller path from first impression to buyer connection.

A useful traffic package should identify:

The traffic type: consumer-initiated inbound, warm transfer, scheduled callback, or another approved flow.
The media channel.
The source and subsource.
The landing page or call experience.
The wording used to describe the service.
Whether the campaign is SSDI-only, SSI-only, or combined.
Which claim stages are targeted or screened.
Which geographies are included.
Whether calls are generated in English, Spanish, or other languages.
Whether the source uses owned media, affiliate traffic, a network, or another supply relationship.
What happens before a transfer.
Which data is collected before the call.
What consent and follow-up records are maintained.
How creatives and pages are reviewed when changed.

The purpose is not paperwork for its own sake.

The package tells the buyer what the caller likely expects. It gives the exchange enough information to route the source deliberately. It gives the publisher a defensible way to show that one source, subsource, or traffic type should not be judged by the problems of another.

Publishers can use the broader checklist in how to prepare traffic for buyer review, but SSDI traffic deserves several additional controls.

Marketing must not create a false government connection

SSDI marketing naturally uses terms such as “Social Security,” “SSA,” “SSI,” and “disability benefits.” Those terms are necessary to explain the subject. They also create a serious risk when the page, ad, envelope, phone script, or visual design makes a private service look official.

Section 1140 of the Social Security Act prohibits using specified Social Security and Medicare names, acronyms, symbols, or lookalike materials in a way that a person knows or should know would convey—or could reasonably be interpreted as conveying—a false impression of approval, endorsement, authorization, or government connection.

Operationally, that means a source-review process should look beyond a footer disclaimer.

Review the full impression created by:

Government-style seals, emblems, cards, envelopes, or colors.
Domain names and sender names.
“Official,” “approved,” or “authorized” language.
Countdown language implying a government deadline.
Claims that the caller was selected or prequalified by SSA.
Forms that resemble government applications.
Caller-ID names.
Transfer introductions.
Statements about guaranteed approval or benefit amounts.
Disclaimers that are visually buried or contradicted by the rest of the page.

A truthful private-service disclosure should be easy to see and understand. It should not be used as a small-print defense for an otherwise misleading experience.

Publishers should preserve the actual creative and landing page used for each source. Buyers should review them before launch and again when material changes occur. Exchanges should be able to pause the affected source without shutting down every publisher relationship.

This is where compliance becomes an operating differentiator, not merely a paragraph in a contract.

Accessibility is part of call quality

A disability campaign that is difficult for people with disabilities to use has a quality problem before the phone rings.

The Department of Justice explains that inaccessible web content can deny people with disabilities equal access to information and services. Its guidance highlights practical barriers such as low color contrast, missing text alternatives, videos without captions, forms without labels, unclear error messages, and interfaces that cannot be operated with a keyboard.

For SSDI publishers and buyers, accessibility should be treated as a source and intake requirement.

A reasonable review should include:

Sufficient text contrast.
Text that can be resized without breaking the page.
Descriptive headings.
Form fields with programmatic labels.
Clear instructions and error messages.
Keyboard navigation.
Useful alternative text for meaningful images.
Captions for material video content.
A phone path that does not require a consumer to complete an inaccessible form first.
Options for callers who are deaf, hard of hearing, blind, have low vision, have limited dexterity, or need another communication aid.
Plain language that reduces unnecessary cognitive load.

Accessibility is not only a legal review topic. It changes the traffic itself.

An inaccessible form can create abandoned leads, repeated submissions, wrong answers, and callers who reach the buyer frustrated. A transfer script that does not account for a relay call can be mistaken for poor intent. An intake agent who rushes a caller with a speech disability can turn a valid inquiry into a short-call dispute.

A serious operation should ask whether the caller path works for the people the campaign is intended to serve.

Consumer-initiated calls and transfers should be separated

SSDI calls can arrive through different models, and those models should not be blended casually.

Consumer-initiated inbound calls

The caller sees an ad, page, listing, or other message and chooses to call.

The buyer should review:

What prompted the call.
Whether the marketing accurately describes a private service.
Whether the page distinguishes SSDI from other disability matters.
Whether the caller can understand who will answer.
Whether source and subsource are passed with the call.
Whether broad keywords are attracting unrelated benefit questions.

Live transfers

A publisher or call center speaks with the caller before connecting them.

The buyer should additionally review:

How the original consumer inquiry was generated.
What the first agent said.
Which questions were asked.
What qualified the caller for transfer.
Whether the caller agreed to the handoff.
How the receiving organization was introduced.
Whether sensitive information is repeated unnecessarily.
What happens when no buyer is available.
Whether sample calls and QA records are available for review.

A warm transfer can create a strong caller experience when the handoff is accurate and the receiving team is ready. It can create confusion when the caller thinks they are already speaking with SSA, believes approval is guaranteed, or is transferred repeatedly.

The operational differences are covered more broadly in consumer-initiated inbound calls versus transfers. For SSDI campaigns, the distinction should be included in source approval, routing, reporting, and dispute review.

Follow-up rules should be designed before the first missed call

An inbound call does not answer every compliance question about later outreach.

A caller may hang up, reach voicemail, request a callback, submit a form, or ask to be contacted at a different time. The buyer, publisher, and any call center involved should know who may follow up, through which channels, for how long, and based on what records.

The FTC’s Telemarketing Sales Rule guidance describes exemptions for some inbound calls, but its guidance also makes clear that exemptions are context-specific and that federal and state rules can still apply to telemarketing conduct, Do Not Call requests, caller identification, and later calls. The FCC and states may impose additional requirements.

Do not reduce this to “the consumer called us, so anything after that is allowed.”

Before launch, qualified counsel should review:

The original call-to-action and any consent language.
Who is identified as the caller or seller.
Whether the buyer, publisher, and vendors are covered by the wording used.
Live-call, prerecorded-call, text, and email follow-up.
Entity-specific Do Not Call requests.
National and state Do Not Call rules.
Caller-ID practices.
Record retention.
Suppression sharing among authorized parties.
State professional-advertising and solicitation rules.

The operational system should preserve the records needed to apply the approved policy. It should not invent a legal conclusion from the fact that a phone number exists.

Collect less sensitive information in the marketing layer

SSDI callers may discuss medical conditions, medications, treatment, employment history, income, family circumstances, identity information, denial notices, and financial hardship.

That does not mean every field belongs in a publisher form, RTB ping, routing URL, or analytics platform.

The marketing and routing layer should collect only what is needed to:

Understand the requested category.
Determine whether an approved buyer path may fit.
Route the caller safely.
Support the agreed source, consent, and audit record.

Avoid placing highly sensitive data into query strings, source labels, campaign names, recordings shared as ordinary files, or broad analytics tools. Social Security numbers, full medical records, government account credentials, and detailed case documents generally do not belong in a basic lead form or routing payload.

The buyer’s secure intake process can collect information that is genuinely needed after the caller reaches the appropriate organization.

Data minimization improves security and call quality. It also reduces the chance that an upstream screener starts acting like an adjudicator.

Routing should reflect the buyer’s real SSDI practice

A single “SSDI” campaign label is not enough for controlled routing.

A routing decision may need to consider:

SSDI, SSI, or both.
Initial application or appeal.
Adult, child, or other accepted matter type.
Caller geography.
Buyer service area.
Language.
Consumer-initiated inbound or transfer.
Source approval.
Buyer schedule.
Buyer concurrency.
Daily or test cap.
Existing-representation response.
Duplicate policy.
Appeal urgency.
Destination health.
Buyer funding and commercial eligibility.
Required metadata or reservation.

Not every buyer needs every filter. Every filter should reflect a real operating difference.

A hypothetical routing example

Suppose a publisher sends two calls labeled “disability.”

The first caller is in a state the buyer serves, is seeking help after an SSDI denial, is not currently represented, and called from an approved consumer-initiated source. The buyer accepts appeals, is open, and has intake capacity.

The second caller is seeking help with a private employer disability policy. The same buyer handles only Social Security claims.

A broad keyword label makes the two calls look identical. A controlled routing process does not.

The first call may fit the buyer path. The second should be excluded or sent only to a separately approved buyer that handles that category. The exchange should record the reason rather than letting the second call ring, fail, and become a vague quality complaint.

Dependable Calls is being built around this kind of controlled, B2B call routing. The current product direction uses operator-curated source access rather than unrestricted buyer discovery: Dependable Calls determines which reviewed sources are appropriate to offer, and the buyer determines which offered sources to enable for a target. Both gates matter.

That model can help with SSDI traffic only when the underlying source review, vertical labels, buyer rules, and live validation are accurate. Software controls do not turn a poorly defined source into a good one.

Duplicates require a campaign-specific policy

Duplicate disputes can become especially confusing in disability traffic because a claimant’s matter may continue for months or years.

A simple “same phone number appeared before” rule may be too broad. A rule with no lookback may be too weak.

The agreement should define:

The identity fields used for matching.
The duplicate lookback period.
Whether the lookback is buyer-specific, campaign-specific, or source-specific.
Whether an initial-application inquiry and later appeal are treated as the same opportunity.
How shared family phone numbers are handled.
What happens when the caller previously contacted the buyer but was never reached.
Whether existing clients are excluded.
What evidence is returned to the publisher without exposing unnecessary claimant information.
Which timestamp controls.
Whether a duplicate blocks routing or becomes a later dispute.

The exchange should avoid disclosing one buyer’s claimant data to a publisher or another buyer. A useful duplicate response can state that a call is ineligible under the agreed rule without exposing another relationship.

Billing should follow the agreed event, not the buyer’s final case outcome

The commercial agreement should identify what earns the buyer price and what earns the publisher payout.

Possible structures include:

A connected call that reaches a stated duration.
A qualified call that meets defined routing and intake criteria.
An accepted transfer with a valid handoff.
A later retained-client or approved conversion event.
Another clearly documented CPA outcome.

Those events are not the same.

A routed call may fail to connect. A connected call may be the wrong category. A qualified call may not become a client. A retained matter may later be declined or withdrawn. A successful claim may take substantial time and depends on factors outside the publisher’s control.

Buyers and publishers should not collapse routed, connected, qualified, billable, payable, retained, approved, and paid into one status.

The article on routed, qualified, and billable calls explains the broader distinction. For SSDI campaigns, the settlement rule should also state how claim stage, wrong-category calls, already-represented callers, duplicates, technical failures, and buyer no-answers are handled.

Duration is evidence, not the whole truth

A duration threshold can be useful, but it is not a complete quality definition.

A short call could mean:

Wrong category.
Caller confusion.
A duplicate identified quickly.
A buyer no-answer.
A transfer failure.
An accessibility or communication breakdown.
A caller who only wanted SSA.
A buyer agent ending a potentially valid call too quickly.

A long call could still be misrouted or misleadingly generated.

Use duration with source, call type, connection result, stage, recording or QA evidence where lawful, dispute reason, and buyer handling data. One number should not carry the entire meaning of the call.

Reporting should make optimization possible

An SSDI report should help the parties answer why performance changed.

Useful dimensions include:

Source and subsource.
Traffic type.
Creative or landing-page version.
SSDI, SSI, or other category.
Claim stage.
Geography.
Language.
Buyer target.
Route result.
Connection result.
Duration.
Qualification result.
Billable and payable status.
Duplicate result.
Dispute reason.
Buyer answer rate.
Transfer completion rate.
Retained or converted outcome when the commercial model uses it.
Date and hour.

The goal is not to expose every piece of claimant information.

The goal is to separate operational causes.

If one source has a high wrong-category rate, review the targeting and creative. If one target has a low answer rate, review capacity and routing. If transfers from one subsource have repeated caller-confusion disputes, review the upstream script. If qualified calls connect but rarely move forward, the buyer should review intake before declaring the entire source bad.

Serious buyers should ask these questions before accepting traffic. The detailed checklist in what buyers should ask before accepting publisher calls is a useful starting point.

A buyer checklist before launch

Before accepting SSDI or disability calls, a buyer should be able to answer:

Which programs and matter types do we handle?
Which claim stages do we accept?
Which geographies do we serve?
What authority, registration, licensing, and advertising rules apply to us?
Which traffic types do we accept?
Which sources have we reviewed and approved?
What must the caller have requested?
Which questions may an upstream screener ask?
Which questions must be left to our intake team?
How do we identify already-represented callers?
What is our duplicate policy?
What counts as connected, qualified, billable, payable, or converted?
Which failures are buyer-side rather than publisher-side?
How quickly can we answer and return calls?
What are our schedule, cap, and concurrency limits?
How do we accommodate callers with disabilities?
Which languages and communication methods do we support?
What follow-up policy has counsel approved?
What evidence is available for disputes?
Who can pause a source when a problem appears?

If several answers are unclear, the buyer is not ready for meaningful scale.

A publisher checklist before launch

Before offering SSDI traffic, a publisher should be able to answer:

What program does the source actually target?
What claim stage is the caller likely to be in?
How is the caller generated?
What does the caller see and hear before the call?
Is the private nature of the service clear?
Could the overall impression be mistaken for government communication?
Are approval, benefit, urgency, or outcome claims supportable?
Is the landing page and form accessible?
Are consumer-initiated calls and transfers separated?
What screening occurs before a transfer?
Which source and subsource labels are passed?
Which geographies and languages are included?
What sensitive data is collected, and can it be reduced?
What follow-up consent and suppression records exist?
How are creative changes reviewed?
Can one source be paused without shutting down everything?
What test volume is appropriate?
Which reports will be provided?
How will disputes be investigated?
What would cause the publisher to stop a subsource voluntarily?

A publisher that can answer these questions is easier to evaluate than one offering only a price, duration, and volume estimate.

What a serious SSDI call operation looks like

A dependable SSDI call program is not defined by the largest number of calls.

It is defined by whether the parties can explain:

What the caller was looking for.
How the caller entered the flow.
Whether the marketing was truthful.
Whether the experience was accessible.
Which source produced the call.
Which buyer rules were evaluated.
Why the target was eligible.
Whether the buyer had capacity.
What happened during the connection.
Which commercial event occurred.
Why the call was paid, rejected, or disputed.
What should change before the next call.

Dependable Calls publicly identifies SSDI as one of the B2B call categories it is working with, but vertical availability, buyer fit, source approval, and operating readiness must be validated in the live beta. The platform should not be presented as proof that every SSDI source is approved, every buyer is available, or every workflow is mature.

The objective is narrower and more useful:

Build call flow that serious buyers and publishers can understand, control, and improve.

Buying or generating SSDI and disability calls? Contact Dependable Calls to discuss current vertical availability, source fit, and beta readiness.