OneBox Corp
Technical support rates
| Minimal | Initial | Optimal | Maximum | Individual | |
|---|---|---|---|---|---|
| Number of requests | 5-Requests | 15-Requests | 30-Requests | 50-Requests | From 5 hours per month |
| Response time per request in hours. | According to request priority | ||||
| Package storage time | 3 Months | 6 Months | 8 Months | 12 Months | Month |
| Maximum number of requests per day | Up to 3 | ІIndividually | |||
| Payment method | LiqPay | LiqPay/Bank account | Bank account | Bank account | Bank account |
| Cost | 75 $ | 180 $ | 360 $ | 600 $ | From $180/month |
Consultation format
1. System functionality analysis
- Explaining how various OneBox OS features work and how to apply them for your business.
- Advising on the best tools and modules for your business.
- Helping to choose the necessary applications from the OneBox catalog.
2. System configuration for your business
- Recommending how to configure OneBox OS for maximum efficiency.
- Consulting on workflow automation or creating new ones.
- Configuring the interface for user convenience.
3. Solving technical problems
- Quickly finding and fixing any technical errors.
- Explaining how to solve minor issues independently.
- Providing recommendations to prevent system failures.
4. Integration with other programs
- Advising on the best integrations for your business.
- Helping to set up connections with other services via API.
- Testing to ensure all integrations work smoothly.
5. System functionality improvements
- Developing custom solutions for your needs.
- Configuring automation for your business specificity.
- Helping to implement additional functions or system changes.
6. Platform performance analysis
- Consulting on improving system performance based on data.
- Providing advice on optimizing business processes.
- Providing feedback and suggestions for improving platform usage.
Ticket priorities
Priority A (Critical):
Tasks affecting key business processes or making the platform unavailable. Examples: complete system failure, inability to perform core operations, access issues.
Priority B (High):
Issues requiring quick resolution but not critically affecting business processes. Examples: module errors, incorrect data in reports.
Priority C (Medium):
Tasks related to performance improvement or additional settings requests. Examples: integration setup, process optimization.
Priority D (Low):
General questions not requiring urgent intervention. Examples: consultations, improvement suggestions.
Priority E (Very low):
Least important tasks that do not affect system operation. Examples: future feature requests, non-urgent adjustments, low-priority improvements.
