No, you don’t need a chatbot
2016-ish: Chatbots were new, everyone wanted one, most were terrible. Rigid scripts dressed up as conversation. Customers went off-piste and hit a wall. The bubble deflated quietly.
Today: Executives have used ChatGPT, been impressed, and extrapolated. If it can do that, imagine what it could do on our checkout. Our customer portal. Our onboarding journey. Everything.
The technology being impressive doesn't make it the right fit for every interface decision. This is the conversation PMs and designers need to get better at having.
The core principle
A GUI encodes expertise into the screen. The customer doesn't need to know what's possible — the interface shows them. A conversational interface does the opposite. It transfers the burden of knowing what to ask back to the customer.
That's a reasonable trade in the right situation. In the wrong one, it's friction with a friendly tone.
When GUI wins
The task is routine, bounded, and repetitive. A customer logging in to check their order status doesn't want to ask for it. They want to see it. The screen pre-answers the question before they have to form one.
The customer needs to scan, not find. Comparing flight options, reviewing subscription tiers, browsing a product catalogue - these are parallel processing tasks. Chat serialises them into one answer at a time. That's the wrong rhythm for a customer making a decision.
Data entry has known, validated fields. Booking a hotel room, setting up a delivery address, configuring a software plan - forms enforce completeness. A chatbot introduces ambiguity at every step and moves past errors confidently. The customer only discovers the mistake later, when it costs them.
The action is consequential. Cancelling a subscription, processing a return, making a purchase - these need an explicit "you are about to do X" moment. A GUI does this naturally. A chat flow has to work hard to replicate it, and often doesn't.
Discoverability matters. First-time customers and infrequent users need to see what's available to them. A chatbot only surfaces what they already know to ask about. New customers exploring your product are the worst possible audience for an interface that requires them to know the right words.
When LUI wins
The query space is too large to menu-ify. A retailer with a vast catalogue. A bank with hundreds of product combinations. A customer asking "what's the right account for someone who travels a lot and wants cashback" has asked a question no dropdown can anticipate. Language is the only practical navigation tool for a space that large, and a well-designed conversational interface earns its place here.
The customer knows what they want, but not how to get there. "I want to change my delivery address, but the order's already dispatched." "I want to pause my subscription, not cancel it." "I was charged twice." These are goals, not navigable menu items. A chatbot that can understand intent and route accordingly removes real friction.
Interpretation is part of the answer. A customer asking why their claim was declined, or whether a specific product covers their situation, doesn't just need data. They need "here's what this means, here are your options, here's what to do next." A screen surfaces the information. A well-built conversational interface delivers the judgment alongside it.
The interaction is inherently sequential and contextual. Troubleshooting a product. Walking through a complex configuration. Wizard-style GUI flows break the moment someone deviates from the expected path. Customers deviate constantly.
Interface Decision Table
| Task | Right interface |
|---|---|
| Checking order status, account balance, booking details | GUI |
| Comparing products, plans, or pricing options | GUI |
| Booking, purchasing, or configuring with known fields | GUI / form |
| Cancellations, returns, or other consequential actions | GUI |
| First-time or infrequent customers exploring the product | GUI |
| "What's the best option for me given X and Y?" | LUI |
| Customer knows what they want, not how to get there | LUI |
| Query or complaint that needs interpretation, not just data | LUI |
| Troubleshooting or triaging a problem that branches | LUI |
| High-volume routine task with no decisions involved | Automate it |
| Routine journey with occasional complex edge cases | GUI + LUI layer |
How to frame this with execs
When an exec asks for a chatbot on a customer journey, don't push back on the technology. Push back to the right question: what is the customer actually trying to do, how often, and what's making it hard right now?
Sometimes the answer is a chatbot. Often it's a better-designed screen. The customer who can't find their delivery details doesn't need a conversational interface. They need the information somewhere obvious.
One thing worth being explicit about: a chatbot is not an upgrade to a broken customer journey. If the underlying experience is fragmented and the information is inconsistent, a conversational layer on top makes everything worse. The customer is now having a conversation with something that will confidently give them the wrong answer. We spend enormous effort making sure our content is clear, our journeys are understandable, and our products are trustworthy. That standard doesn't get suspended because the interface has become conversational.