How to Configure Your Builder Portal Settings on DrawMagic

A developer in Chennai found out three weeks into a launch that half their enquiries had been landing in a shared inbox nobody actively monitored. Nothing was broken — the leads were arriving exactly as designed. The problem was that when the account was set up months earlier, notification routing was pointed at a general company email address instead of the two sales executives who actually worked the phones. By the time anyone noticed, dozens of consented, ready-to-talk buyer enquiries had gone cold waiting for a reply that never came.

This is the single most avoidable failure mode in any lead-generation platform: the leads show up, but the settings that route them to a human being were never configured, or were configured once and then left untouched as the team grew or reorganized. Portal configuration isn't a one-time checkbox exercise you do on day one and forget — it's the foundation that determines whether your speed-to-lead is measured in minutes or in weeks. This guide walks through setting up notifications, team seats, routing and your public profile on DrawMagic so that doesn't happen to you.

Why Configuration Is the Foundation of Speed-to-Lead

Every enquiry that reaches your builder dashboard has a shelf life. A buyer who fills in a requirements brief and expresses interest in your project is, at that moment, actively evaluating options — theirs and, often, several competing developers' at once. The developer who replies within the hour has a materially different conversation than the one who replies three days later, by which point the buyer has either moved on or lost the urgency that made them enquire in the first place.

Settings are what stand between "the lead exists in the system" and "the right salesperson knows about it in real time." Notification channels determine whether an enquiry reaches someone by app alert, email, or SMS the moment it lands. Working-hours configuration determines whether a night-time enquiry is queued sensibly or fires an alert to someone asleep at 2 a.m., training them to ignore notifications altogether. Team seats and roles determine who can act on a lead versus who only needs visibility. And routing rules determine whether an enquiry about your Chennai project reaches your Chennai desk, not a generic inbox in Bengaluru. Get these right once, thoughtfully, and every enquiry after that flows to the right person automatically — no manual triage required.

According to IBEF's Real Estate Industry in India report (February 2026), India's real estate sector is scaling from roughly US$200 billion in 2021 toward a projected US$1 trillion by 2030, and FY25 delivery volumes rose 33% year-on-year to over 406,000 units. As more developers compete for buyer attention in a fast-growing market, the operational discipline of actually responding to the enquiries you generate becomes a real differentiator — not a nice-to-have.

Step-by-Step: Configuring Account, Notifications, Seats and Routing

1. Start with account and business details. In /builder/settings, confirm your company's registered details are accurate and current — this underpins everything else on the account, including how your identity appears to buyers and how invoices are addressed.
2. Set your notification channels. Choose how you want to be alerted to new enquiries — in-app, email, and where available, SMS or push. Don't rely on a single channel; email alone is easy to miss amid daily inbox volume, while in-app-only alerts can be missed if a team member isn't logged in.
3. Configure working hours. Set the hours during which your sales team is actively monitoring and responding, so notification timing and any auto-acknowledgment messaging can be tuned sensibly rather than firing indiscriminately at all hours.
4. Add team seats and assign roles. Bring on the actual people who will act on leads or manage listings, and assign role-appropriate access — not everyone needs the same level of access to buyer contact details or account settings.
5. Set up lead-routing preferences. If you operate across more than one city or project, configure routing so enquiries about a specific project or region reach the desk responsible for it, rather than a single shared queue.
6. Review and complete your public profile. Head to /builder/profile to make sure your company's public-facing identity — logo, About section, registration identifiers — is accurate, since this is what buyers see before they even reach out.
7. Do a test pass. Where possible, confirm notifications are actually arriving where you expect by checking with the team member who should receive them, rather than assuming the configuration worked.

Settings, What They Control, and Recommended Defaults

What Changes for Multi-City, DPDP-Aware Indian Developers

Multi-city routing. A developer with projects in both Bengaluru and Chennai needs enquiries about each project reaching the desk that actually knows that project and that city's buyer expectations — not a single generalist queue where local context gets lost. Set routing rules by project or region as soon as you have more than one active site, rather than waiting until the confusion has already cost you a lead.

Business identifiers on the account. Indian developers should keep their CIN (Corporate Identity Number), GSTIN, and the RERA registration number for each project state current in their settings and, where relevant, their public profile. RERA numbers in particular are state-specific — a project in Telangana and a project in Karnataka carry different registration numbers, and buyers increasingly expect to see this information stated plainly rather than have to ask for it.

DPDP-era consent hygiene. Under India's evolving data-protection framework, buyer data that flows into your account arrives with the buyer's consent attached to a specific purpose — responding to their enquiry. Keep internal access role-appropriate: a listing-management seat doesn't need the same visibility into buyer contact details as a sales seat actively working that lead. This isn't just good governance — it's the kind of hygiene that keeps a growing developer's data practices defensible as the team scales and more people get account access.

Notification timing tuned to Indian buyer behaviour. Property enquiries in India skew toward evenings and weekends, when working professionals have time to research and reach out. If your working-hours setting is configured for a strict 10-to-6 window, you may be queuing or delaying exactly the enquiries that arrive when buyers are most engaged. Consider extending your active-hours window, or at minimum making sure evening and weekend enquiries are flagged clearly rather than silently queued until Monday.

NRI buyers need more than a phone number. An NRI buyer evaluating a project from a different time zone may not be able to take a call during your team's working hours at all. Make sure your public profile and settings surface an email or messaging channel prominently, not just a phone number, so time-zone-mismatched enquiries still have a clear path to a response.

Mini Scenario: Routing Leads for a Two-Region Developer

