Buying SSDI calls is not primarily a media-buying decision. It is an intake-operations decision.

A disability practice can receive more inquiries and still create a worse outcome for prospective clients, intake staff, and the practice itself if the calls arrive outside its service area, after its team has stopped answering, at a rate the team cannot absorb, or with expectations the team did not set. The same is true when a firm labels every non-retained call “bad” without first separating the call’s source, the buyer’s stated acceptance policy, and the firm’s own handling.

A serious buyer starts by deciding what it can responsibly receive, how it will evaluate a call, and which records it needs to improve the next decision. Only then should it purchase a controlled test.

This guide is for disability law firms, established non-attorney representatives, advocacy organizations, practice leaders, and intake teams that can operate a real buyer campaign. It explains how to define the target claimant, service area, hours, acceptance policy, source-review requirements, test volume, and reporting before a source sends the first call.

It is not a claimant eligibility tool or legal advice. The Social Security Administration—not a call source, exchange, or intake script—decides whether a claimant meets the program’s requirements. Firms should have qualified counsel review their particular advertising, attorney-conduct, privacy, recording, and follow-up practices.

For the broader buyer-and-publisher view of the vertical, start with SSDI / Disability Calls: What Buyers and Publishers Should Know. This article focuses on the buyer’s operating model.

Start with the capacity you can actually serve

The wrong first question is, “How many SSDI calls can we buy?”

The right first question is, “What happens if the next appropriate caller reaches us right now?”

An SSDI inquiry often needs more than a quick intake handoff. A caller may be looking for help with an initial application, a pending claim, a denial, an appeal, an existing representative, or a different Social Security benefit altogether. They may need an interpreter, a relay-service-compatible conversation, a caregiver present, a slower explanation, or a callback from a specific team. A campaign that merely reaches the phone number is not necessarily reaching the practice.

Before purchasing calls, document the operational answers:

Who can answer during each delivery hour, in the relevant time zone?
What is the normal answer-time expectation?
How many concurrent new inquiries can the team handle without putting callers on an unworkable hold?
What happens when every intake specialist is occupied?
Who owns missed calls and callbacks, and how quickly are they worked?
Which days, holidays, lunch windows, and after-hours periods are genuinely covered?
Which languages and communication accommodations can the team support?
Which states and matter types can the organization actually serve?
Who can pause a source or lower a cap if the team falls behind?

A daily cap is useful, but it is not a capacity plan. Ten calls all arriving within one hour can overwhelm a team that can comfortably handle ten calls over an entire day. An after-hours schedule is not real coverage if the only outcome is an unattended voicemail with no owned callback process.

The broader framework in what makes a pay-per-call buyer ready to scale applies directly: capacity is a live operating constraint, not an aspiration. The buyer should set rules from answer capacity and follow-up capacity, then expand only when the evidence supports it.

Define the outcomes before you buy the first call

“Qualified SSDI call” is not a single outcome. It compresses several very different events into one label, which is why buyers and suppliers can appear to disagree even when they are describing different stages.

Use a shared operating vocabulary before a campaign begins.

Term	What it means operationally	What it does not mean
Relevant disability inquiry	A caller appears to be seeking help in a category the buyer has chosen to review.	The caller is eligible for SSDI, is a client, or should be billed.
Buyer-defined qualification	The call meets the buyer’s documented commercial and intake-policy criteria.	SSA has found the claimant disabled or the firm must accept representation.
Connected call	The buyer-side intake path answered or otherwise completed the defined connection event.	The caller received useful counsel, met the buyer’s policy, or became billable.
Billable event	The event the commercial agreement says earns the buyer price, such as a connected call, a defined duration, an accepted transfer, or another documented condition.	A retained representation, a paid claim, or a successful case outcome.
Retained representation	The organization and caller complete whatever intake, conflict, engagement, and representation steps the organization requires.	A favorable SSA decision or a reason to rewrite the campaign’s call qualification rule.
Successful case outcome	A later case result defined outside the call-routing layer.	Evidence that every earlier call in the source was appropriate or that every caller will have the same result.

This separation protects the buyer’s decision-making.

A relevant inquiry can be valuable even when the firm ultimately does not retain the matter. A caller may be outside the firm’s policy, already represented, unable to complete intake, or seeking an adjacent benefit. Conversely, a call that reaches a duration threshold can still expose a source, buyer-script, or capacity problem.

The commercial agreement should name the billable event plainly. If a buyer price is attached to a call, the buyer should know whether the trigger is connection, duration, buyer-defined qualification, an accepted transfer, or a later documented outcome. Those terms should not be changed retroactively because a call did not become a signed client.

For a fuller explanation of why these stages should stay separate, see the buyer’s guide to qualified inbound calls.

Build a buyer-owned acceptance policy—not an eligibility script

