SSDI Call Provider Due Diligence Checklist for Law Firms

A disability practice should not choose an SSDI call provider because a sales deck says “qualified,” “exclusive,” or “compliant.” Those words can describe very different operations. The useful question is simpler and harder: can this provider show how a specific call was generated, why it was sent to your intake path, what the provider counted, and what your firm observed after it arrived?

That is a buyer due-diligence question, not a claimant eligibility decision. The Social Security Administration decides whether a person meets SSDI requirements through its own process. SSA’s current overview explains that SSDI involves both covered work and its definition of disability, along with a step-by-step evaluation. A marketing form, a transfer agent, or a law-firm intake screen cannot replace that process. Review SSA’s eligibility overview when you design language, fields, and escalation paths.

This guide gives disability law firms, established non-attorney representatives, and advocacy organizations a practical way to compare providers before they buy. It focuses on what to define, ask for, and observe. It does not tell a caller whether they qualify for SSDI, SSI, retirement benefits, or representation.

Not legal advice: This is operational information, not legal advice. A firm should have appropriate legal and compliance counsel review its advertising, intake, referral, privacy, recording, telephony, fee, and state-specific obligations before it activates a campaign or accepts a provider’s terms.

Due diligence starts with your firm, not the provider’s pitch

A provider cannot design a sound SSDI call path around a buyer that has not defined its own operating policy. Before the first demo, decide what your organization can actually serve.

Write down:

• The states, jurisdictions, and claimant populations your practice can accept.
• Whether you take initial applications, reconsiderations, hearings, appeals, or only selected stages.
• Whether you accept SSDI-only inquiries, SSI-only inquiries, combined SSDI/SSI inquiries, retirement questions, or a narrower mix.
• Your answer hours, average answer capacity, after-hours policy, callback owner, and maximum callback delay.
• The facts your intake team may collect at the first interaction and the facts that must wait for a later review.
• What you will do when a caller has an existing representative, a pending claim, an outside-service question, or a matter your firm does not handle.
• Who owns daily caps, pauses, source approvals, dispute decisions, and intake-disposition feedback.

This is not bureaucracy. It tells you whether a provider can deliver to a path your team can answer, measure, and correct. A firm that accepts all 50 states only on paper, answers slowly on Fridays, or has no owner for missed-call follow-up cannot make a provider’s volume look good through better lead labels.

If you have not already done this work, begin with How to Buy SSDI Calls: A Pay-Per-Call Guide for Disability Law Firms. It turns capacity, service area, intake rules, caps, source review, and reporting into a buyer-owned setup process.

Make the provider define every outcome word

Most poor buying decisions begin when the parties use one label for six different outcomes. Insist on a written definition of each term in the provider’s proposal, reporting, and contract. Then compare that definition with the event your firm needs to measure.

A buyer price is what Dependable Calls charges the buyer. A publisher payout is what Dependable Calls pays a publisher. Neither term tells you whether a call was merely routed, was billable, was retained, or led to a successful case. Keep the commercial event separate from your intake and case outcomes.

The definition work is not semantic cleanup. It determines what evidence must exist. For example, “a qualified SSDI call” cannot be a valid claim if it means “the caller will be approved.” A more defensible buyer definition may be: a live conversation that reaches the firm during the agreed operating window, matches the documented service-area policy, presents an inquiry the practice is willing to review, and is not excluded by a known routing rule. Whether the caller has an SSDI claim that SSA will approve is a separate question.

For a fuller buyer-side taxonomy, see What Makes an SSDI Call Qualified?. It separates relevance, buyer-defined qualification, billability, retention, and outcome without turning intake into an SSA decision.

Ask what type of call is actually being delivered

“Call lead” is not a delivery specification. Your first provider-review question should be: what exactly happens between a person seeing marketing and your intake team receiving the call?

Ask the provider to describe, in plain language:

