Dubizzle

Overview

Dubizzle rides the same Push API token as Bayut, but Ruby CRM treats it as a fully independent portal. Each listing has its own Dubizzle toggle, its own live status, its own expiry date, and its own reference number — so you can run different inventory strategies on Bayut vs Dubizzle without juggling two CRMs.

How to set up

1. 1

   Set up Bayut first — the same Push API token covers Dubizzle automatically.

2. 2

   In your Ruby CRM Bayut connection, add your Dubizzle agency name so listings publish under the right banner.

3. 3

   Toggle Dubizzle publishing per listing in the publish dialog — every property is independent.

4. 4

   Wallet credits for Dubizzle show separately from Bayut in the publish dialog, so you always know which inventory you can keep promoting.

Benefits

• Per-listing Dubizzle toggle independent of Bayut — same agency, different promotion strategy
• Separate Dubizzle wallet balance shown in the publish dialog — never run out mid-day
• Leads from Dubizzle inquiries flow into the same inbox as Bayut, tagged by source so you can route differently
• One configuration, two portals — no second API token to manage

Why it matters

Dubizzle reaches a different buyer demographic than Bayut — often more price-sensitive, often more renters. Brokerages that publish blindly to both waste credits on Dubizzle for properties that won't convert there. Ruby CRM's per-listing toggle lets your team be deliberate without doubling the admin overhead.