Submitting a Case
Please note there is no product registration for any Mobility product (i.e. Cyber Files (formerly Files Advanced, Access Advanced, mobilEcho, and activEcho), Files Connect (formerly Access Connect and ExtremeZ-IP), and MassTransit. This will not affect your ability to open a case with us.
You can submit cases through the following method:
You will receive an immediate automated confirmation email with a case number. Please make sure to enter your contact email into the webform carefully and check any spam email filter you may have if you do not see this automated confirmation email within a few minutes.
Priorities & Assignment
We assign each case a Severity from A through D.
||Issues causing serious disruptions or shuts down operations: Server down (crash, hang services won't start); clients unable to connect/transfer data; critical websites down, upgrade failure, data loss or corruption
||Significant disruptions to operations: Some clients unable to connect/transfer data; major performance degradation (slow but still working; major product feature not working)
||Minimal disruptions to operations: Minor product feature not working (ex. mE or MT reports cannot be exported); new workflow setup issue or new installation issue; minor performance issues
||No operational impact: Feature requests; non-technical questions (ex. Serial number issue); non-Customer related; internal Acronis related (non-production system)
Your case will be assigned to a Support Engineer with the appropriate knowledge and availability to help.
When you submit your case via web, the assigned Support Engineer will contact you as soon as possible, during normal support hours. The timeframe will depend on current caseload and urgency.
Depending on the nature of the case and the information needed to advance the investigation, the follow-up typically will proceed via email. Your Support Engineer may also suggest that you work together through remote screen sharing. After the initial response, case follow-up will depend on the nature of the next steps. In some cases, the next step may require that you perform configuration changes, reproduce the issue in a test environment when possible, or wait for another occurrence of the problem. We request your participation and cooperation while the case is being investigated. Also, we do have automated processes in place to improve efficiency. If a Support Engineer requests additional information from you (i.e. logs, screenshots, clarification), please reply at your earliest convenience. If we do not hear back within a few days, an automated email will be sent asking, "if the issue has been resolved or do you need more time to respond". After second attempt, case will automatically close and cannot be reopened. Please reply to one of the automated emails to inform us of current status and reset automatically closing process.
In some cases the Support Engineer may escalate the case to the Development team to determine whether the observed problem is a bug or to establish next steps.
In these cases, the Support Engineer will remain as your case owner and point of contact.
If the case is dependent on a bug fix or other product change, it will be escalated to the maintenance queue for further evaluation. Support, Development, Product Management, and Sales will work together to determine the priority for possible product changes. Your Sales team representative is your point of contact for all questions about the product roadmap, including possible future releases. In the event a change is implemented, our QA team will verify that the change works and that it does not introduce unintended side effects. It will then be made available to all customers on maintenance, or initially to a subset if the change is isolated.