• Whether the person calls a displayed number, submits a form and receives a follow-up, speaks with an agent before transfer, or encounters some combination of those paths.
• Whether the delivery is a caller-initiated inbound call, a live transfer, a scheduled callback, or another format.
• The name and purpose of each party in the path: marketer, publisher, call center, transfer agent, exchange, buyer, and any subcontractor.
• What the person is told before a transfer or collection of information.
• What happens when your line is busy, a cap is reached, an intake window closes, or no one answers.
• Whether the person may be offered to another destination and, if so, under what disclosed and documented policy.
• What data is collected before the transfer, where it is held, and what your firm will receive.

Do not use “consumer-initiated” as a blanket substitute for this explanation. A caller may dial a number after viewing marketing; a live agent may transfer someone after a conversation; a person may be called back after a form. Those paths have different operational evidence, expectations, and review needs. A provider should be able to identify which path applies to a source and explain it without hiding behind a category name.

The distinction matters even when a campaign has no outbound component. The FTC notes that telemarketing rules can turn on the facts of the campaign, including calls received in response to advertising, and that federal, FCC, and state rules may all matter. Its compliance guide is a starting point, not a campaign-specific legal conclusion. Ask counsel to assess the actual path, scripts, records, and jurisdictions.

Review the claimant-facing experience before you review the dashboard

A clean-looking dashboard cannot repair a misleading landing page, misleading ad, or confusing transfer script. Ask to review the caller-facing materials associated with every proposed source before activation and after material changes.

The review package should include, where applicable:

• Search, social, display, or other ad creative.
• Landing pages, forms, disclosures, and thank-you pages.
• Phone scripts and transfer scripts.
• Recorded message or callback language, if used.
• The source’s name, role, and any subsource relationship that affects the journey.
• Change-control rules: who approves material changes and how a buyer is notified.
• The exact language used to describe benefits, representation, the provider, the buyer, and the next step.

Pay special attention to claims about government affiliation, approval, or authority. Social Security Act §1140 prohibits use of Social Security-related names, symbols, or language in a way that creates a false impression of SSA approval, endorsement, authorization, or connection. Read the statutory text. A buyer should not accept a provider’s assurance that “the page is compliant” as a substitute for reviewing what the person actually sees and hears.

A careful source review also protects the firm’s own intake. Avoid lead copy that tells people they are “approved,” “qualified for SSDI,” or already represented. The SSA describes SSDI as a program with work-history and disability requirements assessed in its process. It also treats SSI as a separate program with its own rules; an SSDI buyer may need a respectful route for SSI, retirement, survivor, or status-only questions rather than pretending all disability inquiries are the same. Article 25’s SSDI/disability guide explains why program labels and claim stage change the meaning of a call.

Trace the source chain, not just the brand on the proposal

A provider may have a strong brand but still deliver from multiple publishers, affiliates, call centers, or creative variants. That is not automatically a problem. It becomes a problem when the buyer cannot tell which source generated a call or cannot control what happens when a source changes.

Your due-diligence checklist should ask:

1. Who generated the inquiry? Request a stable source identifier for reporting. You do not need private identities or sensitive caller information to see source-level performance.

2. Is there a subsource? Ask whether the provider buys, syndicates, resells, or otherwise accepts traffic from another party. If so, determine whether source-level review and approval reach that level.

3. What was reviewed? Ask what the provider reviews before a source can send calls: the creative, landing path, call type, transfer flow, vertical fit, jurisdictional fit, and any required disclosures.

4. What changes are controlled? A review conducted in January is not evidence that a new landing page or new transfer script was reviewed in June. Ask how material creative, routing, or staffing changes are logged and surfaced.

5. Can the source be paused? The answer should cover both the commercial right to pause and the operational mechanism that stops delivery to your target or call path.

6. What evidence can be examined later? Source identifiers, creative versions, timestamps, routing events, and disposition categories are more useful than an untraceable quality score.

This is the difference between source awareness and source control. A buyer should not need to know every proprietary detail of a provider’s business to receive a coherent record of why a call arrived. Call provenance is useful here: no single artifact proves an entire journey, but a chain of related records makes a review possible.

Check delivery rules against your actual intake operation

A provider can accurately deliver what it sold and still create poor results for your firm if delivery rules do not match capacity. Put these items in the order form, test plan, or target specification—not only in a sales email.

