01
Implementation readiness
Confirm scope, roles, infrastructure, migration inputs, integrations and the people responsible for decisions.
Zylvoo support can cover implementation readiness, training, go-live assistance, issue handling and planned improvements according to the selected product and service arrangement.
Support journey
Preparation, testing and user ownership reduce avoidable go-live problems and create a stronger foundation for ongoing support.
Confirm scope, roles, infrastructure, migration inputs, integrations and the people responsible for decisions.
Validate representative workflows, permissions, reports and exception cases before the agreed go-live step.
Train administrators and end users around the tasks they actually perform instead of presenting every system feature.
Coordinate cutover, data checks, initial issue handling and escalation responsibilities according to the implementation plan.
Handle agreed software issues, updates and technical assistance through the configured support channels and service scope.
Separate new requirements from defects, assess impact and schedule enhancements through a controlled change process.
Support arrangements
Specific response times, channels, exclusions and service levels are defined in the applicable proposal or support agreement. No universal response-time promise is made on this page.
For new deployments requiring configuration, migration preparation, testing, training and go-live coordination.
For agreed issue handling, updates and technical continuity after the implementation period.
For new reports, workflow changes, integrations or custom functionality that require assessment and separate scope.
Existing clients can use the configured application login and, when enabled, the external support portal managed through centralized URL settings.
Implementation path
Discovery, solution design, testing, training and ongoing support are connected stages rather than separate promises.
Understand the business, current tools, users, priorities and operational challenges.
Map the recommended system, workflows, integrations, controls and reporting approach.
Confirm included modules, responsibilities, assumptions, exclusions and delivery priorities.
Configure approved capabilities or build the agreed custom features and integrations.
Prepare, validate and transfer suitable data using the agreed migration plan.
Verify functionality, permissions, workflows, reports and user acceptance against scope.
Train relevant users, complete readiness checks and move the approved system into use.
Provide agreed maintenance, issue handling and future improvement planning after launch.
Support FAQs
Final support terms depend on the selected product, deployment and signed service arrangement.
Implementation and post-launch support scope is defined in the relevant proposal or agreement. Different products and deployment models may require different arrangements.
Training can be planned for administrators and user groups according to their responsibilities, selected modules and rollout plan.
Use the configured client support channel or contact Zylvoo with the affected module, user, time, steps and any safe screenshots needed to understand the issue.
A defect in agreed functionality and a new requirement are different. New reports, integrations or workflow changes normally require impact assessment and separate approval.
Remote and on-site assistance can be assessed according to location, project needs, access requirements and the agreed service arrangement.
Business hours and escalation details will be displayed from Super Admin settings after they are verified. Empty or unverified hours are not published.
Only when those responsibilities are included in the hosting or support scope. On-premise and customer-managed infrastructure may assign backup and server duties to the customer.
Get the right support path
Use the relevant contact path and provide enough context for Zylvoo to identify the product, environment and next practical step.