How to Manage Real Estate Token Amounts and Booking Confirmations Using Your CRM in India

Real estate CRM token booking management in India solves the single most expensive mistake in residential and commercial sales: the double booking. When a ₹90 lakh flat is blocked on WhatsApp by two different agents at the same time, someone is going to lose a buyer, a commission, and possibly face a RERA complaint. A purpose-built CRM instantly updates unit status the moment a token is recorded, sends a confirmation to the buyer automatically, and triggers the entire downstream workflow — booking form, Agreement to Sale, payment plan — without anyone chasing anyone. This guide explains exactly how that works, from token receipt to signed agreement.

What Is a Token Amount in Indian Real Estate?

A token amount is the first financial commitment a buyer makes to block a specific unit. It is not the booking amount, and it is not the down payment — it is the signal that the buyer is serious and the unit should be removed from active availability.

Token amounts vary by asset type and city:

• Residential projects: typically ₹25,000–₹5 lakh
• Commercial projects: typically ₹50,000–₹25 lakh
• Luxury residential (Mumbai, Delhi NCR, Bengaluru): ₹2–10 lakh is common

The same financial instrument goes by different names across India:

• Token amount (most common)
• Booking amount (often used interchangeably, though technically the full booking amount comes later)
• EOI — Expression of Interest (pre-launch; no specific unit assigned yet)
• Earnest money
• Advance

Regardless of what it is called, the token triggers unit blocking — the unit is marked unavailable to all other buyers and agents from the moment the token is received.

What Follows the Token

The token is the beginning of a structured sequence:

1. Token received → unit blocked
2. Booking form executed within 24–48 hours
3. Balance of booking amount paid (if staged)
4. Agreement to Sale executed within 30–90 days
5. Payment plan instalments begin

RERA Section 13 is critical here. Under the Real Estate (Regulation and Development) Act, a developer must execute the Agreement to Sale within 30 days of receiving any advance or deposit that exceeds 10% of the property cost. Failure to do so creates a statutory refund obligation. For a ₹1 crore flat, that threshold is ₹10 lakh — which many “booking amounts” cross immediately. The 30-day clock starts ticking the moment the money is received, not when the paperwork is remembered.

Types of Booking Models in India

Not every token works the same way. Indian real estate has evolved four distinct booking models, and your CRM workflow needs to handle all of them.

1. Direct Booking The buyer pays the token directly to the developer. The broker facilitates the transaction but typically does not collect funds. The unit is blocked in the developer’s inventory immediately. This is the standard model for under-construction and ready-to-move residential projects.

2. EOI / Priority Application Common at pre-launch stages where specific units are not yet allotted. The buyer submits an Expression of Interest along with a payment (₹1–5 lakh typically) to get priority in the unit allotment process. No unit is blocked yet — the EOI queue determines the order in which buyers choose their units when the project formally launches.

3. Demand Note Booking The developer issues a formal demand note before the booking form is executed. The buyer pays against the demand note, and the booking form follows. More common in larger commercial transactions and institutional deals.

4. Blocked Unit Advance / Soft Hold The unit is held for 48–72 hours against a soft verbal or written commitment — no money may have changed hands yet. This is common when a buyer is coming from another city, or when funds take time to transfer. The soft hold converts to a hard block when the token is received.

Each model has a different starting point in the CRM workflow, but all of them converge at the same place: a unit blocked, a buyer confirmed, and a countdown to Agreement to Sale.

Why Token Booking Management Fails Without a CRM

Managing 50 active deals across multiple projects without a CRM is not inefficient — it is a liability. Here is exactly where the failures occur:

