Celest · Helpdesk Triage · Try it
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 HD-06, “Cannot sign in after MFA prompt”: ask for a proposal, change a field if you disagree, approve, and read the receipt. Proposals here are scripted; in the product, Microsoft 365 Copilot writes them.
Your sample tickets live in your browser’s storage for the sandbox, shared by your tabs. The sandbox server answers the page’s tool calls, stores no sample data and sets no cookies; Cloudflare keeps ordinary request logs for a few days. Open it in its own tab if the frame is too small. Limited preview — enrolling by conversation.
What you are looking at
The product’s working surfaces are these two cards, plus a setup card for the site owner; the receipt is the last section of the proposal card. The sandbox shows them in a page layout; the product also shows them inside Microsoft 365 Copilot and on the tickets list’s command bar.
Exceptions first, with the reason each one stalled. The routing vocabulary your desk uses (departments, priorities, categories, queues, assignees) goes to Copilot with the queue, and a proposal can only use values from it.
One exact change, field by field, with evidence marked observed or inferred, what is still missing, a rationale, and a confidence. Edit any field. Nothing is applied until you approve.
After approval the change is applied with the ticket’s ETag and read back. The receipt says verified, stale, diverged, indeterminate or failed, and the run is recorded as a row in your runs list.
