Discuss ongoing support, maintenance and version update needs according to your POS project and operating context
Understand how support, maintenance, updates and service responsibilities may be arranged for different projects
Clarify which questions, issues and service requests are included in the agreed support arrangement
Create a clearer way to record, discuss and follow up on operational issues
Consider routine maintenance tasks and the responsibilities required to keep the system running
Discuss how future version changes may be reviewed, scheduled and handled for the project.
Separate routine support from new feature or workflow changes that may require additional project work
Make communication, maintenance, updates and related responsibilities clearer between the parties
After launch, a clear support request helps both sides understand what happened, where it occurred and what information is needed for follow-up
A service question, a maintenance task and a new feature request may affect the system in different ways. Their scope, timing and responsibilities should be discussed separately
Clear background details make it easier to discuss the issue and identify the next step
Separating support, maintenance, updates and new changes helps prevent different requests from being handled in the same way
Service items, applicable versions, fees and responsibilities can be reviewed according to the project and cooperation terms
Share your system background, current issue or planned change so we can discuss the appropriate next step