• Double booking. Unit blocking is not updated in real time in a shared Excel sheet. Agent A blocks Unit 304 on WhatsApp at 11:03 AM. Agent B closes a token payment for Unit 304 at 11:47 AM. Neither knew. Now you have two buyers, one unit, and one very unhappy person.
• No audit trail. “I sent the confirmation on WhatsApp” is not documentation. When a buyer disputes the token terms or claims they were never told about the cancellation policy, you have no timestamped record.
• Follow-up slips. The next step after token receipt — collecting the booking form, scheduling site visits, sending payment reminders — depends entirely on someone remembering to do it. When it slips, the buyer cools off. A cooled buyer at booking stage is a cancelled deal.
• Team visibility gaps. In a team of 5 agents, each working independently, no one knows which units their teammates have soft-blocked or are in conversation about. Leads are duplicated, conflicts arise, and commissions get disputed.
• Agreement to Sale deadline missed. The 30-day RERA clock runs silently in the background. An agent closes a token on a ₹85 lakh flat in Hyderabad, marks it in a notebook, and moves on. Forty-five days later, the developer issues a default notice. A CRM with an automated Day 7 / Day 20 / Day 28 reminder makes this impossible to miss.
• Cancellation chaos. A buyer withdraws after paying a token. Without a CRM, the unit sits marked “blocked” for days because no one thought to unblock it. Waitlist leads who could have been converted are never notified. The refund is tracked in a separate sheet that may or may not be reconciled.

Step-by-Step CRM Workflow for Token Booking Management

Here is how a properly configured real estate CRM handles the entire token-to-agreement sequence.

Stage 1: Unit Identification

A lead arrives — from 99acres, MagicBricks, Housing.com, a site walk-in, or a referral. The CRM auto-creates a contact and lead record the moment the enquiry comes in. No manual data entry needed for portal leads — the integration pulls them directly.

The agent opens the lead record and views the inventory module. Unit status is live:

• Available — no one has spoken to this buyer about this unit
• Soft Hold — unit held informally, timer running
• Blocked — token received, unit off the market
• Booked — booking form executed
• Sold — Agreement to Sale signed and registered

The agent shortlists 2–3 units for the buyer. The CRM shows current price, floor plan, facing, and availability status for all of them simultaneously — across every project the agency handles.

Stage 2: Token Payment

The buyer confirms they want to proceed. The agent moves the deal to “Booking in Progress” stage in the CRM pipeline.

Token payment details are recorded immediately:

• Token amount in ₹
• Payment mode: NEFT / UPI / cheque / demand draft
• UTR number or cheque number
• Receipt number

The moment the token is recorded, the CRM does three things simultaneously:

1. Updates unit status: Available → Blocked. Every agent on the team sees this instantly. The unit disappears from the available inventory list.
2. Sends automatic WhatsApp + email confirmation to the buyer. The message includes: unit details, token amount received, receipt/UTR reference, next steps, and the developer’s contact details.
3. Creates a task for the agent: “Execute booking form within 48 hours.”

The buyer has written confirmation. The agent has a task. The unit is locked. All of this happens in under 60 seconds.

Stage 3: Booking Form Execution

The CRM auto-triggers a task for the agent when the token is received: complete the booking form within 24–48 hours. This is not a calendar reminder the agent sets manually — it fires automatically, every time, for every deal.

The signed booking form is uploaded to the deal’s document vault in the CRM. From this point:

• The unit is permanently linked to the buyer record
• Every team member with access to the project can see the unit as booked
• If the booking amount is staged, automated reminders fire for the balance

The document vault also stores: the builder’s brochure, RERA registration certificate, payment plan schedule, and any personalised offer letters exchanged before booking.

Stage 4: Agreement to Sale Tracking

RERA Section 13 compliance is non-negotiable. The CRM sets an automatic reminder sequence from the day the token is received:

• Day 7: Reminder to agent and team lead — “Agreement to Sale must be executed by Day 30.”
• Day 20: Second reminder — “10 days remaining for Agreement to Sale execution.”
• Day 28: Urgent reminder — “Agreement to Sale deadline in 2 days. Take action now.”

Within the deal record, the agent tracks:

