The 2015 budget law let federal debt robocalls skip consent and left the limits to a later FCC rule

Section 301 of the Bipartisan Budget Act, signed November 2, 2015, exempted calls to collect federal debts from the TCPA's consent rule. The FCC's limits came later and hinged on a paperwork approval; in 2020 the Supreme Court struck the exemption.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

Section 301 of the Bipartisan Budget Act, signed November 2, 2015, exempted calls to collect federal debts from the TCPA's consent rule. The FCC's limits came later and hinged on a paperwork approval; in 2020 the Supreme Court struck the exemption.

  1. The week The law was a budget measure.
  2. The permission arrived on enactment The amendment took effect with the law. [1] Nothing in Section 301 delayed the exception until the FCC acted. [1] The regulatory deadline in section 301(b) applied to the Commission's implementing rules, not to the exception itself. [1] In our reading, from November 2, 2015, a caller that fit the statutory words could rely on them without waiting for any rule.
  3. The limits came by rulemaking, on a later schedule The order defined the calls that fit the exception.
  4. The operators carried the work, and the records Each condition in the FCC's design corresponds to a record someone had to keep.
  5. The constitutional test turned on the call's subject The opinion addressed liability for calls already made.
  6. The consent model outlasted the exception Two of those exemptions are directly relevant to the series' sectors.
  7. With hindsight The FCC adopted the implementing order on August 2, 2016.

The week

On November 2, 2015, the Bipartisan Budget Act of 2015 was approved and became Public Law 114-74. [1] Its legislative history records that the House concurred in a Senate amendment with an amendment on October 28, and that the Senate considered and concurred in the House amendment on October 29 and 30. [1]

The law was a budget measure. Its twelve titles included budget enforcement, agriculture, pensions, health care, Social Security, a temporary extension of the public debt limit and a spectrum pipeline. [1] One short section, in the title headed "Commerce," reached a different subject: the robocall rules of the Communications Act. [1] Section 301, headed "Debt collection improvements," amended section 227(b) of the Communications Act of 1934, the provision added by the Telephone Consumer Protection Act. [1]

Section 301 inserted a new exception into section 227(b)(1)(A)(iii), the sentence that governs autodialed and prerecorded calls to cellular telephone numbers. [1] After the words about the called party being charged for the call, it added "unless such call is made solely to collect a debt owed to or guaranteed by the United States." [1]

The section made a parallel change to section 227(b)(1)(B), the rule for prerecorded calls to residential lines. [1] It inserted language exempting a call that "is made solely pursuant to the collection of a debt owed to or guaranteed by the United States." [1]

Section 301 also gave the Federal Communications Commission a new power. It added a subparagraph (H) to section 227(b)(2). [1] Under it, the Commission "may restrict or limit the number and duration of calls" made to a cell phone number to collect such a debt. [1]

The section set a deadline for rules. Section 301(b) was headed "Deadline for Regulations." [1] Under it, the Commission was to prescribe implementing regulations "Not later than 9 months after the date of enactment of this Act." [1] It was to act "in consultation with the Department of the Treasury." [1]

The text did not define which debts were "owed to or guaranteed by the United States." [1] It did not say who could place the calls, whether a call could go to someone other than the borrower, or how often a borrower could be called. [1] It left those questions to the Commission's rulemaking, through the new limiting power and the deadline. [1]

Section 301 sat beside other provisions in the same law that dealt with how federal programs reach people. Section 814, for example, headed "References to Social Security and Medicare in electronic communications," amended section 1140 of the Social Security Act. [1] It extended that section's prohibition to "any Internet or other electronic communication." [1] It also made each dissemination, viewing or accessing of such a communication a separate violation. [1]

For the agencies that lend or guarantee money, and for the servicers and collection contractors that call borrowers for them, the week's change was simple to state. A category of autodialed and prerecorded calls to cell phones no longer depended on the borrower's prior express consent. [1] Whether those calls would be limited, and how, depended on rules the FCC had yet to write. [1]

The statute itself named no lending program and no agency other than the Treasury, which the Commission was to consult. [1] Which borrowers would hear from the new calls depended on which debts fit the statutory words. [1]

