Support SLA / Contact emails β
Ridy comes with a tiered support model based on your license type and upgrade plan. This section explains what to expect, how to reach us, and what falls within (and outside) the scope of support.
π οΈ Support Tiers & Response Times β
| Plan | Includes | Response Time | Channel Access |
|---|---|---|---|
| Regular License (Basic) | Installation support for unmodified code only | Up to 2 working days | Customer panel (ticket only) |
| Pro Plan | One-time installation & branding on buyerβs server | Installation only (done in 2β3 weeks) | Customer panel |
| Pro Plus | Priority support, update maintenance, Slack/Telegram access | < 8 hours on weekdays | Ticket + Direct Messaging |
β° Support hours:
MondayβFriday, 10:00 β 18:00 (GMT+0)
Weekend on-call for production incidents only (Pro Plus)
π« Contact Methods β
| Purpose | Contact Method |
|---|---|
| Sales / Pre-purchase inquiries | π§ Email: contact@lumeagency.io |
| Technical Support | π οΈ Customer Panel β Support Ticket Submission (for license holders) |
| Pro Plus Direct Support | π¬ Telegram / Slack (via invitation after onboarding) |
β Please do not submit support requests via email. All technical support must go through the customer panel.
π Support Scope by Plan β
| Task / Topic | Regular | Pro Plan | Pro Plus |
|---|---|---|---|
| Installation (Default Docker Stack) | β | β | β |
| Admin panel setup wizard help | β | β | β |
| Bug reporting | β | β | β |
| Flutter app branding & splash | β | β | β |
| Flutter app publishing | β | β | β |
| Ongoing version updates | β | β | β |
| Direct chat support | β | β | β |
| Help with custom builds | β | β | β |
| 3rd-party plugin integration | β | β | β |
| DevOps or CI/CD pipeline setup | β | β | β |
π§ Support is only provided for the original, unmodified version of the product.
Modifications, custom logic, or unsupported 3rd-party integrations fall outside all support plans.
π§Ύ Best Practices for Support Requests β
To ensure the fastest resolution, your support ticket should include:
- Your purchase code
- Server IP and credentials (optional, but recommended)
- Description of issue with screenshots or logs
- Target platform or app affected
π Once your issue is resolved, you are encouraged to change any shared credentials
