Support begins with classification
A request may be deployment assistance, maintenance, access review, governance clarification, or third-party dependency review.
Digitalith support is built around clear intake, approved systems, documented responsibility, and realistic review paths. It is not open-ended operational responsibility.
This guidance supports scoped deployment decisions. It defines responsibility, readiness, and support conditions without implying operational coverage beyond agreed work.
These points are written from the way Digitalith approaches deployment work: define the system, protect the handover, reduce operational ambiguity, and keep support tied to real responsibility.
A request may be deployment assistance, maintenance, access review, governance clarification, or third-party dependency review.
Screenshots, URLs, error messages, recent changes, and access status help clarify what can be reviewed.
Support depends on whether the affected item is within approved scope, client-managed, or controlled by a third party.
Requests should move to the right review path instead of being treated as one undefined support bucket.
The support structure protects both the client and Digitalith by keeping assistance tied to real scope, access, complexity, and dependency conditions.
For issues connected to a delivered or stabilizing deployment.
For controlled updates, approved adjustments, or reviewable improvements.
For questions about access, ownership, change responsibility, or operational boundaries.
Request a scoped review to identify readiness gaps, ownership concerns, dependency risks, and practical next steps.