100+ Threats to KILL Trump Went Unanswered

Donald Trump speaking at a microphone in a black-and-white photo — Photo: Joseph Sohm / Shutterstock

When citizens flag explicit threats against a sitting president and the messages appear to stall in the system, the question isn’t just “who failed to reply”; it’s whether the nation’s protective-intelligence machinery is aligned to capture, triage, and act on risk at the speed and volume today’s environment demands.

At a Glance

WeTheJ6ers co-founder Barry Ramey says he sent threat material about President Trump to the Secret Service within 80 minutes of an agency request, then followed up nine times over 25 days without a response.
The Secret Service’s threat assessment model distinguishes between alarming messages and individuals who meet investigative thresholds; how that model ingests citizen-submitted tips is central to this dispute.
Open-source threats against protectees can surge; prior records show large volumes around politically charged periods, underscoring triage pressure inside protective intelligence.
The policy issue is procedural, not partisan: clear intake channels, documented acknowledgments, and feedback loops reduce both operational risk and public mistrust.

What Ramey Reported, and Why It Matters

According to reporting, the sequence began on September 12 when the Secret Service asked Barry Ramey, a co-founder of WeTheJ6ers, for evidence of threats against President Trump. Ramey says he supplied the material within 80 minutes and then sent nine follow-up emails over the next 25 days seeking acknowledgment or action, with no reply reported by the time of publication. This is a straightforward logistical claim—date-stamped outreach, prompt submission, and repeated follow-up—which places the burden of explanation on how the government’s protective-intelligence intake operates when citizens hand over potentially time-sensitive data.

The gravity is self-evident: any credible threat against a sitting president is a national security matter. But urgency alone does not settle process. Protective intelligence is not merely a yes/no to “Did someone read the email?” It is a workflow: intake, initial screening for immediacy and specificity, case-building if thresholds are met, and risk management. When the public encounters silence after sending in frightening material, it is natural to infer inaction. Whether that inference is accurate depends on how the system is designed to communicate—internally and outward to tipsters.

How Protective Intelligence Actually Works

The U.S. Secret Service has long defined threat assessment as an investigative process that identifies, assesses, and manages individuals who may pose a risk to protectees. That process separates alarming messages from actionable cases and emphasizes behavioral indicators, capability, and intent over rhetoric alone. In practice, protective intelligence starts well before an event: analysts collect open-source signals, correlate tips, evaluate specificity (targets, timeframes, operational detail), and quantify imminence. When the system functions, it quickly elevates time-urgent threats, routes them to the appropriate field and protective teams, and initiates mitigation ranging from interviews to arrest via partner agencies, depending on probable cause and jurisdiction.

Two aspects matter for the Ramey account. First, the agency’s model is built to ingest large quantities of low-signal data—much of it emotional or hyperbolic—without missing the handful with operational detail. Second, because the focus is on the subject (the would-be actor) rather than the message alone, the best tips include identifiers and corroborants: names, handles, IPs, geolocation cues, purchase histories, weapons access, or documented reconnaissance. The more a submission speaks to capability and planning, the more likely it is to cross investigative thresholds promptly.

Volume and Triage: Why Intake Can Feel Opaque

Periods of political tension generate sharp spikes in open-source threats. Leading up to January 6, 2021, federal documents reflect dozens of web-based “behaviors of interest” directed at top officials in a single week, illustrating the scale and speed at which protective teams must filter signal from noise. Committee materials and subsequent analyses likewise describe Secret Service awareness of threats in volatile windows, an institutional reminder that the system routinely confronts more leads than any one office can handshake-acknowledge in real time.

None of this justifies a broken feedback loop. It does explain why a citizen who submits something alarming may hear nothing back even while an investigation is quietly underway—or, alternatively, while the material is logged but not elevated because it lacks actionable identifiers. The public-facing intake experience is, by design, conservative: tipsters are not entitled to case details. But there is a middle ground between operational secrecy and radio silence: an acknowledgment that the material was received and routed, plus standardized guidance on what types of evidence accelerate assessment.

What Ramey’s Account Suggests About Gaps

If the reported timeline is accurate—initial Secret Service outreach to Ramey, rapid submission, then nine unanswered follow-ups over 25 days—it points to two potential shortfalls. First, intake clarity: a request for evidence should come with explicit instructions on format, identifiers, and a single case reference. Second, acknowledgment discipline: even if the content does not meet investigative thresholds, a minimal response closes the loop and preserves public confidence in the system’s diligence. The underlying protective mission is too important to allow the appearance of indifference, particularly given the heightened threat environment around a traveling president and visible campaign activity.

On the other side of the ledger, the protective-intelligence standard deliberately resists action on rhetoric alone. Agencies look for specificity—time, place, capability signals, procurement behavior, or reconnaissance. In recent cycles, some arrests tied to threats against President Trump included references to mapped rooftops and event locations, the sort of operational detail that vaults a case to the top of the stack. Open-source reporting has highlighted such cases, underscoring how concrete planning indicators galvanize rapid intervention by the Secret Service and partner law enforcement.

The Institutional Fix: Intake Architecture and Accountability

Threat assessment doctrine is mature; intake architecture is where practice lags perception. Three adjustments would materially reduce friction without compromising investigations. First, a unified intake interface—web and email—that generates an immediate case number and a timestamped receipt, with a short checklist of “what elevates your submission” based on Secret Service criteria. Second, a 72-hour courtesy follow-up template, sent automatically, that outlines next steps in general terms and asks for any missing identifiers. Third, an internal service-level metric: time-to-initial-triage for outside submissions, tracked and audited alongside existing protective metrics. None of these reforms require disclosing investigative steps; all of them demonstrate procedural respect for the public’s role in early warning.

Agencies already publish guidance on behavioral threat assessment and encourage multi-agency coordination; codifying transparent intake hygiene is a natural extension of that ethos. It also insulates the institution from politicized narratives by replacing uncertainty with process. When the system can show that a tip was received, triaged within a defined window, and either escalated or archived based on stated criteria, disputes shift from “you ignored us” to “does this meet thresholds,” which is where the professional standards properly reside.

Bottom Line

The Ramey account, as reported, presents a credible process concern: repeated follow-ups about threats to President Trump apparently went unanswered after an initial agency request for evidence. That does not prove investigative inaction; it does reveal a communications seam that can and should be closed. Protective intelligence is built to separate noise from danger and to act decisively on specificity. It will do both more effectively—and with broader public trust—when intake channels consistently acknowledge, guide, and timestamp the civic vigilance they depend on.