You published an application in the Bitrix24 Marketplace. A month later — first complaints: users see blank tabs, some can't log in. Without a support system, the app rating drops due to negative reviews. Every minute of downtime loses trust and revenue. Proactive support is not a luxury but a necessity for any published solution.
Even if the app is perfectly written, reality is: tokens expire, REST API becomes outdated, and users' portal configurations break logic. Only systematic monitoring and quick response save the rating. We have seen projects where one outdated API property disabled functionality for 30% of installations.
Why tokens are the main support issue?
refresh_token lives 180 days. If a user hasn't opened the app for six months — token expired, re-authorization is impossible without manual intervention (reinstall or forced re-auth). Monitoring tokens by expires_at and proactive notification is needed. We set up a system that sends a notification 30 days before expiration or automatically renews the token via a refresh request. With automatic renewal, error probability is reduced by 3 times compared to manual notification.
How to adapt to Bitrix24 REST API changes?
1C-Bitrix periodically deprecates methods. A deprecated warning appears in the documentation a few months before, but the removal can be abrupt. Subscribing to the REST API changelog is mandatory. We include weekly changelog checking and test runs in a sandbox environment when changes are detected. Sentry allows spotting compatibility errors 5 times faster than passive log monitoring.
How much does lack of support cost?
Let's calculate: the average incident with an expired token takes 2 hours of developer work. With a typical developer hourly rate and 5 such incidents per month, losses can be significant. If the app loses users due to errors, lost profit can be many times greater. According to our data, implementing proactive monitoring reduces incidents by 70%, leading to substantial savings for an app with 1000 active installations. These funds are better spent on feature development.
What other surprises await developers?
Changing placements, non-standard portal configurations, custom user permissions — all cause errors only for some users. Without proper logging with member_id, diagnosis takes hours. We use Sentry with grouping by member_id and error type, and alert when error threshold is exceeded within 15 minutes. This reduces average diagnosis time from 4 hours to 30 minutes.
| Scenario | Without Support | With Support |
|---|---|---|
| Token expiration | User complaints, manual recovery | Automatic renewal 30 days before |
| REST API change | App breaks, urgent fix | Smooth migration 2 weeks before deadline |
| Single portal error | Week of diagnosis | 30 minutes via member_id logs |
How we organize support
Minimum set for supporting a published application:
- Error monitoring — Sentry or equivalent with grouping by
member_idand error type. Alert when error threshold exceeded within 15 minutes. - API call logging — all calls to Bitrix24 REST with response code, execution time,
member_id. - Failed tasks queue — tasks with error status displayed in support dashboard with retry capability.
- Communication channel — email, site form, or chat, with SLA: response within 24 hours, critical incidents within 4 hours (during business hours — within 2 hours).
Each ticket includes the portal member_id — linking the ticket to specific logs and tokens.
Example SLA structure
Critical incidents — response within 2 hours, resolution within 4 business hours. Regular requests — response within 24 hours, resolution within 3 business days. Weekly app status report and Bitrix24 changelog monitoring.Process steps
| Stage | Duration | Result |
|---|---|---|
| Analysis | 2-3 days | Monitoring and logging dashboards |
| Design | 1-2 days | SLA, communication channels, escalation procedures |
| Implementation | 3-5 days | Sentry integration, automatic token renewal |
| Testing | 1-2 days | Test on portal, failure simulation |
| Deployment | 1 day | Production launch, documentation handover |
What you get
- Documentation on support procedures and contacts.
- Access to monitoring and logging systems.
- Training for your team (2 hours).
- Regular app status reports.
Timeline and conditions
Setting up support takes 1 to 2 weeks depending on app complexity. The cost is calculated individually based on user count and required SLA. Contact us for a project evaluation.
Our team has over 500 projects on Bitrix24. We guarantee SLA and transparent reporting. Order technical support — we'll set up monitoring and processes in 1-2 weeks. Get a consultation right now to keep your app stable.