Watch someone plan a weekend trip today and you will see two very different behaviours, often in the same household.
One person opens a search engine, scans the results, opens a few tabs, compares, goes back, refines the search, opens a booking site, creates an account, fills in a form. The other opens ChatGPT or Claude and types: "Find me a quiet hotel near the old town in Lisbon for two nights in October, walking distance to good seafood, under two hundred a night." Then they say "book the second one" and go back to whatever they were doing.
The first behaviour is navigating. The second is asking. The shift from one to the other is the most important change in how people use software since the smartphone, and it is happening one habit at a time.
What actually changes when people ask instead of navigate
Navigation puts the work on the person. You have to know where things live, in what order to visit them, and how to translate what you want into the buttons each site offers. Every service is an island with its own map.
Asking moves that work to the assistant. The person states the outcome once, in their own words, and the assistant does the visiting, comparing, and clicking. A few things follow from that.
The middle steps disappear. Nobody enjoys the eight clicks between "I need this" and "done". When an assistant can take them, people stop tolerating them. A service that still needs a person to navigate it is competing against one that does not.
Memory becomes expected. After a few conversations, people assume the assistant knows their preferences, their past orders, their calendar. They do not want to re-enter the same details on every site. The assistant becomes the place where context lives, and services are expected to plug into it rather than rebuild it.
Comparison happens out of sight. When someone asks for "the best option", the assistant looks at several services and comes back with one or two. The person may never see the others. Being visible in that comparison is a new kind of distribution, and it is decided by whether the assistant can read and act on your service, not by your homepage.
Voice and the phone amplify it. Speaking a request to a phone or an earbud is far easier than typing, and impossible to combine with tab hunting. The more people ask out loud, the more they expect the answer to be an action, not a list of links.
Why now
None of this is a new dream. Voice assistants promised it a decade ago and mostly delivered timers and weather. What changed in the last few years is that the assistants became genuinely capable of understanding an open-ended request, and, more recently, of doing something about it.
Two developments matter most. First, the assistants moved into the places people already are: the phone, the browser, the operating system, the messaging app. Asking is now one gesture away, always. Second, the assistants learned to use tools. Open standards such as the Model Context Protocol mean an assistant can connect to a service and call it, rather than only talking about it. That turned "I know a good hotel" into "I booked it for you".
Search engines have responded by answering directly instead of only listing links. Assistants have responded by adding browsing and connectors. From the person's point of view, the two are converging on the same experience: describe what you want, get it done, move on.
What it means for a service
If your customers are starting to ask instead of navigate, the honest question is not "how do we get more traffic to our site". It is "can an assistant use us on our customer's behalf?"
That question breaks into a few practical ones.
Can it find out what you offer? Assistants read documentation and structured descriptions. If the only way to understand your service is to click through your interface, the assistant will guess, or move on to a competitor it can read.
Can it act, safely? Looking something up is easy. Booking, ordering, cancelling, and paying need a defined action, clear inputs, and a confirmation step before anything irreversible happens. Services that expose those actions deliberately get used; services that leave the assistant to fill in web forms get used badly or not at all.
Does it know who is asking? When a person delegates a task, the assistant is acting for that specific customer. Your service needs a clean way to recognise them and to limit what the assistant may do on their account.
Is anyone watching? Once an assistant is calling your service, it is a production channel. It needs the same care as your website: monitoring, rate limits, and someone paying attention when something changes.
The homepage is moving
For twenty years, the homepage was the front door and navigation was how people walked through it. That door is still there, and it still matters. But a second door has opened inside the assistant, and a growing share of people are arriving through it, usually without ever seeing the first one.
The services that thrive in the next few years will be the ones that can be reached through both. That does not mean rebuilding your product. It means making it usable by an assistant: a clear description of what it can do, a small set of safe actions, and a hosted connection that assistants can rely on.
If you want to know how close your service already is, our free Agent Readiness Audit takes about two minutes. It reads what you share, proposes the tools an assistant would get, scores what is ready, and gives you a fixed price to have the connection built, hosted, and maintained under your own domain.
The habit is changing. The question is whether your service is ready to be asked.