A developer with an active project in Bengaluru and a newer launch in Coimbatore initially ran both through a single sales inbox managed by one coordinator in Bengaluru. Coimbatore enquiries were getting the same response templates and, worse, occasional confusion about site-visit logistics because the coordinator wasn't familiar with the Coimbatore project's specifics.

The fix was straightforward once identified: in /builder/settings, the team set up region-based routing so Bengaluru enquiries went to the existing coordinator and Coimbatore enquiries routed directly to the two-person team based there, who had proper project familiarity. They also staggered working-hours settings slightly to reflect that the Coimbatore team preferred to start responses a little later in the morning. Enquiry-to-first-response time for the Coimbatore project improved almost immediately, simply because the right people were seeing the right leads without a manual forwarding step in between.

Building an Accurate Public Profile

Your profile at /builder/profile is often the first thing a buyer checks after seeing your project listing — before they decide whether to enquire at all. Treat it as a factual company record, not a marketing pitch:

• State your company's history, project portfolio, and registration details plainly — CIN, relevant RERA numbers, and years of operation.
• Keep your logo and visual identity current and consistent with your actual branding.
• Never describe your own company or projects using words like "verified," "best," "guaranteed," or "certified" — these are claims DrawMagic doesn't make on a builder's behalf, and using them undermines the credibility of a profile that's supposed to read as trustworthy documentation, not self-promotion.
• Update the profile whenever something material changes — a new project, a change in registered address, a new regional office — rather than letting it go stale for years.

Pro Tips

1. Enable multi-channel alerts from day one. A single point of notification failure is the most common reason leads go cold.
2. Set working hours to match reality, then extend for peak enquiry windows. Indian buyer enquiry activity skews evening and weekend — configure accordingly rather than defaulting to standard office hours.
3. Review team roles quarterly. People join, leave, and change responsibilities; a role assigned correctly six months ago may no longer match who's actually handling that desk today.
4. Route by project or region as soon as you have more than one active site. Don't wait for a routing failure to prompt the change.
5. Audit your public profile every time you update a project. A profile that's accurate for your first project but stale for your third undermines trust exactly when a new set of buyers is looking at it for the first time.

Common Mistakes to Avoid

• Relying on a single notification channel. Email-only or app-only alerts are one missed check away from a cold lead.
• Leaving contact details stale after a team change. A departed employee's email still receiving enquiry alerts is a silent failure mode nobody notices until a buyer complains about no response.
• Over-broad access for every seat. Giving every team member full account access, including billing and settings, creates unnecessary risk without any operational benefit.
• Using a single shared queue for a multi-city operation. This is the most common cause of slow, low-context responses to region-specific enquiries.
• Writing self-superlative profile copy. Claims like "the most trusted developer in the city" don't belong on a factual company profile and don't align with how DrawMagic frames builder-provided information — state your registration facts and let buyers draw their own conclusions.

How This Fits With the Rest of DrawMagic

Settings and profile configuration are the connective tissue between your project listings and your actual sales operation. Once notifications, roles and routing are configured properly, every enquiry that reaches your builder dashboard flows to the right person automatically, and your public presence on /builders accurately represents your company to the buyers evaluating you. This groundwork also makes everything else in the portal — subscription sizing, project listings, lead management — work the way it's meant to, because the plumbing underneath it is solid.

Value Note: A Configured Portal Means Fewer Missed Leads

The value of good configuration is almost entirely defensive: it doesn't generate new enquiries, but it stops the enquiries you're already generating from silently failing to reach anyone. For most developers, the cost of a missed lead — a buyer who enquired, got no timely response, and moved to a competing project — is far higher than the ten minutes it takes to set notification channels, working hours, and routing correctly. Treat portal configuration as an operational investment with a near-immediate payback, not an administrative chore to defer.

Key Takeaways

• Configure notifications, working hours, team seats and lead routing in /builder/settings before you rely on the account for a live launch — not after leads start slipping through.
• Enable at least two notification channels so a single missed alert doesn't mean a missed lead.
• Set working hours to reflect Indian buyer behaviour, which skews evening and weekend, not standard office hours.
• Route enquiries by project or region as soon as you operate in more than one city — a single shared queue loses local context fast.
• Keep CIN, GSTIN and state-specific RERA numbers current on your account and public profile.
• Practice DPDP-era consent hygiene: keep internal data access role-appropriate rather than uniformly open.
• Build your public profile at /builder/profile as a factual record — no self-superlatives, just accurate registration and portfolio details.
• Give NRI and outstation buyers an async contact channel like email, not just a phone number tied to your working hours.
• Review team roles and routing quarterly as your team and project portfolio change.
• A well-configured portal doesn't generate leads — it stops the leads you already have from going cold.

FAQ

How often should I revisit my portal settings? Review notifications and routing whenever your team or project portfolio changes, and do a full review at least quarterly even if nothing obvious has changed — settings that were correct on day one drift out of date as teams grow.

Can different projects have different routing rules? Yes, that's the point of region/project-based routing in /builder/settings — set it up as soon as you have more than one active project or city.

Does my public profile affect how buyers perceive my company? It's often the first thing a serious buyer checks before enquiring, so keeping /builder/profile accurate and current matters — but it should read as a factual record, not a marketing claim.

Is DrawMagic responsible for verifying the details on my profile? No — DrawMagic is a software and information platform; builders are responsible for the accuracy of their own company and project details. Present facts with sources or registration references, not unverifiable superlatives.

Start by opening your builder dashboard to see how enquiries are currently flowing, then head to /builder/settings to configure notifications, seats and routing properly — and finish by giving your public profile a review so it reflects your company accurately.