The robocall section of the 2015 budget law is easy to read as a footnote to a fiscal deal. [1] Read with what followed, it shows how a citizen-facing contact rule can change faster than the protections meant to go with it. [3] [5]

Our argument is that Section 301 changed the order of things. It removed the consent requirement at once, on enactment, for one class of callers. [1] It left limits on those calls to a later rulemaking. [1] The rulemaking then tied its own effective date to a paperwork approval, so the limits waited on that approval. [3] The constitutional weakness of a carve-out for one kind of caller surfaced later still, in 2020. [5]

For a government program office, a loan servicer, or a bank or health system that runs automated outreach, the lesson is about sequencing. In our view, the legal permission to call and the controls that make calling acceptable to the public do not always arrive together. Planning has to account for the gap.

We take it in five parts, each a separate question that the law, the rule and the courts answered in turn:

  1. The permission: what Section 301 allowed on the day it was signed, and what it left open.
  2. The limits: what the FCC wrote to bound the permission, and how it scheduled them.
  3. The operators: who carried the work of placing compliant calls, and which records they needed.
  4. The constitutional test: why a carve-out defined by the call's subject failed in 2020.
  5. What remained: the consent model that outlasted the exemption, and the narrower exemptions the FCC built for banks and health care.

The permission arrived on enactment

Section 301 did its main work by inserting words into an existing prohibition. [1] The prohibition in section 227(b)(1)(A)(iii) applied to calls using an autodialer or an artificial or prerecorded voice to a cell phone. [5] As the Supreme Court later quoted it, the prohibition excepted calls made for emergency purposes or with the prior express consent of the called party. [5] Section 301 added a third, for calls made "solely to collect a debt owed to or guaranteed by the United States." [1]

The amendment took effect with the law. [1] Nothing in Section 301 delayed the exception until the FCC acted. [1] The regulatory deadline in section 301(b) applied to the Commission's implementing rules, not to the exception itself. [1] In our reading, from November 2, 2015, a caller that fit the statutory words could rely on them without waiting for any rule.

What the words left open

The words fit easily into a statute and were hard to apply in a call center. Three phrases carried most of the uncertainty.

"Owed to or guaranteed by the United States." Federal credit programs come in different forms. Some loans are made directly by an agency. Others are made by private lenders and guaranteed by an agency. Some debts move from one holder to another over their life. The statute did not say how a caller should treat a debt that had been sold or assigned. [1] The FCC later decided that the phrase covered only debts the United States owned or guaranteed at the time of the call. [3]

"Solely to collect." A servicer's call can mix collection with other purposes: a reminder, a change in terms, a product offer. The statute did not say whether a call that mentioned anything else still qualified. [1] The FCC later read the word "solely" to exclude calls with marketing, advertising or sales content. [3]

Who may be called. The statute did not say whether the exception reached only the borrower, or also co-signers, references and family members listed on a loan file. [1] The FCC later limited covered calls to the debtor or another person legally responsible for paying the debt. [3]

Three choices a servicer faced in late 2015

A servicer holding federal loans on November 2, 2015 had to decide what to do with the new words before any rule existed. [1] In our reading, it had three broad options, each with a different risk.

It could keep seeking consent before autodialing cell phones, as if nothing had changed. That choice carried no legal risk under the TCPA and gave up the permission Congress had granted. [1]

It could rely on the statutory words alone for calls it judged to be solely to collect a covered debt. That choice carried interpretive risk. The caller had to decide for itself which debts were covered, which calls were "solely" for collection, and whom it could call. [1] The FCC later answered each of those questions more narrowly than a broad reading of the statute might have. [3]

It could rely on the words and also apply limits of its own, anticipating a rule. That choice reduced the chance of later conflict with the FCC's design, at the cost of guessing what the design would be. The Commission's proposal did not appear until May 2016. [2]

The choice belonged to the servicer and, through its contract, to the agency that hired it. In our reading, it was a governance decision as much as a legal one. It decided how a federal program's borrowers would be contacted for the months before the rules were written.

Why the gap mattered to borrowers

