The White House plans to move passport and Medicare sign-ups behind America.gov's chatbot

A person who types a question about passports into America.gov gets, in the site's own description, "simple answers only from official government sources" ^[1][2]. They do not need an account to ask ^[5]. Next year, the same chatbot is supposed to take the passport application itself ^[8].

Announcing the site on Tuesday ^[4], Trump said on X: "Instead of forcing citizens to search through the endless maze of tens of thousands of government websites and rules... you'll now have one front door for every single question" ^[13]. What ships today is narrower. According to Engadget, America.gov currently sorts through information that was already openly available and performs none of the services it describes ^[8].

The executive order changes what the product is for. It directs officials "to establish and operate America.gov as the single point of entry for Americans to access covered services online, and to integrate Login.gov with America.gov" ^[9]. The privacy promises suit an anonymous question box: no stored messages, no account, and a feature the site says will help "prevent you from sharing personal information before you send it" ^[3][5]. Engadget reported that the site has not explained how those promises fit with tasks that "rely entirely on citizens' personal data" ^[12].

Teams will hear that citizens want one door for every question ^[13]. Neither Engadget's nor TechCrunch's report includes a usage figure showing what citizens do with the door, and Engadget's excerpt of the order does not say which services count as covered ^[9].

For an agency, the model paraphrasing its eligibility rules is also only partly known. Google has confirmed Gemini ^[6]. Grok's part rests on Joe Gebbia's interview ^[7]. TechCrunch, noting that large language models remain prone to hallucinations ^[10], wrote that errors on food stamps, visas or taxes could mean missed deadlines, denied benefits or penalties ^[11].

For a team that runs a federal service, I'd sort each flow on two questions. The first is whether the flow needs to know who the user is. Under this order, that means a Login.gov handoff ^[9]. The second is what the user loses when an answer is wrong ^[11].

Anonymous, low-stakes answers are what America.gov already gives, so the work there is keeping the source page accurate, because that page is what it quotes ^[2]. Anonymous answers with high stakes, such as a filing deadline, get paraphrased today too, and the agency's own page remains the version it answers for ^[2]. Signed-in flows with lower stakes are where I'd design the Login.gov handoff first. Signed-in flows with high stakes, like Medicare enrollment ^[8], are where I'd keep the transaction on the agency's own system, with the chatbot routing users to it. I'd hold that line until the site explains how its no-retention policy applies to personal data ^[3][12]. The cost is a possible second build if next year's actions arrive as chat-native flows that agencies are then asked to match ^[8].