Celest · Helpdesk Triage · Support
Email us.
We answer with the next step.
Use this support path for product questions, setup, incidents, uninstall and deletion instructions, and data-request routing. Limited preview — enrolling by conversation.
Contact support
Email [email protected] with “Helpdesk Triage” in the subject and the minimum context needed to route the request. Support cannot change a ticket for you; only an operator’s approval in the card does that. Report an incorrect or inappropriate proposal the same way.
Include the useful facts
- Whether this is a product question, a setup question, an incident, a deletion request, or another support need.
- The ticket id and the site, without the ticket’s contents.
- What you expected and what the card showed, including a receipt that reads stale or diverged.
Do not email secrets, tokens, protected ticket content, or unnecessary personal data. Send only the minimum context needed to route the request.
How we handle requests
Support confirms the scope and the next accountable person. For a ticket question the path is the product’s own: evidence, an exact proposal, approval in the card, one bounded update, readback and a receipt. A support reply is not evidence that a change happened.
Data-request route
This section is an instruction page, not an intake endpoint. It accepts no form, upload, secret, credential, or protected ticket content. Product data lives in your organization’s SharePoint lists, so requests about it go to your organization; requests about support mail go to [email protected] with the minimum context.
Security-sensitive issues
Email [email protected] with “security-sensitive” in the subject and describe only the minimum scope needed to route the issue. The security page describes where the package runs. For access removal or uninstall instructions, use the uninstall page. For product data handling, read the privacy notice; the separate site privacy notice covers celest.dev analytics.