Bitrix24 Integration with Omnidesk
Support works in Omnidesk, sales—in Bitrix24. When a customer writes to support, the agent doesn't see deal history. When a manager calls the customer, they don't know that customer wrote an angry complaint yesterday. Two systems, two contexts, zero connection—and customer feels like talking to two different companies.
Integration unifies the data: tickets from Omnidesk display in CRM, and information about the customer from CRM is available to support agents.
What Gets Transmitted
| Data | Omnidesk → Bitrix24 | Bitrix24 → Omnidesk |
|---|---|---|
| Tickets | Create task in CRM timeline | — |
| Ticket statuses | Update activity | — |
| Correspondence | Comments in timeline | — |
| Contact data | — | Name, phone, company, manager |
| Deals | — | List of active customer deals |
| Tags and priorities | Transmitted as activity fields | — |
Integration Architecture
Omnidesk supports REST API and webhooks. Scheme:
- Webhook from Omnidesk — triggers when ticket is created, status changes, new message arrives.
- Middleware — receives event, identifies customer by email/phone in CRM.
- Record in Bitrix24 — create or update activity in contact timeline.
- Reverse channel — middleware returns CRM data to Omnidesk on agent request.
Binding Tickets to CRM Contacts
When ticket is created in Omnidesk, middleware executes:
- Extract customer email from ticket.
- Search for contact in Bitrix24 by email (method
crm.contact.listwith filter). - If contact found — create task of type "support request" with data: ticket number, subject, channel (email/chat/messenger), priority.
- If not found — create lead or contact (configurable).
- Bind to open deal of contact, if exists.
Result: manager in CRM sees all customer support requests right in the card.
Multi-channel Support
Omnidesk receives requests from different channels: email, website widget, Telegram, VK, Facebook, Instagram. All channels converge into one ticket. Integration sends channel info to CRM—manager sees where customer contacted from.
If customer wrote from Telegram, then replied via email—it's one ticket in Omnidesk and one activity in CRM. No duplication.
Status Synchronization
Ticket lifecycle is reflected in CRM:
- Opened — task created, status "In work".
- Awaiting — waiting for customer reply, status updated.
- Resolved — task closed, mark in timeline with date and resolution time.
- Reopened — task active again, manager sees problem returned.
Tags from Omnidesk (e.g., "bug", "billing", "cancellation") are transmitted as task categories. This allows filtering and analyzing requests in CRM.
Agent Assignment
Omnidesk distributes tickets among agents by rules: by department, by load, by topic. Integration transmits to CRM the name of agent responsible for the ticket. Manager knows who to contact for details.
Reverse logic: if customer in CRM is assigned to specific manager, this info is transmitted to Omnidesk. Support agent sees who manages the customer and, if needed, includes them in correspondence.
Context for Agents
A widget with CRM data is added to customer card in Omnidesk:
- Company — name and industry.
- Plan / product — what customer uses.
- Deal amount — total customer value.
- Current deal stage — if negotiations or onboarding.
- Manager — name and contact.
Agent makes decisions with context. Customer signing major contract gets priority. Customer with overdue payment—redirected to manager.
Request Analytics in CRM
Omnidesk data enriches CRM analytics:
- Number of requests per customer — custom field, updates automatically.
- Average resolution time — to assess support quality per customer.
- Request frequency — rising trend may signal product issue or churn risk.
- Request topics — based on tags. If customer wrote 5 times about billing—that's a signal.
Manager sees summary in CRM without need to enter Omnidesk.
Automatic Scenarios
Based on Omnidesk events, Bitrix24 business processes launch:
- Negative ticket (tag "complaint" or low CSAT) — task to manager: "Contact customer".
- Ticket from VIP customer — notification to manager.
- Ticket not closed for 72 hours — escalation through CRM.
- New ticket during active deal — notification to deal manager.
Error Handling
- Contact not found in CRM — lead created with data from ticket. Log for manual check.
- Duplicate webhook — deduplication by ticket ID and timestamp.
- Omnidesk API unavailable — request queue with retry. Data not lost.
- Email mismatch — if customer writes from new address not linked to CRM, new activity created with "contact not identified" mark.
Security
Omnidesk webhooks are verified by signature (HMAC). API tokens stored on middleware server. Transmission—HTTPS. Logs with personal data rotated every 90 days.
We configure integration for your specific processes: from basic ticket transmission to CRM through complete linkage with agent context, analytics, and automatic escalations.