A borrower's experience of the change did not depend on any of these questions being settled. A call that relied on the exception would ring the same way whether or not a court later agreed with the caller's reading. The FCC's 2016 order noted that consumers consistently complained to the Commission, the Federal Trade Commission and the Consumer Financial Protection Bureau about abusive and persistent debt-collection robocalls. [3]

For an agency running a lending or guarantee program, the exception also changed what its contractors could do on its behalf. Contracts that had required consent before autodialing a cell phone could now be read as permitting such calls for qualifying debts. [1] In our reading, an agency that wanted the older, stricter practice to continue had to say so in its own contracts or policies, since the statute no longer required it.

The residential line change

Section 301's change to section 227(b)(1)(B) had a smaller effect than its text suggests. [1] The FCC's 2016 order explained that the Commission had already used its exemption authority to apply the consent requirement for prerecorded calls to residential lines only to calls that included advertising or constituted telemarketing. [3] It had also found that debt collection calls did not constitute telemarketing. [3] The cell phone change was the one that altered existing practice.

The Commission also read Congress's grant of limiting power as reaching only cell phone numbers. [3] It noted that Congress, by omission, had not authorized limits on calls to residential lines. [3] In our reading, this left two kinds of numbers under different regimes for the same debt.

What state and local agencies could not use

The exception's reach was federal by its terms. It covered debts owed to or guaranteed by the United States. [1] A state agency collecting a state tax, a county collecting a utility bill, or a public hospital collecting its own patient balances had no claim to it. [1]

In our reading, that left state and local governments on the general rule throughout. Their autodialed or prerecorded calls to cell phones still needed consent or an emergency purpose. [1] [5] A state program that shared a contractor with a federal program had to make sure the contractor did not carry federal-debt dialing settings into state work.

The boundary could also run through joint programs. If a state agency administering a federally funded benefit recovered an amount owed partly to the state and partly to the United States, the statute gave no rule for the mixed case. [1] An agency in that position needed counsel's view on which accounts fit the words before relying on them.

The limits came by rulemaking, on a later schedule

The FCC opened its rulemaking with a notice of proposed rulemaking published in the Federal Register on May 20, 2016. [2] Comments were due on or before June 6, 2016, and reply comments on or before June 21, 2016. [2] The notice proposed to limit federal debt collection calls to three per month, per delinquency, after delinquency. [2]

The Commission adopted its order on August 2, 2016, and released it on August 11, 2016, as document FCC 16-99. [3] A summary appeared in the Federal Register on November 16, 2016. [3] The statute's "Not later than 9 months" deadline ran from November 2, 2015. [1] The order's own date line said the order "was issued August 11, 2016." [3]

What the order allowed

The order defined the calls that fit the exception. Debt collection calls could be made while a debt was delinquent. [3] Debt servicing calls could be made after a specific, time-sensitive event that affected the amount or timing of payments, and "in the 30 days before such an event." [3] The order listed the end of a deferment period and a deadline to recertify eligibility for an alternative repayment plan among those events. [3]

The order explained why servicing calls belonged in the exception. It said such calls could help a debtor avoid delinquency or default, preserving payment history and eligibility for future loans. [3] It gave the example of income-based repayment plans for student loans, which can require a higher payment automatically if the borrower does not recertify. [3]

The order limited who could call. A covered call had to be made by the owner of the debt or its contractor. [3] The Commission declined to extend the exception to subcontractors as such. [3] It limited covered calls to three categories of wireless numbers. [3] The first was the number the debtor gave when the debt was incurred, and the second a number the debtor later gave the owner or its contractor. [3] The third was a number obtained from an independent source that was actually the debtor's. [3]

What the order restricted

The Commission used the limiting power Congress gave it. [3] It capped federal debt collection calls to wireless numbers at three within a thirty-day period. [3] It applied that cap per servicer or collector, and allowed a separate cap for each type of federal debt the servicer handled for the debtor. [3] It limited artificial-voice and prerecorded-voice calls to 60 seconds, exclusive of required disclosures. [3] It set no cap on the length of autodialed calls with a live caller. [3]

The order allowed calls only between 8:00 a.m. and 9:00 p.m., local time at the called party's location. [3] It said that this matched the rule for telemarketing calls. [3] It said callers had to follow the most restrictive rule where other laws also applied, and that Section 301 did not affect laws for which the CFPB or the FTC had responsibility. [3]