• Agreement draft status (pending / sent to buyer / under review / signed)
• Stamp duty payment date
• Registration appointment date
• Payment plan instalments linked to the deal

If the deal is cancelled at any stage, the CRM triggers a refund workflow: the refund amount is logged, the unit status reverts from Blocked to Available, and the CRM notifies waitlist leads for that unit automatically.

Common Token Booking Mistakes (and How a CRM Prevents Them)

These are the mistakes that kill deals, damage relationships, and create RERA exposure. Every single one is preventable.

1. Accepting token without written confirmation to the buyer. The buyer assumes the deal is done; the agent forgets to send anything. Three days later, the buyer calls someone else. A CRM auto-sends the confirmation the moment the token is recorded — no human step required.

2. Not updating unit status immediately after token receipt. The agent updates the Excel sheet “when I get back to the office.” In that window, another agent calls the same buyer about the same unit, or worse, another buyer books it. A CRM updates unit status in real time, the moment the token payment is entered.

3. No clarity on refund conditions at time of booking. When a cancellation happens, a dispute over the refund amount immediately follows. A CRM document vault stores the cancellation policy (from the builder’s booking form) at the time of token, giving both sides a clear reference point.

4. Not recording which agent closed the booking. In a team deal with multiple agents involved, commission disputes are common when records are unclear. The CRM timestamps every action and assigns it to a user — there is no ambiguity about who recorded the token, who followed up, and who closed.

5. Missing the 30-day Agreement to Sale deadline under RERA. This is the most serious mistake. The developer can face a statutory refund obligation; the broker loses credibility with the client. The CRM’s automated Day 7 / Day 20 / Day 28 reminders eliminate this entirely.

Comparison: Without CRM vs With Realatic

Function	Without CRM (Excel + WhatsApp)	With Realatic
Unit status visibility	Updated manually, always lagging	Live — updates the moment token is recorded
Double booking prevention	No protection	Impossible — unit blocked instantly on token entry
Token receipt confirmation to buyer	Manual WhatsApp, easy to forget	Auto-sent via WhatsApp + email on token recording
Booking form storage	Email attachment or physical file	Document vault — searchable, accessible by team
Follow-up automation	Agent’s memory / personal calendar	Auto-task triggered on every stage change
RERA Section 13 reminder	None	Automated reminders: Day 7, Day 20, Day 28
Team visibility	None — each agent works in isolation	Full team can see unit status and deal stage
Cancellation management	Manual: refund tracked separately, unit unblocked manually	Automated refund workflow, unit reverts to Available
Waitlist notification on cancellation	Never happens	Auto-notifies waitlist leads when unit is freed
Commission tracking	Separate spreadsheet, often disputed	Logged at booking, tied to deal record and agent
Audit trail	None	Every action timestamped, logged, non-editable
Payment plan tracking	Separate document	Linked to deal record, milestone reminders automated
TDS prompt (deals >₹50L)	Never reminded	Auto-prompt: Form 26QB within 30 days
Reporting by project / agent	Manual pivot tables	Live dashboard — bookings, conversion, revenue by project

Real-World Scenarios from Indian Markets

Scenario 1: Pune Launch Day — 200-Unit Project, 50 EOIs in 3 Hours

A residential project in Wakad, Pune, opens bookings on a Saturday morning. The developer’s sales team and channel partners receive 50 EOI applications in the first three hours. Each application is for a different unit preference. Several buyers have expressed interest in the same floor-facing combination.

Without a CRM: The sales team is managing three WhatsApp groups, two Excel sheets, and a physical ledger at the site office. Three units are confirmed to two buyers each. The resulting dispute takes four weeks to resolve, one buyer takes a legal notice, and two channel partners lose their commission.

With Realatic’s inventory module: Every EOI is logged as a lead record the moment it is submitted. When the team begins allotting units, the inventory module shows live status — no unit can be allotted to a second buyer once blocked. The project manager can see the full allotment status in real time on a dashboard. Fifty EOI conversions, zero double bookings.

