How to handle portal and Meta leads in one calling queue

Put every source into one list and call it in one order. Meta lead ads can flow in on their own: connect your Facebook Page once, and each new lead is called as soon as it arrives, inside your calling hours. Portal leads from 99acres, MagicBricks and Housing.com usually arrive as spreadsheet exports, so upload each export as soon as you download it, as a named batch; an uploaded batch is spread across the morning and afternoon calling slots. Then remove duplicates by phone number, keep the source on every lead, call fresh enquiries before old ones, and let the first call sort out the junk.

This post is part of our guide to AI lead qualification for Indian real estate.

Why one queue

Most developers and brokers run several lead sources at once, each with its own sheet, its own owner and its own idea of who calls first. The result is predictable: some buyers get two calls in ten minutes from the same company, and others get none.

One queue fixes three things at once. Every lead is called by the same rules. Nobody is called twice for one enquiry. And every result can be compared by source, which is the only way to know what your ad money buys.

Meta lead ads: connect once

Connect your Facebook Page from the BlackWolf dashboard. From then on, new leads from your lead forms arrive the moment they are submitted, marked as Meta leads, and each one is called as soon as a line is free, once calling is switched on for your workspace and inside your calling window. There is no export to download and nothing for anyone to remember, which is why Meta is usually the fastest source to call. The speed to lead advantage comes for free.

This connection is new in BlackWolf: it is built, and its first live client connection is still to come.

Meta's standard fields (name, phone and email) land in the lead's own fields. Answers to your own form questions, such as preferred configuration or budget band, come through as notes on the lead, so they are not lost. If Meta delivers the same lead twice, it is stored once.

Keep the form short. The call will ask the rest, in conversation, which is a better way to learn a budget than a drop-down.

Portal leads: export, then upload

Leads from 99acres, MagicBricks and Housing.com usually leave the portal as a spreadsheet. The import is built for those files as they come:

• Up to 5,000 rows per upload. Split larger files and upload the parts.
• Columns are recognised by name. "Mobile", "Contact No" and "Phone Number" all read as the phone. "Locality", "Location" and "Project" read as the locality. "Budget" and "Price Range" read as the budget. "BHK", "Configuration" and "Unit Type" read as the configuration.
• First and last names are joined. Portals often export them as two columns. Importing only the first would file every buyer under half their name.
• Title rows are skipped. An export with a banner or a timestamp above the real header row still imports.
• One bad row does not sink the file. Rows with a problem are listed with their row number and the reason. The rest go in.
• Name the batch. When you upload, give the batch a name, such as the portal and the date. Import is the only moment anybody knows what the file is.

The scientific-notation trap

Open a portal export in Excel, save it, and a phone number like 919876543210 can come back as 9.19877E+11. Only six digits survive. Expanding that gives 919877000000, which looks like a valid number and belongs to a stranger.

So the import refuses a mangled number instead of guessing it, and says why. The fix is on your side: format the phone column as Text before you save, or upload the file exactly as the portal exported it.

Deduplication

A buyer who enquired on two portals and through your Meta ad is one person, and should get one call.

• Inside one file, a repeated phone number is reported and imported only once.
• Across files and sources, match rows before you upload. Use the last ten digits of the mobile number, because the same number arrives as +91 98201 34567, 09820134567 and 9820134567 depending on the source.
• Keep the earliest enquiry's source, and note the others. The first touch matters when a channel partner later says the buyer was theirs.

One duplicate matters more than the rest: a number that asked not to be called. Every number is checked against the suppression list before it is dialled, so an opted-out buyer is never rung again, even when they reappear in next week's export.

Tag every lead with its source

A lead without a source is a lead you cannot learn from. If your export has a "Source" or "Lead Source" column, it is read. If not, the lead is marked as an import, and the batch name tells you which one. Meta leads are marked automatically.

With sources in place, you can see per portal and per campaign what matters: how many leads were reached, how many qualified, how many booked a site visit. Divide what you spent by qualified leads and you have the cost per qualified lead for each source, which can rank your sources very differently from cost per lead. More on that in cost per qualified lead.

Calling order

When the queue is long, order decides who gets called while they still remember enquiring.

1. Commitments first. A buyer who asked to be called at 4 pm, and a site visit that needs confirming, come before anything new.
2. Fresh enquiries next. A Meta lead from ten minutes ago, then this morning's portal export.
3. Backlog last. Last month's portal leads go in as their own named batch. BlackWolf works through an uploaded batch from the next calling slot, as lines come free, rather than dialling it all at once. They have waited weeks; they can wait until the fresh leads are called.

The first call itself is the start of lead qualification: it should name your company, mention the buyer's own enquiry and ask whether now is a good time.

After the call, one record per buyer

Whatever the source, the lead looks the same once the call ends: name, budget, configuration, locality, timeline, sentiment and a short summary, with the full transcript and the recording. A sales person picking it up does not need to know which portal's column names it arrived with. If your leads come from DaeBuild, call outcomes can also be written back to the same records there. Other CRMs are not connected today, so for portal and Meta leads the BlackWolf dashboard is the place your team works them.

A seven-day clock on enquiries

TRAI notified the Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026 on 18 September 2026 (the notification (PDF), opens in a new tab). They amend the TCCCPR definition of "Relationship", which the regulations use for inferred consent. An enquiry counts when it was submitted "within seven days immediately preceding the date of the receiving of communication". It must also be "made in writing or through digital means, and shall be maintained in a verifiable form by the Sender".

The amendment comes into force thirty days after it is published in the Official Gazette. For portal and Meta leads, two consequences follow:

• Keep the evidence. The portal export and the Meta lead record are your written, digital record of each enquiry. Keep the original files after you import them.
• Call inside the week. Speed was a sales advantage; for enquiries it becomes a question of consent too. Once the amendment is in force, an enquiry older than seven days no longer gives you that basis on its own. Ask your compliance adviser what does before you run an old list.

This is a summary as of September 2026, not legal advice. Our TRAI TCCCPR guide covers the regulations in full.

Junk leads

Every source produces some: wrong numbers, names like "test", people who say they never enquired, brokers posing as buyers, competitors checking your prices. Filtering too hard before calling throws away real buyers with lazy form habits. Remove the obviously unusable rows, such as blank numbers, and let the first call sort the rest:

• "I never enquired." The agent apologises, does not argue, and asks once whether they would like to hear about the project anyway. A no ends the call politely.
• "Where did you get my number?" The true answer: from the enquiry they made on the portal or the form. Never "from a database".
• "Do not call me again." The number goes on the suppression list the moment it is said.
• A broker, not a buyer. Note it and pass it to whoever handles partners.
• A number that never connects. Check it against the original export. It is a data problem, not a calling one.

Track junk by source. A portal whose leads are mostly wrong numbers is a conversation to have with your account manager, backed by your own records.

What stays with you

Importing a list does not change who is responsible for calling it. Registration on a DLT platform, the number series TRAI designates for commercial calls, and scrubbing your lists against the national NCPR register stay with you, through your own DLT access. BlackWolf checks its own suppression list before every dial, which is a different thing. We explain the difference in DND and NCPR explained, and the real estate page shows the whole lead flow.

What to do next

Take one week of exports from every portal and your Meta form, match them on the last ten digits of the phone number, and count the duplicates. That number is how many wasted calls a single queue saves you every week.