govt.fyi
US Congress · H.R. 7022 · Passed the House

Mystic Alerts Act

Introduced
Moved
Reached a final decision
Introduced 2026-01-12
Derived from the official record below.

Officially: “Mystic Alerts Act Read the full text

Science, Technology, Communications

What it does

Mystic Alerts Act This bill provides for wireless emergency alerts to be transmitted to mobile devices via satellite. (Currently, wireless emergency alerts are sent via terrestrial mobile networks to individual devices in geographically targeted areas. Commercial mobile service providers are not required to participate; only devices connected to a participating service provider’s network receive alerts.) Under the bill, commercial mobile service providers that participate in the wireless emergency alerts system must give notice to the Federal Communications Commission (FCC) indicating whether
Summary by the Congressional Research Service, from the official record. Plain-language version below. Not legal advice.

Read it in plain language

AI plain language2 sections
Written by AI from the complete official bill text and independently fact-checked against it. Not legal advice.
1Short title

This section gives the Act its short title, the Mystic Alerts Act.

Show official text
Official text, verbatim from the record

1. Short title This Act may be cited as the Mystic Alerts Act .

2Transmission of emergency alerts by satellite

This section would apply to any provider of commercial mobile service that voluntarily elects to transmit emergency alerts under section 602(b) of the Warning, Alert, and Response Network Act. Each such provider would have to file an election with the Federal Communications Commission stating whether it also intends to transmit those alerts by satellite to its subscribers or users. A provider that elects to transmit alerts by satellite would have to notify the Commission of that election and agree to transmit the alerts in a manner consistent with the technical standards, protocols, procedures, and other technical requirements the Commission puts in place. A provider that elects not to transmit alerts by satellite would have to notify its new and existing subscribers and users of that election, using the same manner of notice already required under subparagraphs (B) and (C) of section 602(b)(1) of the Warning, Alert, and Response Network Act. A provider that does elect to transmit alerts by satellite would have to prevent the device of any subscriber or user who has opted out of receiving emergency alerts, or classes of such alerts, under section 602(b)(2)(E) of the Warning, Alert, and Response Network Act from receiving those alerts by satellite. Separately, not later than 6 months after this Act becomes law, the Commission would have to publish a Notice of Proposed Rulemaking to establish the technical standards, protocols, procedures, interoperability requirements, and other technical requirements needed to enable satellite alerting capability for commercial mobile service providers that voluntarily elect to transmit emergency alerts, including standards for training those providers on enabling that capability. Not later than 12 months after this Act becomes law, the Commission, in consultation with the Secretary of Homeland Security and the Administrator of the Federal Emergency Management Agency, would have to issue a final rule establishing the standards, protocols, procedures, and requirements described in the Notice of Proposed Rulemaking.

Show official text
Official text, verbatim from the record

2. Transmission of emergency alerts by satellite (a) Service provider election (1) Required filing Each provider of commercial mobile service that voluntarily elects to transmit emergency alerts under section 602(b) of the Warning, Alert, and Response Network Act ( Public Law 109–347 ; 42 U.S.C. 1201 ) shall file an election with the Federal Communications Commission with respect to whether the provider intends to also transmit such alerts by satellite to the subscribers or users of the commercial mobile service of the provider. (2) Notification; agreement If a provider described under paragraph (1) elects to transmit emergency alerts to subscribers or users by satellite, the provider shall— (A) notify the Commission of that election; and (B) agree to transmit such alerts in a manner consistent with the technical standards, protocols, procedures, and other technical requirements implemented by the Commission. (3) Election not to transmit If a provider elects not to transmit emergency alerts by satellite under paragraph (1), the provider shall provide notice to new and existing subscribers and users of the commercial mobile service of the provider of that election in the same manner that is required under subparagraphs (B) and (C) of section 602(b)(1) of the Warning, Alert, and Response Network Act. (4) Consumer choice to opt out If a provider of commercial mobile service described under paragraph (1) elects to transmit emergency alerts to subscribers and users by satellite, the provider shall prevent the device of any subscriber or user that opts out of receiving emergency alerts pursuant to section 602(b)(2)(E) of the Warning, Alert, and Response Network Act, or classes of such alerts, from receiving such alerts by satellite. (b) Satellite alert regulations (1) Notice of proposed rulemaking Not later than 6 months after the date of the enactment of this Act, the Commission shall publish a Notice of Proposed Rulemaking to establish relevant technical standards, protocols, procedures, interoperability requirements, and other technical requirements necessary to enable satellite alerting capability for providers of commercial mobile service that voluntarily elect to transmit emergency alerts, including standards for training such providers on enabling such capability. (2) Final rule Not later than 12 months after the date of the enactment of this Act, the Commission shall, in consultation with the Secretary of Homeland Security and the Administrator of the Federal Emergency Management Agency, issue a final rule establishing the standards, protocols, procedures, and requirements described under paragraph (1).

AI plain languageRead the whole bill in plain language, 2 sections

Where it is

Introduced · 2026-01-12

In the House.

Passed the House · 2026-04-20
Senate floor vote · next · the next step

Official documents

The on-site text is shown verbatim from the GovInfo publication, captured 2026-07-23. The same version at GovInfo.

The numbers

29%
of bills that passed one chamber became law in the 118th Congress, 2023 to 2024 (n=939)
5
sponsors, out of 218 needed to pass

Who is lobbying on this

COMPETITIVE CARRIERS ASSOCIATIONvia COMPETITIVE CARRIERS ASSOCIATION
2 filings
CTIA-THE WIRELESS ASSOCIATIONvia CTIA-THE WIRELESS ASSOCIATION
2 filings
CTIA: THE WIRELESS ASSOCIATIONvia MERCURY STRATEGIES, LLC
2 filings
PEACE OFFICERS RESEARCH ASSOCIATION OF CALIFORNIAvia STEPTOE LLP
2 filings
VERIZON COMMUNICATIONS INC AND ITS SUBSIDIARIESvia MERCURY STRATEGIES, LLC
2 filings
VERIZON COMMUNICATIONS INC AND VARIOUS SUBSIDIARIESvia VERIZON COMMUNICATIONS INC. AND VARIOUS SUBSIDIARIES
2 filings
From 12 filings in federal lobbying disclosures (LDA), via lda.gov, naming this bill (2026). Filings are self-reported by lobbying firms and show who is paid to influence this bill. They do not say which side, or whether it worked.
Every fact on this page links to its source, starting with the official bill record. Last action: Received in the Senate and Read twice and referred to the Committee on Commerce, Science, and Transportation. (2026-04-21).