This document outlines the scope of support provided by Appbrew
Development and production issues.
Informational and implementation questions about the product and its features.
Troubleshooting operational problems.
Email: support@appbrew.tech
For enterprise customers: Slack
Priority Code | Definition | Example | Issue Resolution Time |
Blocker (P1) | Any functional issue that is blocking the user from placing an order on the app. | - User not able to view products - User not able to add to the cart - Checkout not opening - Search not working | A workaround or permanent fix within 24 hours. Permanent fix within the next 48 hours if a workaround is provided. |
Critical (P2) | Functional issues that impact key user flows: - User login - Address management - Sorting and filtering - Wishlist - Order tracking - Returns - Using discounts - App deep linking | - Deep links not working - Push notifications not working - Unexpected behavior of discounts - User is not able to log in | Resolution may take up to 4 working days depending on complexity. |
Major (P3) | Issues related to third-party integrations and custom-developed modules with little to no meaningful business impact. Includes data discrepancies and visual issues. | - Push impressions not reflected in CRM - App design changes | Resolution can take up to 14 working days. If an app update is required, the fix will be included in the next app release following the 14-day resolution period. Note: App approval time on the App/Play Store is not included in the resolution time. |
Release | Description |
Reserved Release Days (2nd and 4th Tuesday) | - Fixes for P3 issues released on the next reserved release day. - New features may be released. |
Issue Fixing Prioritization | Fixes for P1 and P2 issues are released on a priority basis. |
Automatic Updates (every 2 months) | Automatic updates are pushed to ensure users receive the latest product enhancements. |