How to contact us for CrashPlan for Small Business support
To diagnose your issue as quickly as possible, include the following information in your request:
- Product name (CrashPlan for Small Business)
- Operating system and version
- Software version of the Code42 app
- Computer ID (GUID) of affected devices
- Logs from the Code42 app
- Email address (or username) of affected user accounts
- Detailed description of the question or problem
- Screenshots of relevant settings or error messages
- Cloud backup destinations that you use (CrashPlan Central or the Code42 cloud)
We also offer the opportunity to chat directly with a technical support agent. Click the Chat now link above.
How we handle support requests
Our technical support agents actively monitor and triage incoming support requests. Tickets are addressed according to priority of the issue.
Technical support agents try to update tickets at least once every business day. Depending on the priority, responses may be made more frequently.
Support priority levels
Here is how our technical support agents determine priority when prioritizing support tickets:
|You cannot reasonably continue your work. You experience a complete loss of service and/or encounter one of the following scenarios:
You experience a severe loss of service. Operations can continue in a restricted fashion, although long-term productivity might be adversely affected and there is no temporary workaround.
You experience a minor loss of service, which results in a partial, non-critical loss of functionality of the software. The impact is an inconvenience, which may require a workaround to restore functionality.
You request information, report a documentation error, or a recommend a product improvement, but there is little to no impact on the operation of the software.
Automatic ticket closure
When a technical support agent provides a response to a submitted ticket, one of two changes occurs:
- The ticket is marked Solved if the technical support agent provides a solution to the original issue.
- After two days, the solved ticket is automatically marked as Closed. If you respond before the ticket is closed, the ticket is marked as Open for additional work with our technical support team.
- If you reply to a closed ticket, our ticketing system creates a new follow-up ticket.
- The ticket is marked Pending if the technical support agent requires additional input from you.
- After four days, the pending ticket is automatically marked as Solved, as explained above.
When a ticket is marked as Solved, you receive an automated notification email.
Customer satisfaction survey
We send a customer satisfaction survey after a support ticket is closed. We appreciate your feedback! It helps us provide more effective support.
Occasionally, you may find that a support ticket must be escalated. We understand that your data is extremely important and access can be time-sensitive. You can request a ticket escalation by:
Include your ticket number, the reason for escalation, and the priority of the issue, as well as any added contact information that will help us serve you better.
A technical support manager reviews the request as quickly and efficiently as possible, evaluates the situation, and determines an appropriate action. This may require a direct conversation with the manager, or the support ticket may be reassigned to another technical support agent.
You must use the most recent version of the Code42 app. Code42 upgrades your Code42 apps automatically. For more information, refer to Code42's supported version policy for CrashPlan for Small Business.
Use the identified support methods for requesting services and clearly explain the nature of the issue or request for help. When our technical support agents need you to assist in order to resolve the problem or complete your request, be available at the agreed-upon time.
File a bug
If you discover a behavior that may be a software bug, submit a support ticket to our technical support team. Include the steps taken to replicate the unexpected behavior.
If we identify the behavior as a bug, we will file an internal report. The resolution of the bug will depend on its severity and scope, as well as the current state of our development cycle.