The order gave debtors a right to stop the calls. A debtor could ask the owner of the debt or its contractor, by any reasonable method, to make no further calls for the life of the debt. [3] Calls had to disclose that right. [3] Prerecorded and artificial-voice calls had to include an automated opt-out mechanism. [3] When a servicer changed, the stop-call request had to move with the account. [4]

What the cap meant for a borrower with several loans

The order's cap applied to each servicer or collector, not to each loan. [3] The Commission explained that applying it per loan could multiply the calls a borrower with several student loans received. [3] It chose the per-servicer rule to prevent an excessive number of calls to individual debtors. [3]

The order kept one exception to that aggregation. A servicer that held contracts for more than one type of federal debt, such as student loans and Department of Agriculture loans, could use a separate three-call limit for each type. [3] In our reading, this put the burden of counting on the servicer's systems. A dialer had to know how many qualifying calls each debtor had received, by debt type, across every campaign the servicer ran.

Counting calls is harder than it sounds. The order defined a call as any initiated call, whether or not it was completed or reached voicemail. [3] It counted autodialed text messages as calls. [3] A servicer that tracked only completed conversations, or tracked voice and text in separate systems, would undercount.

How the order scheduled itself

The Commission's effective-date decision is the part of the order that matters most for planners. Two pieces of the rules, recording a debtor's stop-call request and conveying it from one servicer to another, required approval by the Office of Management and Budget (OMB) under the Paperwork Reduction Act. [3] Those pieces would not become effective until "60 days after the Commission publishes a Notice in the Federal Register indicating approval of the information collection by OMB." [3]

The Commission then chose to hold back the rest of the rules until the same date. [3] It said the rules that permitted calls and the rules that let debtors stop them were so integral to one scheme that both had to take effect together. [3] It said that doing otherwise would let callers make calls while leaving debtors without consumer protections until OMB approval was complete. [3]

On January 17, 2017, the Commission published a notice that it was submitting the information collection to OMB for review. [4] The notice summarized the rules: three calls in a 30-day period, the 8:00 a.m. to 9:00 p.m. window, the stop-call right and its transfer between servicers, and the 60-second limit on prerecorded calls. [4]

The consequence of coupling

The coupling protected borrowers from one risk and left them exposed to another. It prevented a period in which the FCC's interpretation expanded who could call without any stop-call right. [3] It did not change the statute, which had allowed the calls since November 2, 2015. [1] In our reading, for as long as the rules were not in effect, a caller's conduct rested on the statutory words alone, and the Commission's limits were a published intention rather than an enforceable rule.

The operators carried the work, and the records

The exception was written for the United States as creditor or guarantor. [1] The calls themselves could be placed by contractors. [3] The FCC's order addressed "the owner of the debt or its contractor" throughout. [3] The OMB notice described the callers as federal government callers and contractors making calls on behalf of the federal government. [4]

Four records a compliant call depended on

Each condition in the FCC's design corresponds to a record someone had to keep. For a servicer, these were operational systems, not legal abstractions.

  1. Debt status at the time of the call. The order covered only debts the United States currently owned or guaranteed. [3] It said a debt sold in its entirety was no longer covered. [3] A servicer needed a field, updated when loans were transferred, that told the dialer whether each account still qualified.
  2. Number provenance. The order limited calls to three categories of numbers. [3] A dialer list built from skip tracing or purchased data needed a way to show that a number was actually the debtor's. [3]
  3. Event dates. Servicing calls were allowed only after a qualifying event or in the window before one that the order set. [3] The servicer needed the deferment end date, the recertification deadline and the delinquency status in the same place as the dialer.
  4. Stop-call requests. A request could be made by any reasonable method, including orally and by reply text. [3] It had to be recorded and honored for the life of the debt, and passed to any new servicer. [3] [4]

Why reassigned numbers were the hard case

The order took a firm line on wrong numbers. It said robocalls to wrong numbers were not covered by the exception. [3] It applied the Commission's 2015 one-call window to reassigned numbers: a caller that did not know a number had been reassigned could rely on one call. [3]