Do not let a provider turn your intake policy into a “universal qualification” rule. Work history, current work activity, claim stage, existing representation, and adjacent SSI or retirement inquiries can all be useful signals for a firm’s routing and review policy. They are not automatic legal conclusions. For example, an intake team may want a separate path for a caller who is currently working, but only SSA can apply the relevant program rules to that person’s claim.

The same caution applies to representation. SSA’s representative resources show that appointment is part of the claimant’s process. Review SSA’s representation guidance rather than treating a provider’s “unrepresented” label as enough. A buyer should define how intake asks the question, what it does when the answer is unclear, and how the firm avoids disrupting an existing representative relationship.

Make “exclusive” and “duplicate” claims measurable

“Exclusive” is one of the least useful provider claims until it has a scope. A provider may use the word to mean one buyer at a time, one buyer for a set period, one buyer in a geography, one buyer for a source, or one buyer after an internal matching rule. Those are different commitments. None should be inferred.

If a provider offers an exclusivity term, ask for a written answer to all of the following:

• What event starts the exclusivity period: form completion, call start, connection, transfer, billable event, or accepted intake?
• What exactly is exclusive: a phone number, a caller record, a source event, a category, a geography, or a specified buyer path?
• How is a repeat caller or prior inquiry matched: phone number, email, name, source identifier, time window, or something else?
• Does the rule apply before a call reaches the firm, after a transfer, after a non-answer, or after an intake rejection?
• What happens if the firm’s cap is reached or the line is closed?
• Can any other provider, campaign, or buyer receive the same inquiry under another label?
• What is the evidence if a buyer believes a duplicate or an exception occurred?

A defensible duplicate policy is campaign-specific and evidence-led. It does not say “every repeat is invalid” or “every repeat is billable.” It says what counts as the same person or event for this campaign, how far back the comparison goes, what information is sufficient to support a review, and how exceptions are handled. This is especially important in SSDI, where a person’s claim stage and need for help can change over time.

Separate buyer pricing from performance evidence

Pricing is necessary, but it should not become your proxy for quality. Ask the provider to state the buyer price, the billable event, what happens when the agreed event does not occur, the invoicing cadence, and what report supports each charge. Do not compare that to a publisher payout and infer that one is a measure of qualification or source quality.

A good buying review keeps three ledgers conceptually separate:

• Delivery ledger: What was routed, attempted, connected, transferred, or answered?
• Commercial ledger: What event was billable to the buyer, credited, invoiced, or paid?
• Intake and case ledger: What did the firm classify, retain, decline, refer, or later resolve?

The provider may only control or observe part of the third ledger. Your firm owns the intake policy and many of the downstream outcomes. A provider that promises retained clients or successful cases is skipping these distinctions; a firm that expects its final case outcome to be the sole billing rule is also mixing unrelated stages.

The right question is not “Will every charge turn into a client?” It is “Can we identify the defined commercial event and compare it against our own intake dispositions by source, time, and call path?” The routed, qualified, and billable distinction is worth settling before the first invoice.

Require reporting that helps you make a decision

A weekly total-call report is not enough to evaluate a provider. It may tell you how much activity occurred but not whether a source, schedule, capacity setting, or handoff rule caused the result.

At minimum, ask whether reporting can show, in a privacy-conscious form:

• A stable source or source-group identifier.
• Date and time, call path, target or number, and service-area signal.
• The delivery event and the provider’s defined billable event.
• Routing outcome: sent, connected, blocked by cap, overflowed, missed, callback requested, or otherwise not delivered.
• A reason code for material routing or qualification outcomes.
• The creative, landing, or script version when that evidence is relevant and appropriate to share.
• Buyer feedback categories that your intake team can return without exposing unnecessary caller data.
• Disputed-event status, evidence reviewed, and resolution category.
• A versioned data dictionary so your team understands what every field means.

Do not ask an intake team to maintain a second, secret spreadsheet for provider evaluation. Map the handful of dispositions that make a decision possible: reached intake, outside service area, wrong program or issue, existing representation, unable to connect, callback pending, buyer-defined review needed, accepted for further review, and any other policy category your firm can apply consistently. Keep those labels operational. “SSA eligible,” “approved,” or “good case” should not appear as a casual first-call disposition.

