Mumbai · Delhi · Bengaluru · Pune · Kolkata
Differentiator · 02 of 02 · Sales & Customer Care

Enquiry to possession,
on one record.

Standalone CRMs sell you a pipeline. Then someone else's tool sends the demand letter. Then a third tool tracks the collection. Then a fourth handles complaints. Farvision is the one record — from the first phone call to the keys in the hand, every interaction lives on the customer.

§ 01
Difference
Standalone CRM stack vs. integrated

The CRM was the easy part.
The next 30 years are harder.

Real estate isn't ecommerce. The "sale" doesn't end at checkout — it triggers 5 to 7 years of demand letters, modifications, complaints, possessions and community life. A standalone CRM stops at the booking. Farvision keeps going.
Standalone CRM stack

Pipeline-only. Then handover.

Lead lives in the CRM until booking. After booking, the customer disappears into a different system.
Demand letters generated by an Excel-driven script someone in finance maintains, on the side.
Channel partner commissions tracked in yet another spreadsheet, with month-long disputes.
Complaints & modifications use a ticketing tool that doesn't know the customer's payment status.
By the time the keys are handed over, the customer has been across 4 tools and three teams.
Farvision · integrated

One record, one lifetime.

The lead becomes a customer becomes a resident. One ID. One ledger. One contact history forever.
Demand letters auto-trigger on milestone progress, with the right tax workings, ready for one-click despatch.
Channel partners see their pipeline, their commission, their pending bills — on the white-labelled Channel Partner App.
A complaint comes in — Customer Care sees the customer's full history, payment status, modifications. No 'let me transfer your call'.
At handover, the customer flows seamlessly to Community Management. Same record. Same login. Same trust.
§ 02
Lifecycle
Eight stages · seven years · one ID

The customer journey,
encoded as one ledger.

The customer ID is created on the first enquiry. It carries every tap, message, payment, complaint and possession through to community life — without a single re-keying.
Customer journey from enquiry to community PRE-BOOKING · SFA CUSTOMER CARE COMMUNITY 01 Enquiry website · call · referral 02 Site visit RM · channel · time 03 Offer / Booking price · scheme · token 04 Agreement demand · ledger · TDS 05 Milestone collect demand · receipt · auto 06 Care & mods complaint · transfer 07 Possession snag · keys · OC 08 Community resident app · life D + 0 D + 7 D + 30 M + 1 M + 12 M + 36 Y + 4 Y + 5+
+38%Lift in lead-to-booking conversion when sales & finance share one record
99.8%Of demand letters trigger on time, against milestone certification
5+ yrsMedian customer relationship lifespan held on a single ID
§ 03
Roles
Who actually uses this · what they need

Same customer record,
four chairs around it.

Sales head, RM, customer care manager, CFO — every chair sees the same record, but the lens that matters to them.

The funnel, the source, the commission.

The sales head needs to know the truth — which campaign brought the leads, which RM closed them, which channel partner deserves credit, and how much margin survived the discounting. Farvision's SFA is built so that funnel is the same data finance reconciles to, not a parallel narrative.

01
Live inventory gridUnit-level availability, blocking, allotment — synced across walk-ins, partners, RMs and the website.
02
Channel partner attribution & commissionEach lead source-of-truth ties to commission ledger. Auto-disputes, auto-resolutions, auto-payouts.
03
Funnel + cohort analyticsLead → site visit → booking, sliced by source, RM, project, week. Cohort decay and win-back triggers.
04
Pricing engine & offer governanceDiscount caps by RM, pricing approval workflows, offer-end tracking — discipline without slowing the team down.

Every customer's history, in your pocket.

The relationship manager is the customer's first and last impression. Farvision's mobile SFA means walking into a site visit with everything you need — the lead's history, the units they've shortlisted, the offers they've seen, the pricing they qualify for — without paper, without scrambling.

