Looking for help? We recommend exploring our online support documentation, which offers free technical articles for CrashPlan for Home, CrashPlan PRO, CrashPlan PROe, and SharePlan. If you have questions that are not answered in the documentation, our Customer Champions are ready to assist you!
Use our online form to submit a support request 24 hours a day. You can submit a ticket or check the status of an existing ticket via our ticketing system. To check an existing request, you must create an account.
Include the following information in your request to help our Customer Champions diagnose the issue faster:
Contact a Customer Champion by telephone if your issue is urgent. We recommend calling us if you cannot restore files, adopt, or if you have a server that is preventing multiple users from access to the functionality of CrashPlan. All calls are answered in the order in which they are received. You will be given a ticket number for referencing your specific issue for subsequent updates.
We also offer the opportunity to chat directly with a Customer Champion from the button at the bottom of our page.
Chat hours are 7 a.m. - 5 p.m. US central standard time (CST)
If your technical request cannot be answered by a Customer Champion, please visit our forums.
Our customers are really collaborative, engaging backup advocates. Many answers to questions about unsupported uses can be found there.
Include relevant log files with your initial support request to help our Customer Champions diagnose issues quickly and efficiently:
Our Customer Champions actively triage and monitor incoming support requests. Tickets are addressed according to severity of the issue. Priority is given to issues that require support for restores and getting backups actively working again.
We try to update tickets at least once every business day. Depending on the severity, responses may be made more frequently.
Here is how our Customer Champions determine severity when prioritizing support tickets:
When a Customer Champion provides a response to a submitted ticket, one of two things occurs:
When a ticket is marked as "Closed", the requester receives an automated email indicating as such. A Customer Satisfaction Survey will follow.
We send a customer satisfaction survey after a support ticket is closed. We appreciate your feedback! It really helps us provide more effective support.
Occasionally, you may find that a support ticket requires escalated. We understand backing up and restoring your data is extremely important and sometimes time sensitive. Here are the ways you can request ticket escalation:
Include your ticket number, the reason for escalation, the severity of the issue as well as any added contact information that will help us serve you better.
When a Customer Champion manager receives an escalation request, they review the request, evaluate the situation, and determine an appropriate action.
This may require a direct conversation with the manager, or the support ticket may be reassigned to a Customer Champion with greater expertise regarding your particular issue. Escalations are reviewed as quickly and efficiently as possible.
Code42 supports the two most current major software versions. A major release is indicated by a change to the first number in our software versions (for example, 3.x.x). This was revised from our previous method that used release dates for the version number (for example, 3.8.2010). For more information, refer to Code42's Product Lifecycle Policy.
Customers must ensure they use the identified support methods for requesting services and that they clearly explain the nature of the issue or request for help. When customers are required to assist with the resolution of their problem or the finalization of their request, they should be available at the agreed upon time.
If you discover a behavior that may be a software bug, please submit a support ticket with our Customer Champion team. Include the steps taken to replicate the unexpected behavior. A Customer Champion will determine if the behavior is a bug, feature request, or configuration change on the user's end. If we deem the behavior as a bug, we will file a report on behalf of the customer. The resolution of the bug will depend on the severity, current state of our development cycle, and scope of impact on our deployment.