We think federal loans that run for many years make this a practical problem. The order itself noted concerns that the number on the application might no longer belong to the debtor when the debt entered repayment. [3] For a servicer, the cost of a bad number was the exposure of an ordinary TCPA call, since the exception did not reach it. [3]

The agency's position

An agency that owns or guarantees debt sits behind its contractors in this design. The FCC said its number and duration limits applied to calls by the federal government, to the extent it owned or guaranteed the debt, and to its contractors. [3] The Federal Register summary referred to a Jurisdiction section for the explanation but did not reproduce that section. [3]

In our reading, the agency's practical lever was its contract. An agency could require its servicers to apply the FCC's limits from the date of the order, regardless of the delayed effective date. It could require stop-call transfer at servicer changes, where the borrower's request would otherwise be lost. It could audit dialer lists for number provenance. These are contract terms an agency's acquisition office can write; the statute did not supply them.

What an acquisition office could write

The agency's contract file is where the FCC's design could have taken hold early. Several terms follow directly from the order's conditions and require no new authority. [3]

  • A requirement to classify each account, at the time of each call, as owed to or guaranteed by the United States or not, with the transfer and payoff events that change the classification.
  • A requirement to record the source of every number dialed, in one of the three categories the order described.
  • A stop-call process that accepts requests by any reasonable method, honors them across all of the contractor's campaigns, and hands them to the next servicer at transfer.
  • A call log that counts initiated calls and texts per debtor, per debt type, against a monthly limit.
  • A content review that keeps marketing and sales material out of calls that rely on the exception.

These terms did not depend on the FCC's rules taking effect. [3] Each could be measured in an audit. In our reading, an agency that wrote them in 2016 would have held its contractors to the Commission's design whether or not the rules ever took effect.

The metrics that show whether it works

A program office that contracts out borrower calls needs evidence, not assurances. The order's conditions suggest the measures. [3] They include the share of dialed numbers with a recorded source, the time between a stop-call request and its suppression across campaigns, and the number of stop-call requests lost at servicer transfers.

Complaint data belongs alongside these. The FCC's order rested its limits in part on consumer complaints to three federal agencies. [3] An agency that tracks complaints about its own contractors' calls holds an early signal that its controls are failing.

A bank or health system in the same position

Section 301 applied only to debts owed to or guaranteed by the United States. [1] In our reading, a bank servicing loans that carry a federal guarantee could fall within its words for those loans. [1] [3] A health system collecting its own patient balances would not, since those debts are owed to the system. [1]

The distinction matters for anyone who runs one dialing platform across several portfolios. A single platform may hold federally guaranteed loans and conventional loans side by side. In our reading, the platform needed account-level flags to tell the dialer which consent rule applied to each call, and those flags had to change when loans were sold or paid off.

The constitutional test turned on the call's subject

The exception was challenged on free speech grounds by organizations that wanted to make political robocalls to cell phones. [5] The Supreme Court decided the case, Barr v. American Association of Political Consultants, on July 6, 2020. [5]

What the Court held

The Court affirmed the Fourth Circuit's judgment, which had invalidated the government-debt exception and severed it from the rest of the robocall restriction. [5] The syllabus records several opinions reaching that result by different routes. [5] One concluded that the exception failed strict scrutiny; another, that it failed intermediate scrutiny. [5] Three Justices would have upheld the exception but, given the contrary majority view, agreed it was severable. [5]

The opinion announcing the judgment found the restriction with the exception content-based. [5] It said the law favored speech made for the purpose of collecting government debt over political and other speech. [5] The Government conceded that the restriction with the exception could not satisfy strict scrutiny. [5]

The opinion rejected the Government's argument that the law turned on economic activity rather than content. [5] It said the law focused on whether the caller was speaking about a particular topic. [5] It said that the Government had not sufficiently justified treating government-debt collection calls differently from other important categories of robocalls, such as political speech. [5]

Why severance mattered more than invalidity

The plaintiffs wanted to be able to make political robocalls to cell phones. [5] The Court instead removed the exception and left the 1991 restriction standing. [5] The opinion noted that the Communications Act had contained an express severability clause since 1934. [5]