A firm needs a written acceptance policy before it needs a large cap.

The policy should answer: “Which incoming inquiries do we want to review through this campaign, and which do we need to route differently, decline under our policy, or treat as a non-billable mismatch?”

It should not attempt to answer: “Does this person qualify for SSDI?”

SSA explains that SSDI generally involves covered work history and a medical condition meeting Social Security’s definition of disability. The agency evaluates work activity, medical evidence, past work, and ability to adjust to other work through its own process. See SSA’s current eligibility guidance. That is far beyond what an upstream marketing source or a brief intake screen should claim to decide.

A practical buyer policy can use observable routing signals, such as:

The caller says they are seeking help with an SSDI matter, an SSI matter, a retirement question, or another type of benefits or disability issue.
The caller is located in a state the buyer serves.
The caller is asking about an initial claim, a pending claim, a denial, an appeal, or a status issue.
The caller says they already have a representative, are an existing client, or are seeking SSA directly.
The caller can be reached by the buyer’s approved intake process.
The caller confirms the request reflected in the advertising or transfer introduction.
The call arrived through an approved call type and source path.

Work history and current work activity can matter to a firm’s intake prioritization because SSA’s SSDI program includes work-related requirements and evaluates work activity. They are still signals, not conclusions. The same is true of age, medical-treatment history, diagnosis, claim stage, and a caller’s own description of why they stopped working.

A buyer should define how its team handles each signal:

Signal	Example buyer-policy question	Appropriate outcome
Work history	Does the caller describe recent covered work history that our intake team wants to explore?	Continue intake or route for a more detailed review; do not promise eligibility.
Current work activity	Does the caller report current work that requires a specialized intake path?	Apply the firm’s policy or escalate to trained staff; do not adjudicate the claim.
Claim stage	Is the caller seeking an initial application, help with a pending claim, or an appeal?	Route to the team that handles that stage, or state that the stage is outside current policy.
Existing representation	Does the caller already have counsel or another representative?	Follow the organization’s ethical and operational policy; do not force the call into a new-client flow.
SSI or retirement inquiry	Is the caller asking about a different Social Security program?	Apply the buyer’s routing policy, rather than calling it an SSDI match by default.

SSDI, SSI, and retirement are related in a caller’s mind but not interchangeable programs. SSA describes SSI as a needs-based program for eligible people with limited income and resources who are disabled, blind, or age 65 or older. SSA’s SSI overview is a useful baseline for training intake teams on the distinction. Retirement questions may also need their own route or an explanation that the buyer does not handle them.

A useful policy has three layers:

Routing rule: Can this inquiry enter this target’s intake path?
Intake disposition: What did the trained team learn or decide to do next?
Commercial treatment: Does the agreed call event qualify as billable, disputable, or excluded?

Keeping those layers separate lets the firm improve its intake without turning a source rule into an improper legal conclusion.

Turn capacity into delivery rules

Once the buyer knows who it can serve, translate that into delivery rules a routing operation can apply.

Service area

Start with the states and, where appropriate, more specific areas the organization can serve. “Nationwide” should not be a default label unless the practice, authority, staffing, and operating policy genuinely support it.

The buyer should document how it handles callers who are:

Physically located outside its service area.
Calling about a matter centered in another state.
Moving between states.
Calling on behalf of a claimant in a different state.
In a language or communication situation the designated team cannot support at that moment.

Source geography should be accurate enough to support a rule, but the system should not create false precision. A buyer that only trusts state-level geography should not pretend it has a ZIP-level rule. A buyer that needs a county or radius decision should make that requirement clear before a source launches.

Hours, coverage, and callbacks

Set schedules in the target’s operating time zone. Document the difference between:

Live-answer hours.
Hours when a trained intake team can accept a transfer.
Hours when an intake form or voicemail can be taken responsibly.
Hours when a callback owner is available.
Hours when appeal-related or otherwise urgent inquiries have a defined escalation path.

Do not use a broad “open” schedule to hide a slow callback model. If callers can arrive when no one can provide the promised experience, the source needs a different route, a narrower schedule, or a clearer consumer expectation.

Caps, concurrency, and overflow

Daily caps limit total volume. Concurrency limits protect the team at the moment calls cluster. Both need an owner and an escalation path.

A buyer should decide:

The daily test cap.
The maximum number of simultaneous new calls the intake team can take.
Whether the cap resets in the buyer’s local time zone.
What happens at the cap: stop delivery, switch to an approved overflow path, or collect a callback request.
Which overflow paths are commercially and operationally eligible.
Who can lower the cap immediately when answer speed, abandonment, or queue length deteriorates.

The detailed mechanics are covered in call caps, schedules, and filters. For SSDI, the governing principle is simple: do not ask a source to create demand faster than the practice can honor the caller’s request.