Source-level measurement matters because blended averages hide operational differences. A campaign may look acceptable overall while one source produces high no-answer rates, one schedule produces poor handoffs, or one creative attracts adjacent program inquiries. How source-level metrics help buyers scale explains how to test, hold, diagnose, pause, and scale without mistaking raw volume for quality.

Treat disputes as a review process, not a loophole

A dispute policy cannot erase ambiguity after the fact. It can only make the review narrower and more explainable. Before launch, agree on:

• The eligible dispute reasons, written in observable terms.
• The evidence each side can provide: event logs, source identifier, delivery record, approved creative version, call-path record, and buyer disposition.
• The time window for flagging an event and for responding.
• The person or role authorized to submit and decide a dispute.
• The outcomes available: uphold, credit, correct a report, adjust a source rule, pause a source, or identify a system defect.
• What is outside the dispute policy, including a later agency outcome or an intake decision that falls outside the agreed definition.
• How recurring issues change the campaign rather than merely creating a longer dispute queue.

Do not turn an evidence request into an automatic demand for recordings or sensitive claimant details. Call recordings, if any, create their own consent, privacy, retention, and access questions. The first objective is to verify the operating event with the least information necessary. If the facts require deeper review, use your organization’s legal and privacy process. A practical article on preventing buyer disputes can help frame the definitions before volume makes them hard to change.

Request a provider evidence packet before you approve a test

A serious provider should be able to answer a structured request for information without treating every question as a hostile audit. The packet does not need to include private buyer names, caller data, margin information, recordings, or unpublished contracts. It should give a buyer enough evidence to decide whether a small, controlled test is appropriate.

Here is a practical request list:

1. A written definition of relevant inquiry, qualified call, connected call, billable event, duplicate, exclusive, and retained client—identifying which terms are provider claims and which are buyer-owned policies.

2. A plain-language journey map from marketing through delivery, including whether any agent, transfer center, or subsource is involved.

3. Current examples of the caller-facing creative, landing pages, forms, disclosures, and scripts proposed for your path, plus a material-change notification process.

4. A source-review description: what is reviewed, who can approve a source, how sources are identified, and how a buyer can enable, pause, or disable a source for a target.

5. A delivery specification covering states, hours, caps, overflow, no-answer behavior, transfer rules, callback treatment, and test-volume limits.

6. A sample report and field dictionary with source-level identifiers, event definitions, billing status, and reconciliation rules.

7. A written dispute and correction process with evidence types, timing, owners, and available remedies.

8. A statement of the provider’s data-handling, recording, and retention practices at a level suitable for counsel and privacy review.

9. A description of source-provenance records sufficient to explain a selected event after delivery.

10. A test plan that says what will be observed, who will meet to review it, and what conditions justify pause, adjustment, or expansion.

If a provider responds to all of this with “our calls are high quality,” you have learned something useful. Quality without definitions, source identifiers, event records, or a review path is not a buying standard.

Use a controlled test to evaluate the provider, not just the calls

A test should be small enough that your team can examine outcomes and large enough to reveal operational patterns. There is no universal call count that proves a source is good. The right test volume depends on your answer capacity, service area, intake staff, and the variation in the proposed sources.

Set the test up as a series of decision gates:

1. Preflight: Confirm the buyer policy, source status, delivery window, caps, escalation contact, reporting fields, and what counts as a pause. Review the live creative and call path that will actually be used.

2. First-event review: Examine the first several delivered events promptly. Validate basic routing, hours, service-area handling, and whether staff can consistently apply dispositions. Fix setup errors before they become a data set.

3. Source and schedule review: Compare outcomes by source, day, hour, call type, and target. Look for missed calls, overflow, adjacent-program patterns, repeated contacts, and handoff failures.

4. Reconciliation: Compare provider events and billing rules with your telephony and intake records. Differences may be legitimate; the point is to classify them, not declare a winner based on one system alone.

5. Decision meeting: Choose one of four actions for each source or call path: continue unchanged, adjust, hold for more evidence, or pause. Record why.

6. Scale only when the operation supports it: Increase a cap or enable an additional reviewed source only when reporting, answer capacity, and buyer feedback can keep pace.

