Views

A view is a dashboard your colleague builds for you, pulling data from whatever tools you’ve connected. KPIs, charts, tables, action buttons. Live — they refresh as the colleague gathers more data. You don’t build views by hand. You ask. Sofia, give me a dashboard of all open opportunities by stage, with a button to message the owner. She builds it, you use it.

​

Two ways views show up

Inline in chat. Most views start here. The colleague composes one in the middle of a conversation as part of answering. Useful for one-off summaries. As a saved page. When you want the dashboard to last, ask the colleague to save it. Now it lives at its own URL on your views page. Bookmark it. Open it tomorrow. Come back next month — the colleague keeps it fresh.

​

What goes in a view

Whatever the data needs:

• Big number tiles for the metrics you care about.
• Charts — area, bar, line, donut.
• Gauges and progress bars for things with a target.
• Tables with sortable columns and per-row buttons.
• Recommendation cards with reasoning.
• Forms to capture input from teammates.
• Alerts and call-outs for what needs attention.

If the data has shape, the colleague picks the right component. If you don’t like what they picked, just say so — make this a bar chart instead — they redo it.

​

Action buttons

Every view can have buttons that do real work. Click “Send follow-up” on a row in your sales view, the colleague drafts the email. Click “Open ticket” on an alert, it goes to Linear. Click “Refresh data”, the view re-pulls from the source. Buttons can run a tool directly — send the email now. Or they can kick off a side conversation, where the colleague thinks about how to draft the email first, then sends.

​

Where to next