Four surfaces. One question: what job is the user hiring the AI for?
When a founder says "we need an AI assistant," the question the PM has to push back with is: what shape of assistant? The shape — the UX pattern — is usually decided in a whiteboard meeting in the first week, and then never revisited. That's a problem, because the shape controls almost everything else: the prompt budget, the latency target, the eval rubric, the trust signals, the refusal design, the cost per task.
There are four canonical AI UX surfaces most shipped products today fall into. Not five, not twelve — four. Once you can name them and their tradeoffs, you stop picking "chat" by reflex and start picking the surface the user's task actually needs.
The four patterns, side by side
Each pattern has a skeleton UI, a default interaction rhythm, and a personality. Here they are in one frame — a chat bubble, an inline suggestion pill, an agentic task list, a copilot tool-tip — so you can see the shape of each before we unpack them.
The four patterns, unpacked
Here is the table every AI PM should screenshot and put in their design doc. Each row is one surface. The best for column is where the pattern earns its keep; the worst for column is where PMs typically pick it wrong.
| Pattern | Best for | Worst for | Key trust signal | Typical failure mode |
|---|---|---|---|---|
| 💬 Chat | Open-ended questions, broad scope, low urgency. "Explain this concept." | High-frequency narrow tasks (chat tax on every use) | Citations & sources inline | Confident hallucination with no source |
| ✨ Inline | One-field speed-ups — autocomplete, suggest-a-reply, fill-this-cell | Multi-step reasoning or anything the user wants to discuss | Ghost preview + explicit Tab/Accept | Auto-applying without user consent |
| 🤖 Agentic | Multi-step tasks with real-world actions (schedule, email, update) | Answers the user wants right now — latency will kill you | Visible task list + undo on every step | No rollback when step 4 of 6 goes wrong |
| 🧭 Copilot | User has a canvas they own (code, doc, problem) and wants help in context | Cold-start problems with no existing artifact | Confidence level + "why I suggested this" | Hiding its reasoning, so users can't calibrate |
The trust signal that defines each pattern
If there is one design decision per pattern that makes or breaks it, it's the trust signal. Four cards, one trust signal each. Miss one, and the surface collapses into distrust.
Scenario — VidyaPath, 10 weeks, one doubts-helper
Amara is a PM at VidyaPath in Bangalore. She has 10 weeks to ship an AI doubts-helper for high-school math — Class 9 and 10, CBSE board. The brief from leadership is one line: "help students when they're stuck, without just giving the answer." Target: 60% of students who use it pass their next topic test.
She has to choose one surface to ship by Week 10. Is it chat? Inline? Agentic side-panel? Copilot inside the problem-solving flow? The answer is not obvious, and the uncomfortable thing Amara discovers when she watches a dozen students use the prototype is that the surface she picks changes the pedagogy, not just the UX. A chat bubble begs to be given the answer. An inline auto-complete finishes the student's work for them. An agentic panel does too much, in the background, silently. A copilot — a hint-helper inside the problem canvas — is the only surface that gently nudges without taking over.
Amara picks copilot. Not because chat is wrong in the abstract, but because for this task (supervised learning, teacher-approved, anti-cheat) the shape must invite struggle, not replace it.
The 2×2 that made the call
Amara drew this on a whiteboard. Two axes: latency tolerance (how long the user will wait) and scope (one step vs many steps). The four patterns fall cleanly into four quadrants.
How it actually works — Amara's journey strip
Every AI UX decision eventually collapses to one sentence per column: what does the user want, which surface meets them, what does the AI do, what is the outcome? For the VidyaPath copilot, the strip looks like this.
Notice what the surface makes implicit: the copilot never returns a full worked answer — the AI action is "hint, not answer." That's not a prompt trick; it's a UX commitment. The surface shape enforces the pedagogy. Pick chat instead and the default rhythm is "user asks → AI replies with full solution." Pick inline and the default is "user writes → AI completes." Only copilot has "user struggles → AI nudges → user struggles more → AI nudges deeper" as the natural rhythm.
The AI connection
How real AI teams reason about this
The four patterns aren't just labels — they map onto four very different engineering stacks. Chat is built on streaming responses and conversation memory. Inline is built on low-latency small-model inference and ghost-text UI. Agentic is built on tool-calling, planners and rollback logs. Copilot is built on context-window packing (pulling the user's current artifact into the prompt) and confidence scoring. When you pick the surface, you pick the stack — and the stack decides your cost, latency and failure modes. streaming tool-calling context-packing rollback-log ghost-text
Mini challenge — pick the surface for three features
20 minutes, no coding. Three product briefs, one call each.
A Kenyan user taps "I don't recognize this charge." The AI needs to explain the transaction and offer next steps. Which surface? Write one line naming the primary trust signal. (Hint: low latency, narrow scope, user wants to talk.)
A Lagos seller is writing a product title. The AI can suggest a better title with SEO keywords. Which surface? What's the failure mode you have to design against? (Hint: one field, one suggestion at a time.)
The user uploads 12 months of statements and says "file my taxes." The AI needs to classify entries, fill forms, and surface edge cases for review. Which surface? What must be reversible? (Hint: the work takes 4 minutes; the user won't watch a spinner.)
Interview questions
(1) Detect scope growth. Either explicitly (user clicks a "Do this for me" CTA) or implicitly (the model's planner predicts >3 steps). Do not silently escalate.
(2) Explicit consent screen. "This will take about 4 minutes and will read your last 30 problems and draft a PDF. Proceed / Cancel." No autonomy without consent.
(3) Switch surfaces visibly. The copilot hint panel collapses; an agentic task list slides in with each planned step labeled. The user now sees progress, not a spinner.
(4) Undo and stop always available. Per-step rollback, plus a big "Stop" button. Agentic surfaces that can't be stopped are the number-one source of user distrust.
(5) Fall back gracefully. If any step's confidence drops below threshold, pause and flip back to copilot mode: "I started step 3 but I'm not sure — want to do this one yourself?" The surfaces should breathe in and out as the task demands, with the user always in the driver's seat.
Test your knowledge
Common mistakes
Key takeaways
- Four canonical AI UX surfaces: Chat, Inline, Agentic, Copilot. Learn all four before you pick one.
- Pick the surface by mapping the task onto the latency × scope 2×2 — not by what's easiest to prototype.
- Each pattern has a defining trust signal: chat → citations, inline → explicit accept, agentic → undo, copilot → confidence.
- Surface choice is pedagogy choice for learning products, and authority choice for everything else — it defines who owns the next action.
- Design the handoff between surfaces when task scope grows or shrinks. Explicit consent, visible switch, undo always available.
- "We'll just build a chatbot" is almost never the right answer. Make the team defend chat the way they'd defend any other PRD decision.
You can now pick the right AI surface.
Now design the trust signals around it.
Join the Best AI Program: The AI-Era Agentic Engineer — 5 months, fully online, with placement assistance. Week 1 is free.
Explore The AI-Era Agentic Engineer →