🎯 Goal: Confirm (and fix) everything required before you start the Bitrix24 ↔ MyOperator integration so setup works on the first try.

📚 Table of contents

• When & why to use this
• Quick answer (copy‑paste checklist)
• Detailed checklist with examples
• How to verify each prerequisite
• What success looks like
• Edge cases & limitations
• Sample data formats
• Troubleshooting
• Security & privacy
• Escalation & support
• Next step: Start the integration
• FAQ
• Related articles
• Structured data (HowTo + FAQPage)

🧭 When & why to use this

Use this guide before you open any setup wizard or map fields. It prevents failed syncs caused by missing users, wrong numbers, or disabled APIs.

🔝 Back to top

✅ Quick answer (copy‑paste checklist)

Paste into your team chat and check off:

[ ] Bitrix24 admin access is active[ ] MyOperator admin access is active[ ] In Bitrix24, Contacts/Leads have a Phone field for customer numbers (mobile preferred)[ ] In Bitrix24, each calling agent exists as a user with a unique phone number or email[ ] In MyOperator, After‑Call / In‑Call API/Webhook features are enabled on our plan[ ] MyOperator IVR / DID details are known (IVR ID or DID list)[ ] Decide primary identity key: Phone (recommended) or Email; confirm the same is available in both systems[ ] Test phone numbers prepared (one customer, one agent)

🔝 Back to top

🧩 Detailed checklist with examples

💡 Tip: If you serve multiple countries, normalize numbers to E.164 (e.g., +919876543210) in both systems.

🔝 Back to top

🪜 How to verify each prerequisite

1) Confirm admin access

• Bitrix24: Sign in → open Settings → Users (ensure you can add users).
• MyOperator: Sign in → Manage → API Integration is visible.

2) Check customer Phone field

• Open a sample Contact/Lead → ensure a Phone field exists and is populated.
• If regional rules apply, store either local 10‑digit or E.164 consistently.

3) Verify agent records

• In Bitrix24, confirm every calling agent exists as a user with a unique phone or email.
• Remove duplicates; set the correct owner/department if you’ll route by queues.

4) Confirm MyOperator features

• In MyOperator, check your plan includes After‑Call / In‑Call API/Webhooks.
• If missing, contact your account team to enable.

5) Gather routing assets

• Note your IVR ID/DID list in MyOperator.
• You’ll use these to filter which calls sync to Bitrix24.

6) Prepare test data

• Customer number and agent number ready; place a quick connected test call after setup.

🔝 Back to top

✅ What success looks like

• You can list all required items above without gaps.
• A test contact in Bitrix24 has a valid Phone.
• Each agent appears in Bitrix24 Users with a unique phone/email.
• API/Webhook features are present in MyOperator.
• IVR/DID identifiers are noted.
• You’re ready to follow the integration how‑to without guessing.

🔝 Back to top

⚖️ Edge cases & limitations

• Mismatched formats: +919876543210 vs 9876543210 can break matching; choose one global format.
• Shared numbers: If two Bitrix24 users share a phone, ownership mapping may fail.
• Inactive users: Calls may map to “unassigned” if agents are deactivated in Bitrix24.
• Multiple CRMs: If you sync to multiple tools, confirm dedupe rules to avoid duplicates.
• Privacy/DND: Respect local regulations for storing phone numbers and contacting DND users.

🔝 Back to top

🔢 Sample data formats

Phone:

• Local (India): 9876543210
• E.164: +919876543210

IVR / DID examples:

• IVR Sales_01 → ID IVR-2345
• DID list → 080-1234-5678, 011-7654-3210

Agent record (Bitrix24):

Name: Riya SharmaEmail: riya@brand.comPhone: 9988776655Department: Sales → Inbound

🔝 Back to top

🛠️ Troubleshooting

Problem: Calls don’t map to the right contact
Fix: Normalize numbers; ensure the Phone field is used consistently as the primary key.

Problem: Events fail to trigger
Fix: Verify After‑Call / In‑Call API/Webhooks are enabled on your plan; check admin permissions.

Problem: Owner/assignee is wrong
Fix: Ensure the agent exists as a Bitrix24 user and is active; avoid shared numbers.