Scenario 2: Hyderabad Broker, ₹90L Flat, Missed Agreement to Sale Deadline

An independent broker in Kondapur, Hyderabad, closes a token for a ₹90 lakh 3BHK. Token amount: ₹2 lakh. The buyer is an outstation NRI who is flying back after the token and plans to sign the Agreement to Sale on their next visit.

The broker records the token in a notebook and moves on to three new leads. Forty-five days pass. The developer’s team calls the broker — the Agreement to Sale is overdue, and the developer is preparing a default notice. The buyer is now in a different country and upset. The deal falls apart. The broker’s commission on a ₹90L deal — typically ₹90,000–₹1.35 lakh — is lost.

With Realatic: The Day 7 reminder fires automatically. The broker contacts the buyer to confirm the Agreement to Sale date. The Day 20 reminder confirms the appointment is scheduled. The agreement is executed on Day 22. The broker collects commission. The buyer’s NRI deal closes cleanly.

Scenario 3: Bengaluru Commercial Project — Buyer Withdraws After Token

A buyer in Whitefield, Bengaluru, pays ₹5 lakh as token for a commercial office unit priced at ₹1.2 crore. Three weeks later, they withdraw due to financing falling through.

Without a CRM: The broker manually informs the developer. The unit sits in “blocked” status in the Excel sheet for 10 days because the update is missed. Three leads who had expressed interest in the same unit during those 10 days are never contacted — they find other options. One of them was a serious buyer. That commission evaporates.

With Realatic: When the cancellation is recorded in the CRM, the refund workflow triggers automatically — the refund amount is logged, the developer is notified, and the unit status reverts to Available instantly. The CRM identifies two leads in the pipeline who had shortlisted this unit and sends them an automated notification: “A unit you were interested in is now available.” One of them books within 48 hours.

Realatic Features Built for Token Booking Management

Realatic is built specifically for Indian real estate teams. The token and booking workflow is not a generic CRM adapted for property — it is designed around how Indian residential and commercial sales actually work.

Inventory module. Real-time unit status across multiple projects — residential, commercial, plotted, township. Every agent on your team sees the same live view. Soft hold timers, blocking on token, automatic revert on cancellation.

Custom deal pipeline. Configure stages that match your actual workflow: Lead → Site Visit → Token Received → Booking Form Sent → Agreement to Sale Pending → Registered. Each stage triggers the right automations automatically.

WhatsApp inbox — included free. Token confirmation, booking form receipt, payment reminders, RERA deadline alerts — all delivered to the buyer on WhatsApp. Indian buyers respond to WhatsApp. Not email, not SMS.

Document vault. Every document linked to every deal: token receipt, booking form, payment proof, RERA registration certificate, Agreement to Sale draft, stamp duty receipt. Accessible to the full team. No more “I’ll send it on WhatsApp.”

RERA Section 13 compliance reminders. Automated alerts at Day 7, Day 20, and Day 28 from token receipt. If the advance exceeds 10% of deal value, the compliance clock is tracked automatically.

TDS prompt for deals above ₹50 lakh. Under the Income Tax Act, the buyer must deduct TDS at 1% and file Form 26QB within 30 days of any property transaction above ₹50 lakh. Realatic automatically prompts the agent to remind the buyer when the deal crosses this threshold.

Reporting. Booked units by project, by agent, by week. Conversion rate from token to Agreement to Sale. Average days to close per project. Commission earned by agent. Everything a team lead or business owner needs to manage performance without building custom reports.

FAQ

Q: What is the difference between a token amount and a booking amount in Indian real estate?