Hypothetical example: two providers, the same volume, different evidence

Consider a hypothetical firm that serves a defined group of states and can answer new calls weekdays during a limited window.

Provider A reports 40 “qualified” calls. Its report lists a total by week, but it cannot distinguish caller-initiated inbounds from live transfers, does not identify a source or creative version, and defines “exclusive” only as “not sold simultaneously.” The firm sees a mix of missed connections and adjacent inquiries but has no way to isolate whether the problem came from a schedule, a transfer agent, or a particular source.

Provider B reports the same number of events. It shows two source identifiers, the call path, delivery timestamp, cap status, and the buyer’s returned dispositions. It can point to the reviewed creative version for a sample event and has a written rule for duplicate review. The firm still sees some calls it does not accept—no SSDI provider can make every inquiry a future client—but it can decide whether to adjust its policy, change the schedule, pause one source, or continue a controlled test.

Provider B has not proven eligibility, retention, compliance, or future results. It has supplied something more useful for a buyer: an explainable operating record.

How due diligence 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. It is not presented as an unrestricted open marketplace, a finished mass-market product, or a guarantee that a campaign, source, price, outcome, or volume will be available.

Its source-enablement model has two gates:

1. Dependable Calls decides which reviewed sources are appropriate to offer to a buyer.

2. 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 structure does not make every caller qualified, determine SSDI eligibility, eliminate disputes, or replace the buyer’s own intake policy. It makes the buyer’s source decision explicit and reviewable.

If you are comparing providers, use the same standard everywhere: ask what was reviewed, what the buyer controls, what can be reported, and what can be explained later. Source enablement is valuable only when it is paired with clear acceptance policy, delivery rules, and feedback from the firm that receives the calls.

SSDI call-provider due-diligence checklist

Before you authorize a test, you should be able to answer “yes” to each applicable item:

• We have written the service areas, practice scope, hours, capacity, caps, overflow treatment, callbacks, and escalation owners for this call path.
• We distinguish an SSDI-related inquiry, buyer-defined intake qualification, a billable event, retained representation, and a case outcome.
• Our qualification policy guides intake decisions but does not purport to decide SSDI, SSI, retirement, or representation eligibility.
• We understand whether proposed events are caller-initiated inbound calls, live transfers, callbacks, or another defined delivery type.
• We have reviewed current caller-facing creative, landing pages, forms, disclosures, and scripts for the sources proposed to us.
• We have asked counsel to review the legal and compliance implications that apply to our firm, jurisdictions, marketing, and call path.
• We can identify the source or source group behind a delivered event without requesting unnecessary private caller data.
• We know whether sources or subsources are reviewed, how material changes are controlled, and how a source can be paused.
• We have written delivery rules for service area, schedules, caps, no-answer behavior, overflow, callbacks, and state or program exclusions.
• If “exclusive” or “duplicate” is offered, the term has an exact scope, matching rule, period, evidence standard, and corrective process.
• We know the buyer price, the billable event, the report that supports it, and why it is different from retention or case outcome.
• We will receive a report with source-level identifiers, delivery and billing events, routing outcomes, field definitions, and a way to reconcile those records with our intake system.
• We have limited dispute reasons to observable events, identified the evidence needed, and set response times and escalation owners.
• We have a controlled test plan, including a first-event review, a pause condition, and a source-by-source decision meeting.
• We will scale only after intake capacity, source evidence, and downstream dispositions support the change.

A better buying decision is an explainable one

The best provider is not the one that promises the most. It is the one whose source, delivery, commercial event, and reporting can be understood alongside your own intake outcomes. In SSDI, that discipline is especially important because a useful inquiry, a fit for representation, an agency decision, and a successful case occur at different times and involve different evidence.

If your organization can define its policy, review the caller journey, test a small controlled path, and compare source-level results, you can make a considered decision without pretending the provider or your first-call screen can predict SSA outcomes.

If you are building a buyer program and want to discuss a controlled, reviewed call path, apply to partner with Dependable Calls. An application starts a conversation; it does not promise campaign availability, volume, pricing, source access, or results.