Skip to content
Operations / Real Estate

Get to the site visit before the enquiry goes cold.

Enquiry → Lead → Site visit → Inventory → Booking → Payment. RapidRoot connects lead handling, inventory, bookings and payments into the operational workflow around the customer.

Live — standalone workspace. Org-scoped models. One platform foundation. Project/site data product-owned.

Operational flow — revenue speed, not sheets
01
Enquiry
Portal / ad / form
02
Lead
Stage NEW→LOST, UTM
03
Site visit
Scheduled visit
04
Inventory
Unit holds
05
Booking
BKG- customer
06
Payment
PaymentPlan
Speed decides who gets the visit. Follow-up in minutes, not next working day.
Problem

Enquiries go cold while they sit in a sheet.

Real estate interest cools fast. The first team to qualify and book the visit wins — the spreadsheet doesn’t.

01

Leads wait hours for a callback

Portal enquiries sit until an agent is free. Buyer enquires on three listings at once.

02

Inventory intent conflicts

Two buyers want the same unit. Without a hold, someone books what another was promised.

03

Bookings and payments live apart

Payment plans and receipts live elsewhere — the customer repeats the same question twice.

Inventory

Temporary holds prevent conflicting intent.

The flow that makes this product operationally different from a generic CRM — interest → hold → booking, verified. Without exposing Decimal128 in headline.

01

Lead interest

Lead qualified, unitCode unique per org+project.

02

Available unit

InventoryUnit status — available inventory shown.

03

Hold

Temporary hold helps prevent conflicting intent.

04

Booking

BKG- created, customer CUS- linked, unit booked.

05

Payment

PaymentPlan and documents DOC- generated.

Technical trust — holdsShow detail

Current verified behavior: timed holds with server-enforced expiry, unique unitCode per organization+project, org-scoped queries and RBAC. Quantitative hold window is implementation detail — current window helps prevent conflicting booking intent during qualification.

What’s live

Verified modules — org-scoped, not sheets.

Each group editorial, no icon per item.

Inventory

Projects, sites, units

  • Project → Site (RERA-aware)
  • InventoryUnit unique unitCode org+project
  • Temporary holds

Leads

Enquiry → qualified lead

  • Stages NEW → LOST, temperature, UTM
  • Contact deduplication handling
  • Assignment to agents

Bookings

From visit to booking

  • Site visits scheduled
  • Booking BKG- · Customer CUS-
  • Calling: behalf of agent where qualified

Finance

Payments & documents

  • Payment plans, Documents DOC-
  • Org-scoped, OIDC, RBAC — audit on same workspace
  • Portal 99acres (dummy/idempotent) where configured

Standalone workspace on RapidRoot Core — identity/orgs/billing shared; project/inventory/lead/booking data product-owned. Not a Salesforce replacement.

Communication connection

Enquiry handling that books the visit.

Communication is the trigger — operations is the outcome. When enabled, the same workspace can use Messaging and Voice to qualify and book before the enquiry cools.

Speed

Portal enquiry → qualified in minutes, not next working day. Lead temperature and UTM captured.

Context

Every call/message on the buyer timeline — not a personal phone. Agent joins with context.

Hold

Inventory hold links interest to a specific unit — prevents someone booking what another was promised.

For pure communication, see Messaging and Voice (pilot). This page is the operations workspace.

Live — standalone workspaceReal Estate — standalone product on same platform foundation.

Move enquiries to site visits faster.

Guided pilot on your project and inventory data — holds, leads and bookings in one timeline.