SolutionsSales
Module 04 · Sales

Every enquiry, in one pipeline, fairly shared.

Sales captures enquiries from property portals, your website, phone calls and walk-ins through a single intake, distributes them across the telecalling and closing teams on a rota, and follows each buyer from first call through site visit, hold, token and booking.

Intake

Every enquiry comes through one door.

Whatever the source, a lead is created the same way, deduplicated the same way and allocated the same way. That is what makes source performance comparable — and what stops a paid portal lead dying in an inbox nobody owns.

Intake · one doorLive
PortalsWebsitePhoneMeta / WhatsAppWalk-inCSV importINTAKEContactedSite visitHoldBooked
Property portals

Alert emails are parsed into structured leads on arrival, so the enquiry is in the pipeline before anyone opens the inbox.

Website and landing pages

A signed webhook endpoint per source. Your site posts the form; the lead appears with its source attached.

Phone calls

A telephony webhook creates or matches the lead on the call, so an unanswered enquiry is still a record.

Meta lead ads and WhatsApp

Signed delivery direct from Meta — no token to leak, no CSV to download.

Walk-ins

Manual entry through the same intake, so a walk-in is deduplicated against an existing enquiry.

Bulk and historical

CSV import through the same door, with the same validation as everything else.

Allocation

Distribution is a rota, not a race.

Leads are shared across the telecalling and closing teams on a defined rota rather than going to whoever refreshes fastest. Availability, capacity and who is on shift all count.

Why this matters commercially

Speed of pickup and quality of close are not the same skill. If allocation rewards only the first, you are quietly routing your best enquiries away from your best closer.

Stable, repeatable assignment
Allocation is computed, not manual, so the same conditions produce the same distribution — and a manager can explain any assignment after the fact.
Reassignment is an event
Ownership changes through a recorded transfer with a reason, visible on the lead timeline. Leads do not quietly migrate.
Per-source configuration
Each source carries its own routing, so site-visit enquiries and cold portal leads need not go to the same queue.
The pipeline

First call to booking, with the unit attached.

A lead in Terra is tied to actual inventory, not to a free-text note about what the buyer wanted. A hold on a lead is a hold on a unit.

01
New
Created by intake, deduplicated, allocated and due for first contact.
02
Contacted
Requirement captured: budget, configuration, facing, floor.
03
Site visit
Scheduled and recorded, with the units shown attached.
04
Hold
A unit is held against this buyer, with an owner and an expiry.
05
Token
Token received and recorded against the unit.
06
Booked
The unit moves to booked in inventory. One event, both modules.
Day to day

Built for a telecaller’s morning, not a report.

Click to call, and how it went
Calls are placed from the lead and the outcome is recorded against it. A manual call can be logged the same way.
Follow-ups that become tomorrow's work
A scheduled follow-up on a lead is what appears on that person’s list the next morning. Nothing depends on remembering.
Live inventory in the conversation
The rep sees availability and the explained alternatives from Inventory without leaving the lead.
A dashboard for the manager
Pipeline by stage, by source and by person — reading the same records the team works in.
One timeline per buyer
Every call, visit, note, hold and reassignment, in order. The handover when someone leaves is the timeline.
Watch it

Sales, walked through.

Two minutes, from a telecaller’s first call of the day to the manager’s view of the whole pipeline.

Sales, walked through2:11
Next step

See it against your own project.

A walkthrough runs on your data — one real approval, one live tower, last week’s enquiries. Forty minutes, no slides.