Problem: Duplicate contacts
Fix: Align dedupe settings (prefer Phone, fallback Email); clean existing duplicates before syncing.

🔝 Back to top

🔒 Security & privacy

• Store only necessary PII; restrict export of phone lists.
• Apply role‑based access to integration settings and logs.
• If exporting for support, mask phone numbers and emails.

🔝 Back to top

🆘 Escalation & support

What to collect

• Screenshot of Bitrix24 Contact showing the Phone field and value.
• Screenshot of MyOperator → API Integration section.
• Sample customer and agent numbers (masked), and your IVR/DID.

Who to contact

• 📮 MyOperator Support: /support or support@myoperator.co
• 🧩 Bitrix24 Support: /helpdesk or your Bitrix24 partner

Message template

“We’re preparing Bitrix24 ↔ MyOperator integration. Prereqs checked except . Attached: screenshots + masked sample data. Please advise.”

🔝 Back to top

🚀 Next step: Start the integration

When everything above is green, follow the main guide:
➡️ Connect Bitrix24 with MyOperator (Webhook & Field Mapping) → /kb/bitrix24-myoperator/integration-howto

🔝 Back to top

❓ FAQ

Q: Phone or Email as the primary key?
A: Use Phone for telephony alignment; use Email as a fallback.

Q: Do I need E.164?
A: Recommended if you operate in multiple countries; otherwise, a consistent 10‑digit local format is fine.

Q: Can I sync only certain IVRs/DIDs?
A: Yes—filter by IVR ID/DID in the integration flow.

🔝 Back to top

🔗 Related articles

• Connect Bitrix24 with MyOperator (Webhook & Field Mapping) → /kb/bitrix24-myoperator/integration-howto
• Normalize phone numbers to E.164 → /kb/crm/phone-normalization-e164
• MyOperator: Enable After‑Call & In‑Call APIs → /kb/myoperator/api-webhooks-enable

🔝 Back to top

🧱 Structured data (HowTo + FAQPage)

<script type="application/ld+json">{  "@context": "https://schema.org",  "@type": "HowTo",  "name": "Verify prerequisites for Bitrix24 ↔ MyOperator integration",  "totalTime": "PT20M",  "step": [    {"@type": "HowToStep", "name": "Confirm admin access", "text": "Ensure admin rights in both Bitrix24 and MyOperator.", "url": "#verify"},    {"@type": "HowToStep", "name": "Check customer Phone field", "text": "Make sure Contacts/Leads have a Phone field populated.", "url": "#verify"},    {"@type": "HowToStep", "name": "Verify agent records", "text": "Each calling agent exists as a Bitrix24 user with unique phone/email.", "url": "#verify"},    {"@type": "HowToStep", "name": "Confirm API/Webhook features", "text": "After‑Call / In‑Call features enabled in MyOperator.", "url": "#verify"},    {"@type": "HowToStep", "name": "Gather IVR/DID identifiers", "text": "Note IVR ID and DID list for filtering.", "url": "#verify"},    {"@type": "HowToStep", "name": "Prepare test data", "text": "Have one customer and one agent number ready for validation.", "url": "#verify"}  ],  "tool": [    {"@type": "HowToTool", "name": "Bitrix24"},    {"@type": "HowToTool", "name": "MyOperator"}  ],  "image": {    "@type": "ImageObject",    "url": "./images/bitrix-contact-phone-field.png",    "caption": "Bitrix24 Contact with Phone field present."  }}</script><script type="application/ld+json">{  "@context": "https://schema.org",  "@type": "FAQPage",  "mainEntity": [    {"@type": "Question", "name": "Phone or Email as the primary key?", "acceptedAnswer": {"@type": "Answer", "text": "Use Phone for telephony alignment; Email as fallback."}},    {"@type": "Question", "name": "Do I need E.164?", "acceptedAnswer": {"@type": "Answer", "text": "Recommended for multi‑country operations; otherwise use a consistent local format."}},    {"@type": "Question", "name": "Can I sync only certain IVRs/DIDs?", "acceptedAnswer": {"@type": "Answer", "text": "Yes—filter by IVR ID/DID in the integration flow."}}  ]}</script>

🔝 Back to top