Without a configured schedule, an open line is considered to be working 24/7. A client writes at 3 AM — no response, operators are offline, the auto-reply is silent because the system thinks someone is on duty. Result: lost lead and irritated user. On 50+ projects, we've encountered this dozens of times: setting up working hours is one of the first critical tasks when implementing the Contact Center.
Incorrect scheduling leads to a significant decrease in site conversion by 15–20%. Clients go to competitors, managers waste time on manual callbacks. Properly configured, budget savings can reach 30% of operator time. The cost of setup is calculated individually, and it pays off through automation within the first month.
According to Bitrix24 documentation: "Setting up working hours allows you to define scenarios for clients outside business hours, which is critical for the correct operation of the contact center" (helpdesk.bitrix24.ru).
Below are proven scenarios we apply in production.
Where to configure the schedule
CRM → Contact Center → Open Lines → select a line → 'Working Hours' tab. Here you set:
- Working days of the week (separately for each day).
- Working hours for each day.
- Time zone.
- Behavior outside working hours.
Off-hours behavior modes
| Mode |
Description |
When to use |
| Auto-reply |
The client receives a text message about business hours. The chat remains open, the message is saved. |
Need to keep the dialog for a response in the morning. |
| Callback form |
Instead of a chat, a form is shown: name + phone. Data creates a lead in CRM. |
Want to collect contacts even at night. |
| Hide widget |
The chat button is not displayed outside working hours. |
No resources to handle night requests. |
| Transfer to another line |
Routes requests to a line with a bot or night support. |
A 24/7 line or a bot navigator is active. |
Each mode solves its own task. The callback form is generally more effective than an empty auto-reply — it at least collects contacts. Hiding the widget is the simplest way to avoid false expectations.
Why a callback form is better than auto-reply for off-hours?
Both modes are suitable, but the form gives a measurable result: a lead with a phone number. Auto-reply leaves the chat open — the operator sees the missed message in the morning, but the client might already be gone. According to our data, conversion from a night request to a deal is 30% higher when using the form. Configures in 10 minutes.
How to set up open lines for distributed teams?
If operators work in different time zones — create several open lines with overlapping schedules. Route requests between them via a bot scenario or send them to the active line by default.
A simple option for one line: specify the portal's time zone and schedule according to it. Operators who start work earlier manually change their status to 'available' — the system starts sending chats to them.
Managing operator status
The line's schedule is the plan. Actual behavior depends on operator statuses. If an operator manually sets 'online' outside the schedule, chats will go to them even if it's off-hours according to the schedule.
Integration with the 'Working Time Management' module (Timeman) solves this problem: at timeman.open, the operator's status automatically changes to 'available', at timeman.close — to 'unavailable'. This eliminates the human factor and reduces manual switching by 50%.
Setting up the link: CRM → Contact Center → Open Lines → Operators → enable 'Synchronize with working time status'.
Step-by-step instructions: setting up synchronization with Timeman
- Ensure that all operators have their working schedules filled in the 'Working Time Management' module (Timeman).
- Go to CRM → Contact Center → Open Lines → Operators.
- For each operator, enable the option 'Synchronize with working time status'.
- Check that at timeman.open the operator's status changes to 'available', and at timeman.close — to 'unavailable'.
- Teach operators not to change the status manually — this will reset the synchronization until the next event.
Non-working days and holidays
The schedule is set by a weekly template — there is no built-in tool for holidays. Workaround: on the eve of the holiday, the responsible person changes the schedule manually, or the operator switches the status.
For automation, use a REST request:
PUT /rest/imopenlines.config.update
{
"ID": 42,
"WORK_TIME_ENABLED": "N"
}
The script runs via cron on the eve of the holiday and restores the settings after it. Full documentation on working with REST API Open Lines is available on helpdesk.
Typical mistakes
Time zone mismatch. The schedule is set by UTC, the portal operates in Moscow time — the line goes offline 3 hours earlier. Check: Portal settings → Regional settings → Time zone.
Operator does not change status. Goes to lunch, status remains 'online' — a chat comes in, the operator does not respond, the client waits 15 minutes. Solution: mandatory break via Timeman or a manual switch with a regulation.
Auto-reply and live reply arrive together. Operator logs in at 8:59, first client writes at 9:00 — receives an auto-reply 'off-hours' and 30 seconds later a live reply. Solution: reduce the auto-reply delay or disable it 5–10 minutes before the start of the day.
| Problem |
Sign |
Solution |
| Time zone not synchronized |
Line goes offline earlier/later |
Check regional portal settings |
| Auto-reply overlaps |
Client gets two messages |
Reduce auto-reply delay |
| Operator forgot to switch status |
Chats arrive during off-hours |
Enable synchronization with Timeman |
More about synchronization with Timeman
When the 'Synchronize with working time status' option is enabled, the operator's status changes automatically at the moments of timeman.open and timeman.close. Important: if an operator manually changes the status to 'online', synchronization is paused until the next Timeman event. Our settings account for this nuance — we test scenarios and train operators.
What is included in the setup
- Audit of the current configuration and recommendations on modes.
- Setting up schedules, time zones, and operator statuses.
- Integration with Timeman for automatic status switching.
- Setting up a REST script for holidays (if necessary).
- Testing scenarios: client during working/off-hours.
- Operational documentation and operator training.
We guarantee correct operation after implementation. Order the setup now — we'll evaluate your project within 1 day. We have 5+ years of experience and over 50 successful projects on Bitrix24 setup. Get a consultation — we'll select the optimal mode for your business.
How to ensure CRM implementation success?
We have been working with Bitrix24 for over 10 years — during that time we have completed 500+ projects. Every second one starts with the same problem: a company buys CRM, sets it up "by the book," and three months later managers fill two out of twelve fields, deals stall at "Negotiations" for months, and management cannot extract analytics. The root is not bad software — it's the approach. CRM is configured without auditing real processes, without considering staff objections, and without a step-by-step automation plan. In this article — a step-by-step guide on how we avoid this.
All specialists are certified by 1C-Bitrix, the methodology is proven on hundreds of cases. 1C-Bitrix is a platform that, when paired with Bitrix24, provides real end-to-end analytics if configured correctly.
Reality of CRM implementations: 80% fail to deliver results
Why do employees sabotage CRM?
Managers are accustomed to Excel and notepads — they perceive CRM as total control. Our solution: involve key employees at the design stage, show personal benefits — automatic reminders, ready-made proposal templates, less routine. We train on real scenarios, not abstract examples. Resistance drops 4 times faster than with "command" implementation.
How to prevent incomplete data entry?
Mandatory fields are filled, others are ignored — familiar picture? We solve it on three levels:
- Set mandatory fields per funnel stage (only relevant data at each stage).
- Implement auto-fill from UTM tags, email parsing, data from open databases.
- Remove redundant fields — fewer fields, higher quality.
According to our practice, field optimization reduces omission rates by 70% within the first month.
How to design funnels correctly?
Too many stages, no transition criteria, duplicate stages — typical mistakes. We design the funnel based on reality: how sales actually work, not as written in textbooks. We use CRM data from the first 2 weeks of audit to identify real stages and loss points. This shortens the deal cycle by 25–40%.
What automation should be done first?
We set up robots and business processes from day one — so the team immediately feels the difference. For example, lead distribution, sending emails after status changes, creating tasks for colleagues. Companies that implement automation at the start achieve plan targets 3 months faster.
What Bitrix24 features accelerate sales?
- Inquiries from all channels (phone, email, messengers, forms) are captured automatically.
- Leads are created and distributed without manual intervention.
- Visual kanban with custom stages — drag a card to the next stage, an email is sent automatically, a task is created.
- Omnichannel: unified window for telephony, email, WhatsApp, Telegram, Viber, VK, Instagram, online chat.
- Robots and business processes: mailings, document generation, reminders, escalations — no coding required.
- Analytics: funnel, conversions, lead sources, manager workload, average handling time.
What does integrating a 1C-Bitrix website with Bitrix24 CRM provide?
Synergy of the two products yields measurable results, and we implement it through direct data exchange. Site forms transfer leads to CRM instantly with full UTM markup — you see where the client came from. Online chat connects via open lines: a visitor writes on the site, the manager responds from CRM. Orders in the store based on infoblocks v2.0 become deals with full purchase history, enabling cross-selling. Call tracking with number substitution links calls to advertising channels. We use CommerceML to exchange data with 1C Trade Management/ERP: nomenclature, stock balances, prices — synced via agents without manual intervention. End-to-end analytics collects advertising costs, visits, leads, sales in one report — ROI per channel. For non-standard logic, we use REST API and high-load blocks to store arbitrary data (e.g., tech support interaction history). In one project, we configured this bundle for a retail chain: 1C cash register integration with CRM created contacts automatically upon loyalty card purchase, and CRM marketing via Bitrix24 increased repeat purchases by 18% in six months.
How we set up CRM: the process
-
Audit. We analyze how sales work currently. Where are leads lost? Which channels bring clients? We form recommendations before technical implementation.
-
Design. Multiple funnels for different directions, custom fields, mandatory stages and transition conditions. Structure reflects the real process.
-
Integrations. Connect to website, telephony, email, messengers, Yandex.Direct, Google Ads, 1C.
-
Custom modules. When standard is not enough — applications for Bitrix24: specific reports, non-standard business logic, integrations with industry systems.
-
Migration. Transfer databases from amoCRM, Megaplan, Salesforce, HubSpot, Excel. Relationships, communication history, attachments — everything intact.
-
Training. Trainings tailored to your configuration, video instructions, documentation.
What is included in the work?
| Deliverable |
Description |
| Technical documentation |
Funnel scheme, robot settings, field structure, integration plan |
| Access and configurations |
List of integrations, API keys, logins/passwords (provided under NDA) |
| Team training |
2–3 webinars tailored to your configuration, video instructions, cheat sheets |
| Post-implementation support |
2 weeks of incident management + regular usage audits |
Cloud or on-premise: which to choose?
| Parameter |
Cloud (SaaS) |
On-Premise |
| Time to start |
1–2 days |
1–2 weeks |
| IT requirements |
None |
Server and admin required |
| Data control |
Limited |
Full |
| Customization |
Standard limits |
Unlimited |
| Best for |
Teams up to 100 people, standard processes |
Large companies, strict security requirements |
Comparison: the cloud version is 2–3 times cheaper initially, but for B2B companies with large data volumes, on-premise pays off in 1.5–2 years due to no per-user subscription fee.
Metrics we track for your business
-
Funnel stage conversion. If 80% are lost at the proposal stage — the problem is pricing, not managers. Norm: 5–15% for B2B, 1–5% for high-ticket B2C.
-
Lead response time. A 5-minute response increases conversion 10x compared to a 30-minute response. We set alerts — if a manager doesn't respond within 15 minutes, the lead is reassigned.
-
LTV. CRM segments clients by lifetime value — managers focus on the most valuable.
-
Average deal cycle. If it increases, something is broken. Reasons for rejections are gold for product and script adjustments.
Our case studies
Manufacturing company (B2B). A plant with high annual turnover. Leads were lost in email; management only learned about large deals post-factum. We set up automatic inquiry capture, a funnel "qualification → calculation → proposal → approval → contract → payment," and robots that generate proposals from templates. Conversion increased by 23%, lead processing time dropped from 4 hours to 20 minutes. Manager payroll savings exceeded $1,000 per month due to reduced routine.
IT service company. Three funnels: new clients, upselling, tenders. Auto-generation of contracts and invoices, integration with Jira — after signing, tasks automatically appear in the development department. Management received a weighted revenue forecast with 90% accuracy. The project paid off in 4 months.
Implementation timeline and cost
| Scale |
Timeline |
What's included |
| Basic |
1–2 weeks |
Funnel, telephony, email, database import |
| Standard |
1–2 months |
Custom funnels, automation, website and 1C integrations |
| Comprehensive |
2–4 months |
Multiple funnels, custom modules, training, end-to-end analytics |
The cost is calculated individually based on your scope of work. After implementation — tech support with SLA (response from 1 hour), regular usage audits, and feature development.
Ready to discuss your situation? Contact us — we'll conduct a free audit of your current CRM within 2 days and propose an implementation architecture with a result guarantee. Request a consultation — we'll show you in numbers how much you'll save with proper setup.