Post-sales CRM built around units, bookings and collections.
- Lifecycle stage
- 01Project & inventory setup
- 02Customer & booking
- Used by
- CRM Manager, CRM Executive, Accounts, Support Agent and Admin
Interactive illustration with sample data. Try the controls.
What’s in Post Sales CRM
Projects
Every piece of work in Proprite belongs to a project. Staff choose the project they are working in and see only what their access allows.
- Project information, address, project code and status
- Project bank accounts and accepted payment methods
- Staff access granted project by project
Inventory: tower, floor, unit
Model a development the way it is actually built. Create units one at a time or in bulk, then work with them as a building or as a table.
- Tower → Floor → Unit hierarchy
- Individual and bulk unit creation
- Building view and table view of the same inventory
- Filters and bulk editing across units
Pricing
Rates, plans and charges are defined at project level so every booking draws from the same commercial structure.
- Rate plans and payment plans
- PLC — preferential location charges for floor and facing
- Additional charges such as car parking and club membership
Blocking and booking
Hold a unit for a buyer until an expiry date. If the booking does not happen, the unit becomes available again on its own. If it does, Book Now brings customer, unit, plan, charges, discount and taxes into one live price preview.
- Temporary unit blocks with an expiry date
- Blocked units become available automatically after expiry
- Book Now with customer, unit, payment plan, charges, discount and taxes
- Live price preview before confirmation
- The booking price is locked once the booking is confirmed
Payments and demand letters
Each booking carries its own payment schedule. Record receipts against it, reverse a payment when needed, and generate demand letters as downloadable PDFs.
- Payment schedule generated from the payment plan
- Payment recording and payment reversal
- Demand letters as downloadable PDFs
Customisations, cancellations and documents
Changes that affect a buyer’s unit or money go through approval rather than being edited in place.
- Customisation requests move from Draft → Submit → Approve
- Booking cancellation requires approval
- Documents marked customer-visible or internal-only
Buyer support
Buyers raise tickets from the customer portal. Staff reply in a chat-style thread, so the full conversation stays with the booking.
- Support tickets with chat-style replies
- Ticket history kept with the buyer record
Rules built into Post Sales CRM.
Booking price is locked once the booking is confirmed
Cancellations need approval
Customisations follow Draft → Submit → Approve
Documents are either customer-visible or internal-only
Unit blocks expire automatically
Questions about Post Sales CRM
See Post Sales CRM with your own project.
Walk through Proprite using the workflows your team already manages — your towers, your payment plans, your approval chain.

