# Try Helpdesk Triage in your browser

> Triage a ticket. Approve the route. Read the receipt.

The cards the product ships, on eight sample tickets kept in your browser’s own
storage. No sign-in, no tenant; the sample tickets live only in your browser, and
Reset clears them. Open a ticket, ask for a scripted proposal, change a field,
approve it, and read the receipt. **Limited preview — enrolling by conversation.**

Sandbox: https://try.celest.dev/helpdesk-triage

## The loop, in your hands

Start with an exception such as HD-06, “Cannot sign in after MFA prompt”. Ask
for a proposal, change the queue or the reply if you disagree, approve, and
watch the receipt read the ticket back. The sandbox scripts the proposal so
you can see the loop without a model; in the product, Microsoft 365 Copilot
writes the proposal from the queue it is shown.

## What you are looking at

- **The queue is what Copilot reads.** Exceptions first, with the reason each one
  stalled. The routing vocabulary goes to Copilot with the queue, and a
  proposal can only use values from it.
- **The proposal is what you approve.** One exact change, field by field, with
  evidence marked observed or inferred, what is still missing, a rationale,
  and a confidence. Nothing is applied until you approve.
- **The receipt is what the record says.** After approval the change is
  applied with the ticket’s version check and read back: verified, stale, diverged,
  indeterminate or failed, and the run is recorded as a row in your runs list.

## Next step

Bring one queue of your own: [limited preview](https://celest.dev/helpdesk-triage/preview),
[docs](https://celest.dev/helpdesk-triage/docs), [security](https://celest.dev/helpdesk-triage/security).