01
Mobile site-visit captureCheck-in, capture interest, photo allotment, generate booking form, accept token — all from the phone.
02
Live unit availabilityNo double-allotment. The moment you block a unit, every other RM, partner and walk-in sees it locked.
03
Personalized offers, on the spotThe pricing engine knows the customer's qualification, the inventory's status, your discount cap — generates the right offer in 10 seconds.
04
Auto-follow-up sequencesIf a customer doesn't book in 14 days, the system schedules WhatsApp reminders, calls and updates — with your tone, your name.

The first call is the only call.

Customer care lives or dies on first-call resolution. The team needs to see, on one screen, who the customer is, what they bought, what they've paid, what they've complained about, and what's outstanding. Farvision puts all of that on one record — accessible from the call screen.

01
360° customer viewBookings, payments, demand letters, modifications, prior complaints, communications — all in one timeline.
02
SLA-tracked complaint workflowCategorized, assigned to right team, SLA timers running, customer-visible status. Closure with sign-off.
03
Modifications & transfersPlan changes, name changes, NRI transfers — with the financial & tax implications computed live.
04
Customer App self-serviceMost of what they call about — statements, receipts, complaint status, project updates — is on the white-labelled app.

The booking becomes the receivable — automatically.

The CFO's nightmare in real estate is that sales books a unit and finance hears about it three days later, after the customer has already called asking why their demand letter hasn't arrived. Farvision makes booking and receivable two views of the same row.

01
Booking → AR · atomicThe moment booking is approved, demand schedule, customer ledger, escalations and tax workings exist.
02
Auto demand letters · milestone-awareWhen the engineer certifies a milestone, demand letters draft automatically — RERA-compliant, tax-correct, formatted.
03
Collection auto-applicationBank credit comes in, system matches to demand, applies to ledger, generates receipt, sends to customer. Zero manual.
04
RERA / DLD compliance · embeddedProject escrow tracking, 70% rule, RERA returns — all derived from the customer ledger.
§ 04
Scenarios
Real situations · real flows

What happens in the real world,
walked through Farvision.

Two of the most common customer-side situations a developer's office handles every week.
Scenario 01

Customer books a unit at the site office.

1
RM opens the customer record on their phonePast site visits, channel-partner attribution, KYC done — everything pre-loaded.
SFA · Mobile
2
Pricing engine generates the offerCustomer-specific scheme, RM's discount cap, current unit pricing — output: signed offer in 30 seconds.
SFA · Pricing
3
Token received · unit locked atomicallyThat unit now reads "Blocked" everywhere. No other RM, partner, or walk-in can re-allot it.
SFA · Inventory
4
Booking → AR ledger createdCustomer ID issued. Demand schedule built per agreement payment plan. Tax workings ready.
Customer Care · AR
5
Channel partner commission provisionedCommission ledger updated. Visible to the partner on their app within minutes.
SFA · AP
6
Customer App credentials despatchedCustomer can log in, see status, pay tokens, raise queries — on day one.
Customer App
Scenario 02

An existing customer calls customer care upset about their plan demand.

1
Inbound call resolves to customer recordCRM screen pops with the customer's full timeline — bookings, payments, complaints, modifications.
Customer Care · 360°
2
Demand letter dispute investigated liveAgent sees the demand was triggered by a milestone certification. Source: site engineer's tap on the Site App.
Engineering ↔ AR
3
Photo evidence pulled from milestone certificationSame record. Customer is shown the proof. Issue resolved on call.
CAFM · Documents
4
Conversation logged on the customer recordSLA closed. Sentiment marked. Auto-summary into the customer's contact history forever.
Customer Care · SLA
We replaced three separate tools — a CRM for sales, a ticketing tool for care, and a script for demand letters. Farvision is one screen. Our customer care team's first-call resolution went from 41% to 87% in the first quarter.
— Customer Care Head, Top-10 Indian developer
Next step

See your customer record on Farvision.

30 minutes. We'll walk a single customer from enquiry to community — and back. Bring your sales head, your customer care head, your CFO. They'll all see what they need.