# Support Console (Notchset): prompt.md (v1.0.0)

- id: `support-console` · version 1.0.0 · block · pro (Pro)
- category: Application UI
- build: Base UI (one set of files; its dependencies follow the build)
- install (this build): `npx shadcn@latest add @beautiful-ui-pro/support-console`
- npm dependencies: class-variance-authority@^0.7
- registry dependencies: utils, @beautiful-ui/segmented-control, https://beautiful-ui.dev/r/notchset-foundation.json
- docs: https://beautiful-ui.dev/components/support-console
- The install command carries everything this item needs (files, CSS, tokens, npm and registry dependencies). Prefer it to copying source by hand.

A ticket view: a status chip (open, waiting on customer, resolved) with resolve and reopen, a conversation log of event lines, customer messages, agent replies and internal notes that follows the newest message with a typing indicator, a composer with suggested replies and REPLY / NOTE (notes turn the composer signal), and an aside with collapsible account details, the issue with a one-click fix, and past conversations.

## Build it
- Stack: React 19 (`ref` is a plain prop), TypeScript, Tailwind CSS v4 utilities, a shadcn-initialised project with the `@/*` alias.
- Packages: `class-variance-authority@^0.7`.
- Files: `components/ui/notchset/blocks/support-console.tsx`; shared code: `lib/beautiful-ui/notchset/instrument.tsx`, `lib/beautiful-ui/notchset/root.ts`, `lib/beautiful-ui/notchset/button-variants.ts`, `lib/beautiful-ui/notchset/field-classes.ts`.
- Registry dependencies, installed with it automatically: shadcn `utils` (cn), `segmented-control`, `notchset-foundation`.
- Builds: one set of files for both, but its dependencies come in Base UI and Radix builds. Install the one that matches the project (see Install): a free item's bare URL installs the Base UI build of it and its dependencies.
- Exports to keep: `SupportConsole`, and every exported type.
- CSS: the install adds the notchset foundation (tokens, keyframes, motion levels) to your global stylesheet once. Nothing to import by hand.
- Re-running `add` (or `--overwrite`) re-applies those rules: put overrides in your own CSS, never in the installed rules.
- Tokens: retheme with the `--notchset-*` custom properties (`--notchset-check`, `--notchset-control-edge`, `--notchset-draw-from`, `--notchset-ease-bloom`, `--notchset-ease-glide`, `--notchset-ease-key-down`, `--notchset-ease-key-up`, `--notchset-ease-travel`, `--notchset-fade`, `--notchset-focus-color`, `--notchset-focus-inset`, `--notchset-grow-to`, `--notchset-key-down`, `--notchset-key-up`, `--notchset-life-from`, `--notchset-life-ms`, `--notchset-node-blink`, `--notchset-node-bloom`, `--notchset-node-delay`, `--notchset-plate-color`, `--notchset-rise-from`, `--notchset-rule`, `--notchset-scan-to`, `--notchset-scroll`, `--notchset-signal`, `--notchset-sweep-to`, `--notchset-travel`). Never add Tailwind colour classes inside the component.

```tsx
import { SupportConsole, type ConsoleMessage, type ConsoleStatus } from "@/components/ui/notchset/blocks/support-console";
```

## Parts

| Part | data-slot | What it is for |
|---|---|---|
| `SupportConsole` | `support-console` | Header, thread, composer and the context aside. |

Style a part with `[data-slot="<slot>"]` selectors or its `className`; keep the attributes when editing.

## Sound
- Keep every `data-slot` and `data-sound` attribute: the sound layer reads them.
- Installing this item adds no audio. Nothing plays until the app mounts `SoundProvider` once (install: `npx shadcn@latest add https://beautiful-ui.dev/r/notchset-sound.json`, import from `@/components/ui/notchset/sound-provider`); `useSound()` gives `muted` and `setMuted` for a mute control. Without a provider the audio engine never loads.

## Match the original
- Read `components/ui/notchset/blocks/support-console.tsx` as the reference implementation before changing or recreating anything, and match it: sizes, colours per theme, motion timings, copy and behaviour.
- If you deviate (a prop you can't honour, a style you changed, a dependency you swapped), say so in your reply, part by part.
- Keep the accessibility contract, the keyboard map and the motion levels listed below.

## Use it when
- support ticket, helpdesk conversation, agent console, customer support, internal notes, macros, Notchset
- Answering one conversation with account context
- Mixing replies and team-only notes in one thread

### Not when
- Working through a queue: use Inbox Triage
- Live chat for customers: use Help Widget

## Mistakes
- Keep notes out of anything the customer can see on the server too
- Send replies from the server; the block only reports them

## Usage

```tsx
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

| Prop | Type | Default | What it does |
|---|---|---|---|
| `messages / typing` | `ConsoleMessage[] / boolean` |  | kind event, customer, agent or note; agent messages can be seen. Controlled by your app. |
| `status / onStatusChange` | `'open' \| 'waiting' \| 'resolved' / (status) => void` |  | The chip, and RESOLVE / REOPEN. |
| `onSend` | `(kind: 'agent' \| 'note', text) => void` |  | A 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. |

Full docs: https://beautiful-ui.dev/components/support-console

## Customising
- Colours: the component reads your shadcn tokens (`--background`, `--foreground`, `--border` …), refined by the `--notchset-*` tokens. The signal colour is `--notchset-signal` (it falls back to `--destructive`). Set tokens on `:root`, or on any container to retheme one area.
- Dark mode follows the `.dark` class on an ancestor (the shadcn and next-themes convention).
- Update later by re-running the install with `--overwrite` (review the diff if you edited it). Changelog: https://beautiful-ui.dev/r/changelog.json

## Keyboard

| Keys | Action |
|---|---|
| Enter | Send |
| Shift + Enter | New line |
| ← → | REPLY / NOTE |

## Performance

- Plain DOM; nothing runs while idle.

## Responsive

- Under 860px (container width) the aside moves under the thread.

## Motion inventory

| Interaction | What moves |
|---|---|
| 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 |

## Accessibility contract (preserve when editing)
- 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

## Install

```bash
npx shadcn@latest add @beautiful-ui-pro/support-console
```

Pro item: needs the `@beautiful-ui-pro` registry in `components.json` and `BEAUTIFUL_UI_TOKEN` in `.env.local` (https://beautiful-ui.dev/account). Setup: https://beautiful-ui.dev/docs/pro. Your components.json `style` picks the build: radix-*, new-york and default get Radix, base-* gets Base UI.

## Credits
- Built on shadcn/ui (https://ui.shadcn.com)

The notchset foundation (the tokens listed above, keyframes and motion levels) installs once with the first component; its CSS is public at https://beautiful-ui.dev/r/notchset-foundation.json.