After activating the AI assistant in Bitrix24, many administrators face a problem: the assistant is either not used or is used inappropriately — employees ask it to write poems or jokes. We've seen this on dozens of projects. CoPilot is a built-in AI assistant based on GPT that works without external servers. But without thoughtful configuration of roles, prompts, and access rights, its potential remains untapped. Over 5+ years of implementations and 50+ projects, we have developed an approach that delivers measurable results: typical request processing time is reduced by 25–35%, and the number of clicks to create a task drops by half. Budget savings can reach 40% in recruitment by automating initial responses. Typical configuration cost ranges from $500 to $1500, depending on the number of roles and sections. Clients see ROI within 3 months through efficiency gains.
What problems does CoPilot setup solve?
The first problem is off-target usage. Employees perceive the assistant as entertainment rather than a work tool. Solution: restrict the sections where it is active and create custom personas that are automatically substituted when invoked. We configure CoPilot only in CRM and tasks for the sales department, and disable it for others. This reduces non-work requests by 40%.
The second is template responses. Without custom prompts, the assistant does not know your products, typical objections, or communication style. For example, tech support gets generic phrases that need rewriting. Solution: a prompt describing products, links to the knowledge base, and initial diagnostic algorithms. After configuration, preparation time for the first response is reduced from 15 to 5 minutes (3x faster).
The third is lack of access differentiation. All employees see the assistant in all sections, even where it's not needed. Department-level permissions solve this: for example, the warehouse does not see it in CRM, and marketing does not see it in the support chat.
How we configure CoPilot: tech stack and a case
To automate role creation, we use the REST API crm.copilot.role.add. This allows quickly deploying dozens of custom prompts for different departments. Example from our practice: one of our clients — a company with 120 employees, sales, support, and marketing departments. We created three roles:
-
Sales: prompt describes 30 products, typical objections, and communication scripts. CoPilot generates emails in CRM, taking into account client specifics.
-
Support: prompt includes links to the knowledge base, initial diagnostic checklist, and frequent errors. Operators prepare responses faster.
-
Marketing: prompt contains brand style, forbidden phrases, and target audience. CoPilot helps create feed posts.
Result: the number of requests to the second level of support decreased by 25%, and email preparation time tripled.
How to enable CoPilot and restrict access?
Activation: Settings > Tools > CoPilot. The administrator selects sections (chat, tasks, CRM, feed, documents) and enables/disables for each. Permissions are configured via groups: you can grant access only to the sales department in CRM, and prohibit the warehouse. Details — in the Bitrix24 help center.
Why custom roles work better than standard ones?
Standard roles (Marketer, Lawyer, HR) give template responses because they don't know your business. Custom ones are written for a specific company. Example: role 'Sales manager {company name}' with a prompt specifying: product list, typical objections, tone of voice, and examples of correct answers. The role is linked to a section (CRM, tasks) and an employee group. When invoking CoPilot, it automatically selects this role, and responses become relevant.
CoPilot limitations: when is custom integration needed?
CoPilot is a manual tool. It is not suitable for process automation. Main limitations:
- No access to external APIs — works only with portal data.
- No automation — cannot be triggered by robots or business processes.
- Request limits: finite on 'Standard', higher on 'Professional'.
- Fixed model — cannot change GPT to Claude.
According to Bitrix24 documentation, CoPilot is intended for manual scenarios. If you need automatic lead qualification or call transcription — use custom integration.
Comparison: CoPilot vs custom OpenAI integration
| Criterion |
CoPilot (out-of-the-box) |
Custom integration |
| Requires server |
No |
Yes |
| Automation |
No (only manual call) |
Yes (robots, business processes) |
| Access to external data |
No |
Yes (via API) |
| Model |
Fixed |
Any (GPT, Claude, Mistral) |
| Request limits |
By tariff |
Configurable |
| Setup complexity |
Low |
High |
CoPilot implements 3x faster, but custom integration provides 5x more flexibility. The choice depends on tasks.
Which roles and prompts to create?
| Role |
Example prompt |
Scope |
| Sales manager |
"Describe the client's task in the context of products {list}. Use script {script}. Tone — friendly but businesslike." |
CRM, tasks |
| Tech support |
"Answer the client using the knowledge base {link}. If the problem is {type}, suggest {solution}." |
Chat, tasks |
| Content manager |
"Create a feed post, style — {style}. Avoid {topics}. Target audience — {audience}." |
Feed, documents |
CoPilot setup checklist
- Enable CoPilot only in necessary sections (CRM, tasks).
- Restrict access by departments (e.g., only sales).
- Create at least one custom role for a key task.
- Write a prompt describing products, objections, and tone of voice.
- Assign the role to an employee group.
- Conduct training: how to invoke CoPilot, which role to choose.
- Regularly analyze requests — optimize prompts.
What is included in the CoPilot setup work?
- Audit of current processes — identify scenarios where CoPilot will bring benefit.
- Activation and section configuration — enable CoPilot only where needed.
- Access differentiation — configure permissions by departments and roles.
- Creation of custom roles — write prompts for your products, tone of voice, typical tasks.
- Employee training — conduct a demo: how to invoke CoPilot, how to select a role, how to formulate a request.
- Documentation — transfer instructions on setup and usage, including a detailed guide and troubleshooting tips.
- Post-configuration support — 1 week of assistance to fine‑tune prompts and answer questions.
Timeline: from 2 to 5 days depending on volume. Typical cost ranges from $500 to $1500, with payback within 3 months. Get a consultation on CoPilot setup for your business — we will describe a plan for your processes. Contact us to discuss details.
How a corporate portal on Bitrix24 solves the problem of information chaos?
Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.
We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).
What does the portal offer in daily work and why is it better than messengers?
In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.
Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.
Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.
Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.
HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.
Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.
Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.
How does integration with 1C and Active Directory accelerate HR management?
Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.
Types of corporate portals and key integrations
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
Additional integrations that deliver real value:
- Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
- IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
- Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
- EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.
Security and compliance with Federal Law 152‑FZ
The portal contains personal data, financial reports, strategic plans. We guarantee protection:
- role model via CGroup and section‑level permissions;
- two‑factor authentication (OTP, Yandex.Key, SMS);
- audit of all actions (b_event_log);
- TLS encryption for transmission and disk encryption;
- full compliance with Federal Law No. 152‑FZ "On Personal Data".
How is implementation carried out? Step‑by‑step plan
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- Launch — connect all employees, train, hand over documentation.
What you receive after implementation
- Project documentation: architecture, integration scheme, business process diagrams.
- Configured portal with all integrations (1C, AD, telephony, EDI).
- Business process descriptions and instructions for administrators and users.
- 30 days of technical support after launch.
- Access to our knowledge base and migration scripts.
Post‑launch support: how to prevent the portal from becoming obsolete
After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.
Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.
Order a turnkey corporate portal implementation
Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.
