We configure callback so that the client receives a call in 60 seconds, not in 60 minutes.
The standard Bitrix24 widget handles basic tasks, but when you need a callback from Telegram chat, an automatic callback after a missed call, or integration with call tracking — you cannot do without a custom REST API. Let's look at how this works in practice.
Often clients lose up to 30% of leads because the manager calls back an hour later, when interest has already faded. Callback solves this problem: the request is processed within seconds, and the client receives a call within a minute.
We have implemented such a scheme for more than 50 projects, including online stores with a load of 1000 requests per day. Setting up callback in Bitrix24 is not just a widget on the website.
It is a whole ecosystem: integration with telephony, CRM robots, REST API for non-standard scenarios. Lead loss due to slow response can cost a business an amount calculated after an audit on a monthly basis, and a properly configured callback pays for itself in 2-3 months. Get a consultation on callback setup — we will offer the optimal solution.
Problems we solve
Response delay — every minute of downtime reduces conversion by up to 30%. Callback in Bitrix24 eliminates this factor: the call is initiated automatically immediately after the form is submitted.
Non-standard scenarios — for example, callback from a chat in Telegram or Viber via an external API.
Or integration with call tracking: a client visited the website, did not leave a request, but has not called for a long time — the robot creates a callback task for their number with a specific scenario.
Missed calls — the most common lead loss: a client calls, cannot get through, and never returns. Automatic callback in 5 minutes with three attempts solves this problem.
Callback setup process
We use a combination of built-in Bitrix24 tools and REST API. For a typical website, it is enough to configure the "Callback" widget:
- Select a queue of managers
- Set working hours and delay before the call
- Configure the greeting text
For complex scenarios — we write scripts via telephony.externalcall.originate. Example: initiate a call immediately without waiting for confirmation:
POST /rest/telephony.externalcall.originate { "USER_ID": 15, "TO": "+74951234567", "LINE_NUMBER": "100" } We also integrate callback with 1C and CRM systems via CommerceML, synchronizing call statuses and orders.
Benefits of professional setup
A mistake in call routing or incorrect queue setup leads to the client either not waiting for the call or the call going to the wrong manager.
The team's experience allows us to avoid these problems: we have configured callback for more than 50 projects, including online stores with high load (up to 1000 requests per day). We guarantee stable operation 24/7.
Our clients reduce monthly costs on repeat calls and advertising by an amount calculated after an audit. Contact us — we will tune callback specifically for your business.
How to automate a callback after a missed call?
We create a CRM robot: on a missed call (lead), after 5 minutes we initiate a callback via REST API. We set up up to 3 attempts with a 30-minute interval. This approach increases lead return by 40% and provides savings of up to 30% of the budget.
How to use REST API for non-standard scenarios?
Use REST API. The methods telephony.externalcall.show and telephony.externalcall.originate allow you to flexibly integrate callback into non-standard forms, mobile applications, or chats. We connect callback to any channels — from web forms to messengers.
The solution pays for itself within 2-3 months. Implementing callback brings additional profit calculated after an audit for large projects.
Configuration of CRM robots
For automatic callback after a missed call, create a robot in the section CRM → Settings → Robots. Select the event "Missed call", add the action "Execute REST API" with the method telephony.externalcall.originate.
Parameters: user ID, phone number from the lead, and line. Set up to 3 attempts with a 30-minute interval.
Comparison of callback approaches
| Method | Complexity | Setup time | Flexibility |
|---|---|---|---|
| Built-in widget | Low | 1-2 hours | Limited |
| REST API + custom script | Medium | 4-6 hours | High |
| Automation for missed calls | High | 6-8 hours | Maximum |
Each method is better than the previous one under certain conditions — we choose based on the task.
Typical mistakes and their solutions
| Mistake | Consequence | Solution |
|---|---|---|
| Working hours not specified | Calls outside working hours are not processed | Specify working hours in the widget settings |
| Queue not configured | The call may not reach a free manager | Configure the queue taking workload into account |
| Missed callback without retries | Lead loss | Add up to 3 retries with a 30-minute interval |
What our work includes
- Audit of current telephony and CRM. We will check line settings, queues, and integration with 1C.
- Designing the callback scheme. We choose the optimal method: widget, API, or combo.
- Implementation. Configuring the widget, writing scripts, creating CRM robots.
- Testing. We check scenarios: successful call, busy, no answer, retry.
- Documentation and training. We provide instructions for managers and set up monitoring.
- Support. We guarantee stable operation and, if necessary, adjust the logic.
Approximate timelines
- Typical callback via widget — 2-3 hours.
- Custom scenario with REST API and robots — from 4 to 8 hours.
- Comprehensive automation (including integration with telephony and 1C) — up to 2 days.
Cost is calculated individually — evaluate the project, and we will offer a solution for your budget. Order callback setup and increase conversion today.