- VeteransLikely improves veterans' access and caller experience by reducing time spent on hold and decreasing abandoned calls th…
- Targeted stakeholdersMay improve operational efficiency by smoothing call volumes (callbacks allow callers to be served without remaining on…
- Targeted stakeholdersCreates short-term demand for procurement, IT integration, and contractor work to supply and deploy automated call/queu…
Stuck On Hold Act
Referred to the House Committee on Veterans' Affairs.
The Stuck On Hold Act directs the Secretary of Veterans Affairs to install automated systems on each VA customer service telephone line that (1) inform callers of anticipated wait times and (2) automatically offer a callback to callers when the anticipated wait exceeds 10 minutes.
The Secretary must also issue guidance intended to reduce average caller wait times on covered lines to 10 minutes or less.
The statute excludes the VA toll-free veterans hotline under 38 U.S.C. 1720F(h) and emergency department phone lines from the definition of covered lines.
On content alone this is a narrow, technocratic fix aimed at improving VA customer service for veterans — a subject that typically attracts bipartisan support and relatively little controversy. The primary obstacles are administrative (costs, procurement, and implementation feasibility) rather than ideological. The absence of new entitlements or controversial policy changes increases the probability of enactment, particularly if the language is folded into a larger veterans or administrative package.
Relative to its intended legislative type, this bill is a concise administrative directive that clearly identifies the problem and sets high-level operational requirements and a firm deadline, but provides limited technical, fiscal, and accountability detail.
Scope and adequacy of funding: liberals want explicit appropriations and staffing complements; conservatives worry about unfunded mandates.
Who stands to gain, and who may push back.
- Targeted stakeholdersImplementation and ongoing operating costs (procurement, integration, maintenance, vendor contracts, and training) coul…
- Targeted stakeholdersAdds procurement and program management requirements that could strain VA IT and call center resources; a one-year dead…
- Targeted stakeholdersPotential privacy and cybersecurity risks from storing and handling callback contact data (phone numbers and call logs)…
Why the argument around this bill splits.
Scope and adequacy of funding: liberals want explicit appropriations and staffing complements; conservatives worry about unfunded mandates.
A mainstream progressive would generally view this bill positively as a practical, low-conflict measure to improve access to government services for veterans, particularly those with disabilities, limited mobility, or caregiving responsibilities who face barriers when forced to stay on hold.
They would see it as an incremental consumer-protection and service-delivery improvement that aligns with efforts to make public services more accessible and equitable.
However, they would want assurances that the measure is implemented in ways that protect privacy, does not become a substitute for adequately staffing VA call centers, and includes transparency and accountability (metrics and reporting).
A pragmatic, moderate observer would view the bill as a straightforward, commonsense operational improvement likely to be popular with constituents and relatively noncontroversial.
They would like clearer detail on costs, implementation plans, performance metrics, and oversight to ensure the mandate is practical and fiscally responsible.
Overall they would be inclined to support it if it is budget-neutral or paired with modest funding and clear timelines and accountability measures.
A mainstream conservative outlook would likely support the goal of improving service for veterans and may welcome efficiency gains from automation, but would be cautious about a new federal mandate that requires agency IT/contracting work without clear funding.
They would be skeptical of additional bureaucratic requirements and would want to limit scope, ensure cost-effectiveness, and protect against mission creep.
If the bill can be implemented cheaply and improves constituent satisfaction, conservatives would be open to it; otherwise they would press for cost controls and minimal new regulatory burden.
The path through Congress.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
On content alone this is a narrow, technocratic fix aimed at improving VA customer service for veterans — a subject that typically attracts bipartisan support and relatively little controversy. The primary obstacles are administrative (costs, procurement, and implementation feasibility) rather than ideological. The absence of new entitlements or controversial policy changes increases the probability of enactment, particularly if the language is folded into a larger veterans or administrative package.
- The bill contains no appropriation or specific funding mechanism; actual cost to implement and operate callback systems (and whether VA must seek new funds) is unknown and could affect support.
- Operational implementation details are delegated to the Secretary; lack of technical specifications or performance metrics beyond the 10-minute average target may produce debate about enforceability and oversight.
Recent votes on the bill.
No vote history yet
The bill has not accumulated any surfaced votes yet.
Go deeper than the headline read.
Scope and adequacy of funding: liberals want explicit appropriations and staffing complements; conservatives worry about unfunded mandates.
On content alone this is a narrow, technocratic fix aimed at improving VA customer service for veterans — a subject that typically attracts…
Relative to its intended legislative type, this bill is a concise administrative directive that clearly identifies the problem and sets high-level operational requirements and a firm deadline, but provides limited techn…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.