How to Track Proposal Status and Responses on DrawMagic

The buyer who went silent three days before Navratri

Your sales manager sent a detailed proposal to a buyer who had visited the sample flat twice, asked pointed questions about the floor plan, and seemed ready to move. Then — nothing. No reply to the follow-up call, no response to the WhatsApp message. Was the proposal even opened? Did the buyer get busy with festive-season family visits? Did a competing project's proposal land in the same inbox the same week?

This is one of the most common — and most expensive — failure points in residential sales. A proposal isn't a one-time event; it's the start of a decision window that, for most Indian home buyers, involves the whole family, multiple site revisits, and comparisons across two or three projects before a booking amount changes hands. If a sales team can't see where each proposal stands, follow-ups become guesswork: too pushy for a buyer who's still consulting siblings, or too passive for a buyer who's ready but waiting on someone to close the loop.

Tracking proposal status and responses in one place — status stage, last activity, and next action — turns this guesswork into a disciplined pipeline. This guide walks through how to read proposal status on DrawMagic, connect it back to the original lead, and build a follow-up rhythm that fits how Indian buyers actually decide.

Why proposal tracking matters more in the Indian buying cycle

A proposal sent to a buyer in a metro rarely gets a same-day answer. According to IBEF's Real Estate Industry in India report (as of February 2026), India's real estate sector is on a long growth trajectory — from roughly US$200 billion in 2021 toward a projected US$1 trillion by 2030 — which also means more projects, more proposals landing in the same buyer's inbox, and more competition for attention at every stage of the funnel (IBEF, Real Estate Industry in India, Feb 2026). In that environment, a proposal that isn't tracked is a proposal that's easy to lose to a competitor who followed up first.

Indian home-buying decisions are also rarely made by one person in one sitting. A proposal often needs to be discussed with a spouse, parents, or an NRI sibling contributing to the down payment, which naturally extends the timeline between "viewed" and "responded." Layer festive periods like Navratri and Diwali on top of that — when families travel, celebrate, and often delay big financial decisions until after the season — and you get response patterns that look erratic unless you're tracking status, not just guessing from silence.

Reading proposal status: the lifecycle on DrawMagic

Every proposal sent from the developer portal moves through a lifecycle that you can monitor from /builder/proposals. Rather than treating "sent" and "no reply" as the only two states, the proposal list distinguishes finer-grained stages so your team knows exactly where to focus.

Reading this table in /builder/proposals daily — rather than only when a sales manager remembers to check — is what separates a pipeline that converts from one that leaks.

Step-by-step: monitoring status and planning follow-up

1. Open the proposal list. From /builder/proposals, filter by status to see everything sitting in "Viewed" or "Stalled" — these are the proposals most likely to need a nudge today.
2. Check the last-activity timestamp. A proposal viewed six hours ago needs a different response than one viewed six days ago. Recency should drive urgency, not the order proposals were sent.
3. Trace the proposal back to its lead. Every proposal links to the originating record in /builder/leads, so you can see the buyer's earlier questions, site-visit history, and any notes your team already logged before deciding how to follow up.
4. Read the response, not just the status label. When a status shows "Responded," open the actual message. A one-line question about possession date needs a fast factual answer; a longer message listing concerns needs a considered reply, possibly a call.
5. Log the next action and a date. Whether it's "call Thursday" or "send updated floor plan," write it down against the proposal so the next person checking the list doesn't have to reconstruct context from memory.
6. Review the pipeline snapshot. /builder/dashboard gives a rolled-up view of proposals by status across all your active listings, so a sales manager can spot bottlenecks — for instance, a cluster of "Viewed" proposals from the same week that never moved to "Responded" — without opening each one individually.

Geographic and demographic patterns to plan around

• Family consultation windows. Many buyers, especially first-time buyers, discuss a proposal with parents or a spouse before responding. Build at least a 3–5 day gap into your follow-up cadence before treating silence as disinterest.
• Site-visit scheduling as the default next step. A "Viewed" status that turns into a reply is very often a request to visit again, not a request for more paperwork — have visit slots ready to offer rather than only sending more documents.
• Festive-season timing. Navratri and Diwali periods typically see a dip in responses followed by a spike once families return to routine. Plan a targeted round of follow-ups for the days immediately after a major festival rather than chasing during it.
• Multi-project pipelines in metros. If your team is selling across two or three active projects in the same city, per-proposal tracking (not just per-project totals) is what prevents a promising lead on Project B from being missed while everyone's attention is on Project A.
• NRI buyers and time-zone lag. A proposal sent to an NRI buyer in the US or Gulf may show as "Viewed" hours before a response arrives, simply because of the time difference — factor this into how quickly you escalate a "Viewed" status to "Stalled."

Mini scenario: reviving a viewed-but-silent proposal before a long weekend

A Bengaluru-based developer's sales team sent a proposal to a buyer for a 3BHK in an under-construction project. The proposal showed "Viewed" within two hours of sending, then sat unchanged for four days — right into a Dussehra long weekend. Instead of sending a generic "just checking in" message, the sales manager checked the buyer's original lead notes in /builder/leads and saw the buyer had specifically asked about a corner unit with two-side ventilation during their site visit.

