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.