Celest
Sections
Join limited preview

Celest · Helpdesk Triage · 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.

Start a preview conversation Read the operating docs

Limited preview — enrolling by conversation. Write to [email protected] with the shape of your queue and one ticket that stalled.

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.

Proposal card for HD-07, Shared folder access needs triage: the assistant proposes 7 changes at confidence 0.78, with its rationale and the change field by field, Department IT, Priority High, Category Identity & Access
Casey reviews the proposal.One exact change, the evidence marked observed or inferred, what the ticket is still missing, and the reply draft, all editable before approval. Demo workspace · example data.View full size
Verified loopBy 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.
Review loopQueue, evidence, proposal, named approval, one update, and readback
Product shapeA tenant-wide SharePoint Framework package with a Copilot Component, a page, a list command bar, and customer-owned Lists

Send the useful context

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.

  • 1
    Your role

    Who owns the queue, and who gives the approval that counts?

  • 2
    Your queue

    Which SharePoint site, list, or service desk intake should we understand?

  • 3
    Your exception

    Which ticket would make the conversation useful for your team?

  • 4
    Your shape

    Monthly volume, SPFx or tenant constraints, and timing.

Start a preview conversation Talk through a question

What happens next

See it against your real queue.

The preview starts with one queue and one ticket. Together we make the current work visible and name the next useful step.

  1. 01
    Send the useful context

    A few lines about your role, your queue, and one ticket give the conversation its starting shape.

  2. 02
    Map your queue

    Your routing vocabulary, accountable owners, approval boundary, and handoff expectations.

  3. 03
    Walk one exception

    Queue, proposal, approval, receipt, with you at the keyboard.

  4. 04
    Name the next useful step

    Fit, open questions, and what a scoped pilot would require.

Explore the workflow

Overview: The product story: Copilot proposes, you decide, SharePoint keeps the receipt.Docs: The operating contract: boundary, receipt, statuses, limits.Support: Talk through a queue, pilot, operating question, or incident.Product privacy: What the package touches, what Celest receives, what setup creates, and retention.Security: Where it runs, what it never does, and what setup creates.Uninstall: Access removal, receipt preservation, and deletion requests.