In our reading, political callers gained no new permission from the judgment, and government-debt callers lost theirs. [5] Calls to collect federal debts returned to the general rule: an autodialed or prerecorded call to a cell phone needed prior express consent or an emergency purpose. [5]

The question of past calls

The opinion addressed liability for calls already made. In a footnote, it recorded the Government's acknowledgment about past calls. [5] No one should be penalized or held liable for robocalls to collect government debt made while the exception stood, up to final judgment on remand or another date the lower courts found appropriate. [5] The same footnote said the decision did not negate the liability of parties who made robocalls covered by the restriction. [5]

In our reading, the footnote protected callers who had relied on the exception during its life. It did not protect calls that never fit the exception, such as calls to non-debtors or calls about debts the United States no longer owned. Those calls had always been governed by the general rule.

What the decision means for other carve-outs

The opinion's reasoning reached a carve-out defined by what a call was about. [5] It said the law favored one kind of speech, debt collection for the Government, over others. [5] It also said its decision did not affect traditional or ordinary economic regulation of commercial activity. [5]

For a regulator or a legislature designing a new exemption from a calling rule, the case marks a boundary. In our reading, an exemption keyed to the subject of a message invites the same challenge. Exemptions written as conditions on the caller's relationship with the recipient, and on the message's frequency and form, are a different design. We do not predict how a court would treat any particular exemption, and organizations relying on one should check with counsel.

The current text of the FCC's delivery rule shows how the Commission has handled exempted calls since. [6] It does not contain the federal debt provisions the 2016 order described. [3] [6] It does contain a set of exemptions in paragraph (a)(9), each tied to conditions. [6]

The exemptions banks and health systems use

Two of those exemptions are directly relevant to the series' sectors. One covers calls by financial institutions, as defined by reference to the Bank Holding Company Act, and the other covers calls by or on behalf of healthcare providers. [6]

The financial institution exemption is limited to specific purposes. [6] These include transactions and events that suggest a risk of fraud or identity theft, and possible breaches of the security of customers' personal information. [6] The calls must go only to the wireless number the customer provided. [6] They must not include telemarketing, cross-marketing, solicitation, debt collection or advertising content. [6] An institution may initiate no more than three messages per event over a three-day period for an affected account. [6] Opt-out requests must be honored immediately. [6]

The healthcare exemption is similarly bounded. [6] It covers purposes such as appointment reminders, pre-operative instructions, lab results, post-discharge follow-up intended to prevent readmission, and prescription notifications. [6] The calls must go only to the number the patient provided, and must not include accounting, billing, debt-collection or other financial content. [6] They must comply with HIPAA privacy rules. [6] A provider may initiate one message per day to each patient, up to three combined per week. [6]

How the two designs differ

Set side by side, the 2015 statutory exception and the FCC's own exemptions differ in a way that explains their fates. The statutory exception was defined by subject, collecting a particular class of debt, and its limits came later. [1] [3] The FCC's exemptions are each defined with their limits built in: purpose, number, frequency, content and opt-out. [6]

Both financial and healthcare exemptions expressly exclude debt collection content. [6] In our reading, collection calls by a bank or a health system therefore depend on consent, not on these exemptions. The exemptions serve alerts and care; collection remains on the general rule.

The strongest case against our argument

A fair objection is that the sequence was ordinary. Congress legislates in general terms and leaves detail to agencies. Rulemakings take time. A paperwork approval is a normal step. On this view, the 2015 exception was no different from any other statute with a regulatory deadline.

The objection is right about the mechanics and misses the direction of the change. A rulemaking deadline can attach to a new duty that waits for rules to define it. Section 301 lifted a duty and waited for rules to restore some of it. [1] The FCC's order recognized the risk this created, which is why it coupled the permissive and protective rules. [3] The coupling, in turn, kept the permissive reading from becoming a rule while leaving the statute's permission in place. [1] [3]

A second objection is that the exception mattered little, since prudent servicers kept seeking consent. We have no source that measures how callers behaved during the exception's life, and we do not claim one. Our point is about exposure: the law allowed a practice whose limits were not yet enforceable, and a borrower had no rule to point to.

Signs of the same sequence elsewhere

