Arian Software Studio
Customer portal

Software maintenance and support

After launch, software needs regular attention and a clear way to report issues. We define support around the system’s condition, available access and each party’s responsibilities so requests can be tracked.

Choose features and estimate cost
Software maintenance and support

Support scope and issue handling

Covered systems and modules, contact hours, incident priorities and initial response targets are specified in the agreement. An initial response is different from a resolution time. The approach and estimated completion time follow diagnosis.

Maintenance, backups and changes

Hosting, domains, certificates, backups and recovery responsibilities must be clear. If backups or recovery tests are included, their frequency and scope are recorded. New features, major changes and bulk data correction require a separate scope and estimate.

Deliverables to agree on

  • Initial assessment and agreed service scope
  • A request logging and tracking channel
  • Records of actions and changes
  • Defined infrastructure, access and backup responsibilities

Frequently asked questions

Can you support a system built by another team?

We first review technology, code condition, licences and access. Acceptance and support scope are determined after that review.

Does submitting a ticket mean immediate resolution?

A ticket starts the handling process. Priority and initial response targets follow the agreement. Resolution time is estimated after diagnosis.

Are content updates and development included?

Publishing prepared content or making minor changes is included only when selected with an agreed allowance. New features are estimated separately.