The token amount is the initial, often smaller payment that blocks the unit — typically paid informally via UPI or NEFT, sometimes even in cash, to signal serious intent. The booking amount is the larger, formally documented payment — usually 5–10% of the property value — paid after the booking form is executed. In practice, many developers use the terms interchangeably, but the distinction matters because the booking form and RERA documentation are tied to the booking amount, not the token. If your CRM only tracks “booking amount,” you are missing the unit-blocking event and the RERA Section 13 trigger, which both start from the first advance payment.

Q: Is the token amount refundable if the buyer changes their mind?

It depends entirely on the terms in the developer’s booking form and any side agreement between the parties. Most developers treat the token as partially or fully non-refundable if the buyer withdraws without cause, citing it as compensation for taking the unit off the market. However, if the developer fails to execute the Agreement to Sale within 30 days of receiving an advance exceeding 10% of the property value (RERA Section 13), the developer is statutorily obligated to refund the amount with interest. Buyers should always get the refund conditions in writing before paying. Brokers should store this documentation in the deal’s CRM record — it is the first thing anyone asks for in a dispute.

Q: How does RERA protect buyers who have paid a token amount?

RERA Section 13 is the primary protection. If the amount received exceeds 10% of the agreed property price, the developer must execute a formal Agreement to Sale within 30 days — or refund the amount with interest. Beyond Section 13, RERA requires developers to maintain an escrow account holding 70% of collected amounts, ensuring the money is used for the project and not diverted. Buyers can file complaints with the State RERA authority if the developer delays possession, changes specifications, or misrepresents the project after taking a booking. A CRM that tracks payment dates, amounts, and Agreement to Sale execution gives buyers (and brokers) a clean, timestamped record that is exactly what a RERA authority reviews in a dispute.

Q: How can a CRM prevent double-booking of a real estate unit?

By making unit status updates atomic and real-time. When a token is recorded in Realatic, the unit status changes from Available to Blocked at that exact moment — it is not a batch update, not a manual step, and not something that syncs overnight. Every agent on the team sees the Blocked status immediately, across every device. There is no window in which a second agent can initiate a booking for the same unit. The system also prevents soft holds from running indefinitely — if a soft hold expires without a token, the unit automatically reverts to Available and the team is notified. Double bookings in a properly configured CRM are structurally impossible, not just unlikely.

Q: What documents should a broker collect when a buyer pays a token amount?

At minimum, a broker should collect and store the following at the time of token:

• Payment proof — UTR number (NEFT/UPI), cheque copy, or bank receipt
• Token receipt or acknowledgement from the developer — on their letterhead or CRM-generated
• Developer’s cancellation and refund policy — ideally extracted from the booking form or brochure
• RERA registration number of the project — verifiable on the state RERA portal
• Agreed unit details in writing — tower, floor, unit number, facing, super built-up area, agreed price

If the deal value is above ₹50 lakh, also confirm the buyer’s PAN card copy (required for TDS via Form 26QB). All of these should live in the deal’s document vault in your CRM — not in a WhatsApp thread that will be impossible to find in six months.

Start Managing Every Token Booking Without a Single Missed Step

A token payment is the most critical moment in a real estate transaction. It is the point at which a lead becomes a buyer, a unit moves off the market, and a legally consequential clock starts running. Managing this moment on WhatsApp and spreadsheets is not a workflow — it is a gamble.

Realatic’s inventory module and booking management workflow handles everything from the moment a token is recorded to the Agreement to Sale execution and beyond. Unit blocking, buyer confirmations, booking form follow-ups, RERA deadline reminders, cancellation management, and commission tracking — all automated, all in one place.

• Free plan: 3 users, 100 leads/month, 1 project — no credit card required
• Growth plan: ₹499/user/month
• Pro plan: ₹1,199/user/month
• Setup in 1–2 days
• WhatsApp inbox included free across all plans

If you are closing deals in Pune, Hyderabad, Bengaluru, Mumbai, NCR, or any Indian market and still tracking token bookings manually, the next double booking is not a matter of if — it is a matter of when.

See Realatic’s full inventory and booking management features → or compare plans →