Set up a real-estate developer workspace

Approved project facts, reviewed inventory import, representative ownership, opportunity stages, visits and evidence-safe reporting.

1
1. Add approved projects and unit types
Open Projects and record the approved bilingual name, location, licence metadata, price range, delivery/freshness facts and active unit types. Treat price and availability as checked facts with a date—not a promise. Moyafa does not replace the developer ERP, finance or contract system.
Open projects
2
2. Review inventory before importing
Smart Import accepts CSV, Excel and PDF for review. Confirm table types, bilingual column mappings and every validation issue before save. The current inventory contract creates new projects/unit types and skips duplicates or unknown project references; it never silently overwrites existing inventory. Use the row receipt to reconcile the reviewed file.
Open Smart Import
3
3. Add representatives and agree ownership rules
Invite the pilot representatives and manager with least privilege. Agree which projects/teams receive each inquiry, the acceptance SLA, escalation owner and working hours before enabling live routing. A notification attempt is evidence only when its recorded outcome says it reached the intended representative.
Open team settings
4
4. Confirm the opportunity before acting
An inquiry may become a structured opportunity with project, unit, budget, financing, timeframe and source context. The representative must confirm missing or low-confidence facts. Never let AI invent a project, exact price, availability, financing approval, reservation state, contractual term or consent.
Open inbox
5
5. Work Today, next actions and visits
Use the real-estate workspace to accept ownership, contact the lead, move only through valid stages, keep one next action, and schedule/record site visits. Conversation status and opportunity stage are separate: closing a chat must not silently close a long-running sale.
Open real-estate workspace
6
6. Reconcile reports to durable records
Before using funnel, source, demand, representative or outcome reports, reconcile their totals to the pilot opportunities and event history. Monetary values remain permission-gated. Association or recorded value is not proof that Moyafa caused revenue uplift.
Open real-estate analytics
7
7. Run a synthetic shadow cycle before launch
With fictional leads, test duplicate inquiry handling, assignment/acceptance, notification fallback, SLA escalation, contact, visit, reminder, lost/won paths, iPhone actions, reporting and recovery. Active-lead import, approved sales files, public screenshots and performance claims require the signed pilot boundary and consent.

Approved project facts, reviewed inventory import, representative ownership, opportunity stages, visits and evidence-safe reporting.

1. Add approved projects and unit types

Open Projects and record the approved bilingual name, location, licence metadata, price range, delivery/freshness facts and active unit types. Treat price and availability as checked facts with a date—not a promise. Moyafa does not replace the developer ERP, finance or contract system.

Open projects

2. Review inventory before importing

Smart Import accepts CSV, Excel and PDF for review. Confirm table types, bilingual column mappings and every validation issue before save. The current inventory contract creates new projects/unit types and skips duplicates or unknown project references; it never silently overwrites existing inventory. Use the row receipt to reconcile the reviewed file.

Open Smart Import

3. Add representatives and agree ownership rules

Invite the pilot representatives and manager with least privilege. Agree which projects/teams receive each inquiry, the acceptance SLA, escalation owner and working hours before enabling live routing. A notification attempt is evidence only when its recorded outcome says it reached the intended representative.

Open team settings

4. Confirm the opportunity before acting

An inquiry may become a structured opportunity with project, unit, budget, financing, timeframe and source context. The representative must confirm missing or low-confidence facts. Never let AI invent a project, exact price, availability, financing approval, reservation state, contractual term or consent.

Open inbox

5. Work Today, next actions and visits

Use the real-estate workspace to accept ownership, contact the lead, move only through valid stages, keep one next action, and schedule/record site visits. Conversation status and opportunity stage are separate: closing a chat must not silently close a long-running sale.

Open real-estate workspace

6. Reconcile reports to durable records

Before using funnel, source, demand, representative or outcome reports, reconcile their totals to the pilot opportunities and event history. Monetary values remain permission-gated. Association or recorded value is not proof that Moyafa caused revenue uplift.

Open real-estate analytics

7. Run a synthetic shadow cycle before launch

With fictional leads, test duplicate inquiry handling, assignment/acceptance, notification fallback, SLA escalation, contact, visit, reminder, lost/won paths, iPhone actions, reporting and recovery. Active-lead import, approved sales files, public screenshots and performance claims require the signed pilot boundary and consent.