Integration guides
- Bayut → Bitrix24: capture options, reference mapping, community routing
- Dubizzle → Bitrix24: sales vs leasing routing, duplicate storms on launches
- Property Finder → Bitrix24: lead types, listing context, response SLAs
- Meta Lead Ads → Bitrix24: real-time delivery and campaign attribution
- Website forms and WhatsApp: closing the non-portal capture gaps
The normalization layer
Portal payloads differ, so we normalize before CRM: phone numbers to E.164, references matched against your inventory (SPA) where one exists, sources standardized, raw payloads preserved as attachments. This layer — PortalSync in our product terms — is why a portal format change becomes an alert to fix, not a week of silently lost leads.
After normalization, routing and automation are portal-agnostic: one set of assignment rules, one first-touch flow, one response-time dashboard across every source.