Support Console
Prov1.0.0Answer one ticket with the customer's context beside it: thread, notes, suggested replies and a fix button.
Build for your project
Code/install build
Usage
Import it and pass your content. The props that matter most are listed next.
Example
import { SupportConsole, type ConsoleMessage, type ConsoleStatus } from "@/components/ui/notchset/blocks/support-console";
export function Ticket({ messages, status }: { messages: ConsoleMessage[]; status: ConsoleStatus }) {
return (
<SupportConsole
subject="Scheduled export paused"
ticket="#4821 · REPLY WITHIN 38M"
status={status}
messages={messages}
onSend={(kind: "agent" | "note", text: string) => fetch("/api/tickets/4821/messages", { method: "POST", body: JSON.stringify({ kind, text }) })}
/>
);
}Props
messages / typing–ConsoleMessage[] / booleankind event, customer, agent or note; agent messages can be seen. Controlled by your app.
status / onStatusChange–'open' | 'waiting' | 'resolved' / (status) => voidThe chip, and RESOLVE / REOPEN.
onSend–(kind: 'agent' | 'note', text) => voidA reply or an internal note was sent.
subject / ticket / macros–string / string / { label, text }[]Header lines and suggested replies.
account / issue / past–{ label, value }[] / { title, problem, detail, action, onAction } / { title, meta }[]The aside; issue.onAction resolves with its result line.
Anatomy
- The last agent message shows DELIVERED or SEEN.
- Suggested replies fill the composer; they never send by themselves.
- PAST CONVERSATIONS starts closed.
SupportConsoledata-slot="support-console"Header, thread, composer and the context aside.
Source
components/ui/notchset/blocks/support-console.tsx
This component is included with Pro.
Try the live preview above. Get Pro to install the source.
Build for your project
Code/install build
Installation
pnpm dlx shadcn@latest add @beautiful-ui-pro/support-consoleNeeds your registry key. Your components.json style picks the Base UI or Radix build: radix-*, new-york and default get Radix, base-* gets Base UI.
Styles didn't apply?
The CLI adds the styles to the CSS file named in components.json (tailwind.css). Check that it points at your global stylesheet, that the project uses Tailwind CSS v4, and that the file is imported in your root layout. Installed by hand: paste styles.css into that file.
For coding agents
Give your coding assistant the Markdown guide instead of screenshots.
Use it for
- Answering one conversation with account context
- Mixing replies and team-only notes in one thread
Use something else when
- Working through a queue: use Inbox Triage
- Live chat for customers: use Help Widget
Mistakes to avoid
- Keep notes out of anything the customer can see on the server too
- Send replies from the server; the block only reports them
Agents find it by
- support ticket, helpdesk conversation, agent console, customer support, internal notes, macros, Notchset
Where agents read it
- Guide for this component: https://beautiful-ui.dev/md/support-console.md
- Every component, for tools without MCP: /llms.txt
- MCP server:
https://beautiful-ui.dev/api/mcp(setup)
Behaviour
Keyboard
- Enter
- Send
- Shift + Enter
- New line
- ← →
- REPLY / NOTE
Accessibility
- The thread is a polite log; internal notes say TEAM ONLY in text, not only by colour
- Aside sections are buttons with aria-expanded; the composer is a labelled textarea
- The typing indicator is labelled
Motion
- New message
- Rises 10px into place (320ms settle); the log follows it
- NOTE mode
- The composer turns tint with a signal border
- Fix
- A scanner while it runs, then the result line
Responsive
- Under 860px (container width) the aside moves under the thread.
Performance
- Plain DOM; nothing runs while idle.
Changelog
v1.0.0 · 2026-10-04
First release
Part of
Included with Pro
Pro is in early access.