The follow-up message referenced that exact preference and offered to hold a matching unit until after the holiday. The buyer replied the same evening, requesting a fresh site visit the following week. The proposal moved from "Stalled" territory to "Site-visit requested" — not because of a faster follow-up alone, but because the follow-up used information already sitting in the lead record instead of a generic nudge.

Building a follow-up cadence that respects the buyer's timeline

A workable cadence for most Indian residential sales cycles looks like this:

• Day 0: Send proposal; confirm delivery.
• Day 1–2 (if Viewed, no reply): Soft, specific follow-up referencing something from the buyer's earlier questions or site visit.
• Day 4–5 (still no reply): A call rather than another message — some buyers respond faster to a voice conversation than to text.
• Day 7+ (Stalled): Reassess: is the price point, unit type, or timeline the blocker? Consider a revised proposal rather than repeating the same one.
• Post-festival check-in: For proposals sent just before a major festival, schedule a dedicated round of check-ins in the days immediately after, rather than assuming the buyer has moved on.

The goal isn't more messages — it's fewer, better-timed ones anchored to what the status view actually tells you.

Pro tips

1. Sort by "Viewed" status first each morning. These are your warmest, most time-sensitive proposals — a buyer who has opened a proposal is actively considering it right now.
2. Never send the exact same follow-up twice. If a first nudge didn't get a reply, the second one should add new information (an updated price, a new unit option, a limited-time offer) rather than just repeating the ask.
3. Cross-check proposal responses against site-visit requests. A buyer who responds with visit-related questions is closer to a decision than one asking only about pricing.
4. Use the dashboard snapshot for weekly pipeline reviews. A sales manager reviewing /builder/dashboard weekly, rather than only when a deal is at risk, catches stalled proposals earlier.
5. Keep NRI-specific proposals flagged separately. Time-zone-shifted response patterns can look like disengagement when they're really just a scheduling gap.

Common mistakes to avoid

1. Treating "Viewed" as a green light to stop tracking. A viewed proposal that goes quiet for a week is a warning sign, not a resolved lead.
2. Following up too aggressively during family-consultation windows. Repeated same-day messages can read as pressure rather than helpfulness.
3. Losing the link between proposal and lead history. Following up without checking /builder/leads first often means repeating questions the buyer already answered on a site visit.
4. Ignoring festive-season timing. Sending three follow-ups during a major festival week is unlikely to get a response and can feel tone-deaf.
5. Not logging the outcome when a proposal closes. Whether a buyer books or declines, capturing why keeps future proposals sharper.

Where this fits with the rest of your DrawMagic workflow

Proposal tracking works best as one link in a chain, not a standalone task. A lead captured through your listing eventually becomes a proposal in /builder/proposals; the proposal's status and response history should feed back into the lead record in /builder/leads so the next interaction — a call, a site visit, a revised offer — starts with full context. Zooming out, /builder/dashboard is where a sales manager sees the whole pipeline at a glance, and a well-maintained public presence on /builders is what keeps new leads entering the top of that pipeline in the first place, sustaining the flow of proposals worth tracking.

Plan-level access to proposal tracking and pipeline views varies by subscription tier — check /pricing for what's included at each level if your team is scaling up proposal volume.

Key takeaways

• Proposal status on DrawMagic moves through distinct stages — sent, viewed, responded, site-visit requested, stalled, closed — each with a different recommended action.
• A "Viewed" status with no reply for several days is the clearest signal that a proposal needs a follow-up, not a reason to assume disinterest.
• Indian buying cycles routinely involve family consultation and multi-visit evaluation, so build a few days of buffer into your follow-up cadence before escalating.
• Festive periods like Navratri and Diwali predictably slow response times — plan a dedicated follow-up push for the days right after, not during.
• Always check the linked lead record in /builder/leads before following up so your message uses context the buyer already shared.
• NRI buyers' responses are often shifted by time zone, not disinterest — factor this into how quickly a proposal is marked stalled.
• Use /builder/dashboard for a rolled-up weekly view of proposals by status across all active listings.
• A consistent, well-tracked public presence on /builders helps keep new leads — and new proposals worth tracking — flowing into the pipeline.

FAQ

How soon should I follow up after a proposal is marked "Viewed"? A gap of 24–48 hours before a soft follow-up is generally reasonable, giving the buyer time to review without feeling rushed — though this should flex around family-consultation timelines and festive periods.

Does a "Stalled" status mean the buyer has lost interest? Not necessarily. It often means the buyer is still deciding, comparing other projects, or waiting on a family conversation. Treat it as a cue to change your approach — a call instead of another message, or a revised offer — rather than writing the lead off.

Can I see proposal responses without leaving the developer portal? Yes — responses tied to a proposal are visible from /builder/proposals, and the same record links back to the full history in /builder/leads for additional context.