The 2015 pattern has recognizable markers, and a compliance team can watch for them in any new law. The first is a carve-out that takes effect on enactment while its limits wait for rules. [1] The second is a rule whose protective parts depend on a separate approval, such as a paperwork clearance, before anything takes effect. [3] The third is a carve-out defined by the subject of the activity rather than by conditions on how it is done. [5]

When all three appear together, an organization has a choice to make about its own conduct in the interval. In our reading, the safer course is to adopt the expected protections voluntarily and to keep the records the general rule would require. That course costs some convenience during the interval. It avoids rebuilding consent records if the carve-out falls, as this one did. [5]

What we would tell a program office today

For a federal or state program that contacts the public about money owed, the 2015 episode suggests three design rules. Put the protections in the program's own contracts, rather than waiting for a regulator. Treat an exemption from a consent rule as fragile, since one defined by the call's subject proved vulnerable. Keep the records that would justify a call under the general rule, consent and number provenance, even when an exemption seems to make them unnecessary.

For a bank or health system, the same history argues for mapping each outbound message type to the exemption it relies on. [6] Where no exemption fits, as with collection content, the call needs consent. [6] The records of that consent, and of the number's provenance, are the control that survived every change in the period.

With hindsight

The FCC adopted the implementing order on August 2, 2016. It released the order on August 11, 2016, and published a summary in the Federal Register on November 16, 2016. [3] The order set out a full scheme of limits, but held all of it back until OMB approved the stop-call recordkeeping. [3]

On January 17, 2017, the Commission published notice that it was submitting that information collection to OMB. [4] The notice estimated 36,548 respondents and a total annual burden of 666,598 hours for the collection as a whole, which covered other TCPA requirements as well. [4]

On July 6, 2020, the Supreme Court decided Barr v. American Association of Political Consultants. [5] It affirmed a judgment that invalidated the government-debt exception and severed it from the 1991 robocall restriction. [5] The opinion announcing the judgment said the decision meant the end of the government-debt exception. [5] It recorded the Government's acknowledgment that callers who made government-debt robocalls during the exception's life should not be penalized for them. [5]

The current text of 47 CFR 64.1200, as checked on 2026-11-16, contains none of the federal debt calling provisions the 2016 order described. [3] [6] Its paragraph (a)(9) lists exempted calls by package delivery companies, inmate collect call providers, financial institutions and healthcare providers. [6] The financial institution and healthcare exemptions each exclude debt collection content. [6]

What held up from the week of November 2, 2015 was the underlying rule. The 1991 restriction on autodialed and prerecorded calls to cell phones without consent survived the challenge, by the Court's choice of severance over invalidation. [5] The opinion said the decision concerned only robocalls to cell phones, and was not intended to expand existing First Amendment doctrine. [5]

What did not hold up was the exception itself. A permission that applied to one subject of call, collecting a particular kind of debt, could not be squared with a restriction that bound political and other callers. [5] The Government conceded that the restriction with the exception could not satisfy strict scrutiny. [5]

The FCC's own design choices held up in a different form. The 2016 order combined a purpose limit, a cap on calls, a length limit, a time window and an opt-out that must be honored. [3] The same kinds of conditions appear today in the Commission's exemptions for banks and health care providers. [6] Those exemptions are written into the Commission's own rule with their conditions built in. [6]

For agencies and their contractors, the practical outcome is that federal debt calls to cell phones answer to the same consent rule as any other autodialed or prerecorded call. [5] [6] For banks and health systems, the exemptions they use for fraud alerts and care reminders carry exclusions that keep collection outside them. [6]

We do not know from the sources we opened whether OMB approved the 2017 submission or whether the 2016 rules ever took effect, and we make no claim either way. [4] [6] We do know what the current rule contains and what the Court decided. [5] [6]

The episode's lasting point for leaders is about where controls should live. The 2015 statute moved one control, consent, out of the law before the replacement controls were enforceable. [1] [3] In our reading, the organizations that kept their own consent and number records from 2015 to 2020 held the evidence they would need under the rule that came back. [5]

Spotted an error? Tell us and we will check it and correct the article where needed.

  • TCPA
  • robocalls
  • federal debt collection
  • student loans
  • consent
  • FCC