Start with the meaning of each event
A Dubai agency evaluating Bayut CRM integration should ask what each incoming event actually tells its team. A person viewing a contact option has not necessarily sent a message or spoken to an agent. If the CRM labels every event as a completed enquiry, the agency can overstate conversations and assign unsuitable follow-up. This guide is a proposed acceptance checklist for a development brief; confirm which capabilities are available in your account before implementation.
Use the official list as your starting point
Bayut’s help centre lists call logs, phone views, email leads, SMS clicks, WhatsApp views and WhatsApp leads among the events available through its leads API. Keep those labels distinct in your mapping document. Ask your integration provider for the current field definitions and access requirements. This public list does not establish that every event includes a telephone number, message body or permission to contact a person.
Build a small mapping table
Create columns for source event type, source reference, event time, available contact details, property reference, assigned owner and next action. Treat these as business requirements rather than API field names. For a contact view with no usable identity, the proposed next action may be reporting only. For a genuine enquiry with supported contact details, define the responsible agent and a review step before any automated response. Preserve missing values instead of inventing them.
Demonstrate three different cases
In an approved test environment, ask the provider to demonstrate a contact view, an enquiry and the same enquiry received again. The contact view should remain distinguishable from the enquiry. The repeated delivery should retain the original reference so the agreed duplicate-handling rule can be checked. Record what you observed, including any unsupported case. Never create real customer enquiries solely to inflate a live dashboard.
Check a worked reporting example
Suppose a fictional daily sample contains 12 contact views and 3 enquiries. Report these as two categories, not 15 conversations. You also cannot infer 15 unique people because one person may generate several events. If an agent confirms two conversations, report that separately with its own definition. Do not calculate a conversion rate until the numerator, denominator and observation period refer to compatible events.
Agree the handover to your agency
Ask Devzonia to review your mapping sheet and identify the available, configurable and development-dependent parts. Specify who reviews unassigned enquiries and how the team sees failed imports. Agree a reconciliation sample before launch: compare source references with CRM records and investigate missing items without blindly replaying them. The acceptance decision should be based on the observed flow, not on a generic integration label.
