Interactive UI

What makes Copilot different from a typical chatbot? Instead of just text responses, Copilot renders interactive UI components that you can click to navigate, open records, and take action.

Why Interactive UI?

Traditional chatbots respond with text. If you ask "show my tasks," you get a text list. To open one, you'd have to search for it yourself.

Copilot's approach:

• Ask "show my tasks"
• See a clickable list of actual records
• Click any item to open it immediately

This saves time and keeps you in flow.

Component Types

RecordList

When you ask to see records, Copilot shows a RecordList:

• Title and count
• Each record as a clickable row
• Status and details as subtitles
• Click to navigate directly to the record

Triggers: "Show my tasks," "List open deals," "What contacts were added this week?"

FocusCard

When you ask about priorities, Copilot shows a FocusCard:

• Grouped by urgency (Overdue, Due Today, Coming Up)
• Color-coded by priority
• Each item clickable
• Summary of total items needing attention

Triggers: "What should I focus on?", "My priorities today," "What's overdue?"

DataTableCard

For tabular data with multiple columns, Copilot renders a DataTableCard:

• Column headers
• Sortable data rows
• Click any row to open the record
• Row count footer

Triggers: "Show a table of deals with value and stage," "List people with account and email"

MapCard

For geographic data, Copilot shows a MapCard:

• List of locations with addresses
• Click the arrow to open in Google Maps
• Click the record name to open in Coherence

Triggers: "Map our people," "Where are our customers located?"

NavigationCard

When Copilot navigates or creates something, it shows a NavigationCard:

• Destination label
• Description
• Click to navigate

Triggers: "Go to deals," "Create a task" (shows link to new record)

SearchCard

Search results appear in a SearchCard:

• Query shown at top
• Matching records with module labels
• Click to open any result

Triggers: "Search for Acme," "Find people named Sarah"

Interacting with Components

All components are fully interactive:

Combining Text and UI

Copilot often combines text responses with UI components:

You have 5 overdue tasks that need attention. Here they are:

[FocusCard with 5 items]

Would you like me to update any of these?

The text provides context, the UI provides action.

Follow-Up Actions

After viewing a list, you can reference items by number:

1. "Show my open deals"
2. [RecordList appears with 10 deals]
3. "Update #3 to stage 'Negotiation'"

Copilot understands #1, #2, #3 refer to items in the displayed list.

Mobile Experience

On smaller screens, components adapt:

• Lists become more compact
• Tables scroll horizontally
• Navigation cards stack vertically

All interactivity is preserved on touch devices.

What's Next?