Designing Companion Conversational Interfaces

UX teams who spent a decade perfecting web and mobile apps are suddenly being asked to design chatbots, Teams agents, and Copilot experiences. Most of them reach for the tools they know best: grids, filters, tabs, navigation, and dense panels. The result is predictable: a cramped, worse version of the app that already exists, wearing a speech bubble as a costume.

Consider a familiar scenario. A sales rep has a web dashboard showing their leads, pipeline stages, call notes, and next actions. The product team decides to ship a companion experience in Microsoft Teams or M365 Copilot, not a replacement, a complement. The UX team gets the brief and starts sketching a list view with filter chips and a detail pane rendered as an Adaptive Card. A dashboard, but smaller. A dashboard, but worse.

Conversation is not a compressed app shell. It is a sequential medium optimized for one question, one summary, one action, one moment.

Here is how to think about it.

1. Start From Moments, Not From Screens

Do not inventory the dashboard's features and ask, "How do we put each one in chat?" Inventory the moments in the user's day when they do not want to open a dashboard at all.

• Between meetings, on mobile, walking down a hallway.
• Inside a Teams thread where a colleague just asked, "What's the status of Contoso?"
• At 8:55 AM, wanting a quick readout before a 9 AM call.
• Right after a call ends, with one sentence of context they will forget in an hour.

These moments are what the conversational surface is for. If a task requires scanning forty leads sorted by five columns, that is emphatically a dashboard job. Link to it. Do not rebuild it.

2. Conversation Is For The One Thing

A useful split is this: dashboards excel at comparison, scanning, multidimensional filtering, bulk editing, and visualization. They are spatial. They reward the eye. Conversation excels at a specific question, a specific record, a specific action, or a specific summary. It is sequential. It rewards brevity.

Every conversational response should feel like it answered this question for this lead right now, not like a paginated list waiting to be navigated with arrow keys.

3. Proactive, Not Just Responsive

A dashboard is pull. You go to it when you want something. A good companion is push, used sparingly, with judgment, and always with a clear reason.

• "Your 10 AM with Acme is in fifteen minutes. Last touchpoint was a pricing objection. Here's a two-line recap."
• "Three leads you marked hot last week have gone silent. Want to draft follow-ups?"

Proactivity is the single biggest differentiator between a companion agent and a dashboard, and it is the principle UX teams most often skip because it demands thinking about when to speak, not just what to show.

4. Respect The Host Surface

A companion agent in Teams or M365 Copilot lives next to human conversations, and that context dictates the rules of the room.

• Responses should read like a competent colleague's message, not like a form-filled template.
• Adaptive Cards are a tool, not a default. Do not turn every reply into a card when a sentence will do the job better.
• @mentions, threads, and message actions are already part of the vocabulary users know. Use them instead of inventing new affordances that only exist inside your agent.

The agent is a guest in someone else's app. Act like it.

5. Always Leave A Bridge Back To The Dashboard

The companion is not a silo, and pretending otherwise is how you build a frustrating one. Every substantive response should carry a contextual deep link such as Open Acme in dashboard. The agent handles the quick eighty percent of interactions; the dashboard handles the twenty percent that need richer tooling.

Users should never feel trapped in chat, trying to do in twelve turns something they could do in one click.

6. Context Is The Feature

A conversational interface is only as good as what it already knows when you start typing. At minimum, the agent should be aware of who the user is, what their pipeline looks like, what was said in the previous turns of this conversation, what was said in previous sessions, and what is happening on the user's calendar and inbox where permissioned.

• Who the user is and what their pipeline looks like.
• What was said in the previous turns of this conversation.
• What was said in previous sessions: persistent memory of recent leads, preferences, and ongoing threads.
• What is happening on the user's calendar and inbox, where permissioned.

Without this, every turn becomes a re-authentication of intent. Which lead? Which quarter? Which Acme? That friction is one of the fastest ways to make the companion feel worse than the dashboard it was supposed to complement.

7. Design Dialogue Flows, Not Decision Trees

The old chatbot world, "Press 1 for leads, 2 for accounts," was a world of rigid decision trees. LLM-era conversational UX is closer to writing a playbook for a capable new hire.

• What topics should they confidently handle end to end?
• What should they gather more context on before acting?
• When should they hand off to the dashboard, to a human, or to another agent?
• What tone should they take? How verbose? How willing to speculate?

This is prompt engineering practiced as UX craft. It is the conversational analog of interaction design, and it is where UX teams add the most value once they stop drawing wireframes and start writing instructions.

8. Ground Every Factual Claim

On a dashboard, a number is trusted because its provenance is implicit. In chat, that same number stated in prose can just as easily be a hallucination. Companion agents must cite the record, the field, and the timestamp when stating facts. They should say "I don't know" or "I couldn't find that" rather than confabulate a plausible answer, and they should prefer linking to the dashboard row over paraphrasing it when precision matters.

The fastest way to destroy trust in a companion agent is to be confidently wrong once. The second fastest is to be vaguely right in a way the user has to double-check every time.

9. Make Actions Reversible And Confirmable

Conversation makes destructive actions dangerously easy. "Update the stage to Closed Lost." Done. One sentence, no confirmation dialog, no dragging a card across a board. Companion agents touching shared data must slow down irreversible actions without slowing down everything else.

• Explicit confirmation on writes, especially bulk or irreversible ones.
• Undo as a first-class response: Reverted. Anything else?
• Previews before commit for anything that changes state others depend on.

10. Measure Different Things

Dashboard metrics such as daily active users, time on page, and clicks are misleading when applied to conversational UX. More time in chat is not better. More messages are not better. What matters instead is whether the companion quietly removes work.

• Task completion without escalation to the dashboard.
• Turns per task, where fewer is usually better.
• Acceptance rate on proactive messages.
• Trust signals: does the user act on what the agent says or silently re-verify in the dashboard every time?

What This Looks Like In Practice

Return to the sales rep. A companion that takes these principles seriously probably shows up like this.

What it should not try to be is a chat-shaped rendering of the pipeline grid.

The One-Line Version

A companion conversational interface succeeds when it does the things the dashboard is bad at: quick answers, proactive nudges, and in-context capture, then confidently hands off everything else back to the dashboard. The craft is knowing which is which.