# Helpdesk Triage limited preview

> Bring one exception. Leave with a clearer next step.

You know the ticket: open for a week because IT thinks it belongs to HR and HR
thinks it belongs to IT. Bring that one. A founder walks it through the product
with you, from queue to proposal to approval to receipt, using your routing
vocabulary, your roles, and your review practice. You leave knowing whether
this fits your desk and what a scoped pilot would take.

**Limited preview — enrolling by conversation.** Write to support@celest.dev
with the shape of your queue and one ticket that stalled.

## Preview details

- **Starting point:** One SharePoint exception queue
- **Conversation:** Roles, routing, approval, and handoff
- **Pricing:** Free during the preview
- **Format:** Founder-led preview path

## Working proof

It has run for real: queue, proposal, approval, receipt. The working proof lives in Celest's own tenant: a proposal fired through
SharePoint's Copilot Workbench, an operator approved in the card, SharePoint
applied one ETag-protected change, and the readback matched.

By 2026-09-04, in Celest's own tenant, the component loaded in SharePoint's Copilot Workbench had taken ticket HD-07 from a proposal fired by hand to an operator approval to a verified SharePoint readback receipt, and the shipped package had verified a hand triage from the tickets list's command bar. On 2026-09-04, inside Microsoft 365 Copilot, Copilot wrote a proposal on the sandbox's sample data and an operator's approval verified. The shipped package's own agent has not yet run inside Microsoft 365 Copilot chat.

The product shape is a tenant-wide SharePoint Framework package with a Copilot
Component, a page, a list command bar, and customer-owned Lists. The review
loop covers queue, evidence, proposal, named approval, one update, and
readback.

The proposal Casey reviews keeps one exact change, the evidence marked observed
or inferred, what the ticket is still missing, and the reply draft visible
together, all editable before approval. **Demo workspace · example data.**

## Tell us about one queue

Four lines is plenty. The email opens with prompts for your role, your queue,
your volume, and the ticket you want to walk. Answer the ones you know:

- Your role, and who gives the approval that counts
- The SharePoint site, list, or service desk intake to understand
- Approximate monthly ticket volume
- SPFx or tenant constraints
- Preferred timing
- The ticket that would make the conversation useful for your team

[Start a preview conversation](mailto:support@celest.dev?subject=Helpdesk%20Triage%20limited%20preview&body=Hi%20Celest%2C%0A%0AI%27m%20interested%20in%20the%20Helpdesk%20Triage%20limited%20preview.%0A%0ARole%3A%0AQueue%20or%20SharePoint%20site%3A%0AApproximate%20monthly%20ticket%20volume%3A%0AApproval%20owner%3A%0ASPFx%20or%20tenant%20constraints%3A%0APreferred%20timing%3A%0ARepresentative%20exception%20to%20walk%20through%3A%0A%0AThanks%2C)
or [talk through a question](https://celest.dev/helpdesk-triage/support).

## What happens next

1. **Send the useful context.** A few lines about your role, your queue, and
   one ticket give the conversation its starting shape.
2. **Map your queue.** Your routing vocabulary, accountable owners, approval
   boundary, and handoff expectations.
3. **Walk one exception.** Queue, proposal, approval, receipt, with you at the
   keyboard.
4. **Name the next useful step.** Fit, open questions, and what a scoped pilot
   would require.

## Source and status

- Canonical URL: https://celest.dev/helpdesk-triage/preview
- Product status: Limited preview — enrolling by conversation
- Contact: support@celest.dev
- Publisher: Celest, an independent software company building for Microsoft 365