A support agreement should make responsibilities clear before a fault interrupts work. The most useful document explains which systems are covered, how help is requested and what the supplier will do when an issue is reported.
Define the service in practical terms
List supported applications, environments and integrations. Set out service hours, priority definitions and response targets. A response target is the time to acknowledge or begin handling a report; it is not automatically a guaranteed resolution time.
Practical checks
- Included maintenance tasks and excluded development work.
- Customer responsibilities for accounts, access and reporting.
- Backup ownership, restoration arrangements and third-party dependencies.
- Charges, approval rules, review dates and exit arrangements.
Questions and answers
Does a monthly fee cover unlimited changes?
Only if that is explicitly agreed. Feature development, emergency work and third-party charges need clear treatment so neither party assumes they are included.
What happens when support ends?
Agree how code, documentation, account access and outstanding issues will be handed over. Business continuity should not depend on informal promises made at the end of the relationship.
Discuss your existing software
Digital Solutions can review the available system and discuss an appropriate next step. Feasibility, access requirements and the scope of any chargeable investigation are agreed before work proceeds.
Explore our software support, project rescue and modernisation services.
Book a free 15-minute software review or contact Digital Solutions.