When a buyer wants the underlying decision mechanics—not just the controls—Pay-Per-Call RTB Explained shows how a route can be evaluated before a call is delivered.

Call type

Treat caller-initiated inbound calls and live transfers as different delivery products.

For a caller-initiated inbound call, review the ad, landing page, phone number, and consumer expectation before the call. For a live transfer, review that entire journey plus the upstream conversation, handoff language, screening questions, and what happens when no buyer is available.

The firm’s intake greeting and workflow should fit the call type. A team receiving a warm transfer should not act as though it is answering an unexplained cold call; a team receiving a caller-initiated inquiry should not assume an upstream agent explained facts that no one actually covered.

Start with a controlled test, not a volume commitment

A controlled test should answer a few specific questions. It should not be a vague attempt to “see if SSDI calls work.”

Define the test in writing:

One target claimant and buyer-owned acceptance policy.
One service-area and coverage configuration.
One defined call type.
One or a small number of reviewed sources.
A conservative daily cap and concurrency limit.
A defined test period.
Required source and call-level reporting fields.
A named owner for intake dispositions.
A review cadence and explicit pause conditions.

Hypothetical example

A multi-state practice wants to test calls from one reviewed live-transfer source.

It limits delivery to weekday hours when two trained intake specialists are available, begins with a low daily cap, and directs overflow to a documented callback queue. Its acceptance policy says which claim stages it will review, how it flags existing representation, how it separates SSI and retirement questions, and which dispositions need immediate escalation.

At the end of each week, the practice reviews source-level call records next to intake dispositions: answered, completed intake, outside policy, duplicate under the agreed rule, wrong category, callback required, no contact after callback, retained, and not retained.

The test does not ask, “Did every call become a client?”

It asks:

Did the source send calls consistent with the agreed caller journey?
Did the team answer them at the promised time?
Did the buyer’s stated acceptance policy match the inquiries actually received?
Were intake dispositions captured reliably?
Did a specific source, time window, or call type create repeated mismatch?
Is the next improvement a source change, a target rule change, an intake change, or no scale at all?

A buyer that cannot answer those questions should not increase the cap merely because the raw call count looks attractive.

Review the source before the source turns on

Source review is not a single yes-or-no check. It is a record of what the buyer is agreeing to receive.

Ask for enough information to evaluate the real consumer journey without requesting unnecessary claimant data or protected commercial details.

Source provenance and consumer journey

For each proposed source or subsource, a buyer should ask:

How is the inquiry generated: paid search, owned content, paid social, referral, a call-center transfer flow, or another approved channel?
Is the traffic a caller-initiated inbound call or a live transfer?
What creative, landing page, listing, or pre-transfer script did the caller encounter?
What does the source say the caller is requesting?
What geographic, language, and claim-stage targeting is used?
What fields or questions are collected before the call?
What source and subsource labels will survive into reporting?
Who reviews material creative, landing-page, call-type, or script changes?
What records are available if the buyer needs to investigate a mismatch?

That does not make the source universally appropriate. It lets the buyer decide whether the defined path is appropriate for its own target and intake capacity.

The source should also be reviewed for marketing claims that can create caller confusion. For example, a private firm or call source should not create a false impression of government approval, endorsement, authorization, or affiliation. Section 1140 of the Social Security Act addresses misuse of Social Security-related names, symbols, and emblems in communications that convey such a false impression. This is an area for counsel and a real review of the complete consumer experience, not a conclusion based on one disclaimer.

Delivery and commercial rules

The buyer should also ask:

What must be present for a call to be routed?
Which conditions prevent a call from routing?
How are schedules, caps, and temporary pauses enforced?
What does “exclusive” mean, if that term is used, and at what stage?
How are duplicates defined, including the lookback period and matching fields?
What is the agreed billable event?
Which buyer-side handling failures are not supplier-side quality disputes?
Which evidence can support a dispute, and by when must it be raised?
How are technical failures, failed transfers, and no-answers categorized?
How do reporting and invoice records reconcile to the buyer’s intake system?

A buyer should be cautious of a provider that offers only a volume promise and a price while leaving those questions unanswered. The best time to define a disagreement path is before the campaign has a disagreement.

For the broader due-diligence framework, see how to evaluate a pay-per-call source before scaling it.

Use source enablement as a deliberate buyer control

A buyer should not be forced to accept every source that happens to match a vertical label.

Dependable Calls is being built as a controlled, operator-led, beta-stage pay-per-call exchange. Its source-enablement model is designed around two distinct decisions:

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

Both decisions must be affirmative before a curated source routes.

That is curated source enablement, not open buyer discovery. It does not guarantee source quality, campaign availability, compliance, claim eligibility, or results. It gives the buyer a more deliberate way to start narrow, observe the evidence, and decide whether a source belongs on a particular target.

The practical implication for an SSDI buyer is that “approved for review” and “enabled to route to my practice” are separate decisions. A source may be appropriate to offer but not fit the buyer’s service area, call type, hours, claim-stage policy, or current capacity.

For the underlying model, read what source enablement means in pay-per-call.

Report the operating path, not just raw volume

Raw calls cannot tell a firm whether it has a media problem, a routing problem, or an intake problem.

The reporting model should make each stage visible enough to answer a specific operating question. At minimum, the buyer should be able to reconcile a defined group of calls by:

Date and hour in the relevant time zone.
Source and subsource.
Traffic channel and call type.
Buyer target or call path.
Service-area and language attributes that were validly used for routing.
Route result and reason when no route occurred.
Connection or answer result.
Duration, where relevant to the agreement.
Buyer intake disposition.
Duplicate result and the applicable policy version.
Billable status and reason.
Dispute status, reason, and resolution.
Downstream outcome when the buyer chooses and is able to report it.

The buyer’s own CRM or intake system should add the dispositions it controls: completed intake, callback scheduled, no contact after callback, outside the firm’s policy, retained, not retained, and any meaningful operational reason code. It should not automatically expose sensitive medical or claimant details to an exchange, publisher, or analytics layer.

The key is the join between source-level records and intake-level dispositions.

If one source has low completed-intake rates but the same target has strong results from another source, investigate the source journey. If all sources have high no-answer or callback-failure rates, investigate the buyer’s capacity before disputing traffic. If one hour of the day produces more missed calls, change coverage or schedule rather than treating the problem as an overall source verdict.

Source-level metrics are valuable because they make this kind of controlled comparison possible. When finance or billing is involved, the buyer should also preserve stable call identifiers and reconcile its intake records with the commercial records, as explained in how to reconcile buyer CRM records with pay-per-call billing events.

Make disputes narrow, timely, and explainable

A dispute process should correct a defined problem, not become a second intake department.

Before launch, agree on:

The buyer’s acceptance policy and version date.
The billable event.
The duplicate policy.
The relevant time zone.
The evidence available for each call type.
The reason codes for technical failure, no-answer, wrong category, duplicate, buyer-side handling failure, and source mismatch.
The deadline and method for raising a dispute.
The process for correcting a reporting or billing error.

A call that did not become a retained representation is not, by itself, evidence of a routing or billing defect. On the other hand, a buyer should not have to accept a call that demonstrably failed the agreed delivery rule. The discipline is to identify the stage where the problem occurred and use the agreed evidence to resolve it.

This is why the operating record matters: it lets everyone distinguish a source problem from a capacity problem, an eligibility policy from an SSA decision, and a commercial qualification rule from a case outcome.

SSDI call-buyer readiness checklist

Before expanding an SSDI campaign, the buyer should be able to answer yes to each of these questions.

Intake and coverage

We know who answers new inquiries during every scheduled delivery hour.
We have set a cap and concurrency limit based on real staffing, not a hoped-for call count.
We have a named owner and documented expectation for missed calls and callbacks.
We know what happens after hours and during overflow.
We can describe the languages and communication accommodations available to callers.

Acceptance policy

We have documented the programs, matter types, claim stages, and service areas we intend to review.
We treat work history, work activity, representation status, and adjacent-benefit questions as intake signals—not eligibility determinations.
We know how existing clients, already-represented callers, SSI inquiries, retirement inquiries, and status-only calls are handled.
We can distinguish a relevant inquiry, buyer-defined qualification, a billable event, a retained representation, and a successful outcome.

Source and routing controls

We know the call type and the caller journey for every source we test.
We have reviewed material consumer-facing claims, transfer language, and source provenance.
We know which target, service-area, schedule, cap, and source rules will apply.
We can pause a source or lower a cap quickly if the observed evidence requires it.

Reporting and commercial control

We can see source and subsource performance, not just a blended total.
Our intake team owns clear dispositions and can return them reliably.
We can reconcile call records to our own intake or CRM records without sharing unnecessary claimant data.
We know the billable event, duplicate rule, dispute window, and evidence path before the test begins.
We have defined the conditions required to expand, pause, or redesign the campaign.

If several answers are unclear, the next step is not more volume. It is to finish the operating design.

A controlled way to begin

The strongest SSDI call-buying program is not the one with the most calls on day one. It is the one that can explain what the caller requested, why the call reached a particular intake path, whether the team was ready, what happened next, and what should change before the next increment of volume.

Dependable Calls is being built around reviewed sources, buyer-selected source enablement, target-level routing controls, source-level visibility, and explainable operating records. Those capabilities remain subject to live validation and continued hardening in the beta. They are not a promise of campaign availability, volume, source fit, or outcome.

If your organization can define its service area, intake coverage, acceptance policy, 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.