NewRMDialer is now on iPhone as well as Android · every feature except the call log
RMDialer handles 99acres CRM integration through the response alert: a parser reads each 99acres email and posts the buyer to a broker’s list.
No direct 99acres feed · An email parser is the link
Your own SIM, no virtual number · Android and iPhone apps + Web CRM in one plan · No card for the trial
Updated
Short answer
RMDialer connects to 99acres through the response alert email. Open a webhook in RMDialer called “99acres responses”, set a mail rule that forwards every 99acres alert to an email-parsing service such as Mailparser, Parseur or Zapier Email Parser, teach the parser where the buyer’s name, mobile and listing sit, and point it at the webhook URL. Each response is then posted to RMDialer, mapped and shared round robin across your brokers, and because RMDialer replaces the phone’s dialer, a buyer who rings your listed number shows up in the call log too. RMDialer does not hold a direct 99acres feed; the parser is the link, and it needs a check whenever 99acres changes its email layout.
Key takeaways
Four links, set up once. After that nobody copies a number from an email again.
Link 1
99acres sends you the response, usually as an email alert to the address on your advertiser account.
Link 2
Set a forwarding rule in Gmail or Outlook that sends 99acres alerts to an email-parsing service such as Mailparser, Parseur or Zapier Email Parser.
Link 3
You teach it once where the buyer’s name, mobile number and the listing or locality sit in the email. It repeats that for every later alert.
Link 4
Each parsed response is posted to your RMDialer webhook URL, mapped, and handed to the next caller in the round robin.
Three services that can post parsed results to a URL. Each has its own plan; test with real 99acres alerts before choosing.
Create the URL in RMDialer, then paste it into your email parser as the webhook or HTTP destination for parsed 99acres alerts.
Step 1
Create the URL
In the RMDialer Web CRM, open Custom Webhook and name it, for example “99acres responses”. The name is also the source on any lead that arrives without one. You can edit the webhook later; the URL stays the same and leads keep arriving while you do.
Step 2
Capture a test
Send one test lead from the parser as JSON, the format the webhook accepts. The page waits and shows the request the moment it lands. Nothing is imported from it until the fields are mapped.
Step 3
Map its fields
Every field in the request is listed with a sample value, nested ones as paths such as lead.name or utm.utm_source. Pick which is the phone, the name, the city or the source, ignore the rest, or add a new field with +.
Step 4
Assign
Choose a product, then share the leads round robin across all employees or only the ones you tick. For a number you already hold, the request can update that lead instead: only the mapped fields that have a value, with the old version kept in the lead’s history. It never makes a second lead.
A hypothetical Pune office with realistic listing volumes; no real broker is described.
Picture a resale and rental broker in Baner, Pune, with about sixty listings on 99acres and three field brokers. Responses arrive by email through the day, and each evening the owner forwarded screenshots to the brokers on WhatsApp. By the time a 2BHK buyer was called back the next morning, they had seen three other flats.
The owner sets one Gmail rule for 99acres alerts, a Parseur mailbox that picks out the buyer’s name, mobile and the listing’s locality, and an RMDialer webhook called “99acres responses” with the three brokers in its round robin. A response to the Baner 2BHK now lands in a broker’s list with the locality beside the number; the first call goes out from the broker’s own mobile, and a site visit becomes a status with a reminder for the evening before.
When 99acres adjusted its alert layout one month, the parser showed failed emails on its dashboard. The owner updated the rule in ten minutes and reprocessed the failed emails, so no response was lost.
Running MagicBricks as well? The same setup with its own webhook is on MagicBricks CRM integration. The wider portal routine is in connect portal leads to your dialer, and every source is on the integrations page.
Every source lands in the same lead list and is called from the same SIM. The full list, with the four ways in, is on the integrations page.
Yes, through the 99acres alert email. Forward those alerts to an email-parsing service, teach it where the buyer’s name, mobile number and listing sit, and have it post each response to your RMDialer webhook URL. From then on every 99acres response reaches a caller without anyone copying it.
Not a direct feed. Some CRMs advertise direct 99acres integrations; RMDialer uses the alert email and a parser instead, which works for any advertiser account that receives 99acres alerts by email. If 99acres gives your account a way to post leads to a URL, paste the RMDialer webhook there instead.
Any parser that can send its results to a webhook: Mailparser, Parseur and Zapier Email Parser all can. Pick one on price for your monthly response volume, and test it on three or four real 99acres alerts before switching the forwarding rule on for good.
The parser may stop finding the mobile number, and responses will stop arriving in RMDialer. Check the parser’s dashboard for failed emails once a week and update the rule when the layout changes. The alerts still reach the parser, so once the rule is fixed you can reprocess the ones that failed.
Yes, if the number on your listing rings on a phone running RMDialer. It is the phone app, so an incoming call from a 99acres buyer is logged with its time and length, and the caller can save the buyer as a lead with 99acres as the source during or after the call.
Give each portal its own RMDialer webhook, such as “99acres responses” and “MagicBricks responses”. Leads without a source of their own are filed under the webhook’s name, so you can filter and report by portal and see which one brings site visits.
Each webhook has its own list of employees in its round robin. Use separate parser rules or mailboxes per project if your team splits work that way, each posting to a webhook assigned to that project’s brokers.
Soon: a buyer responding on 99acres is often comparing several listings the same evening. With the parser route, the response reaches the assigned broker once the alert is parsed and posted, and the RMDialer auto dialer rings the day’s new responses one after another from the broker’s own number.
Yes. RMDialer can send a WhatsApp after a call or when the lead’s status changes, such as the brochure and location pin when the status becomes Site visit booked. Use templates approved for your WhatsApp account and keep to buyers who responded.
A 99acres setup has three costs: your 99acres listings, the parser’s monthly plan, and RMDialer seats at ₹159 each per month on annual billing, taxes extra. The webhook itself adds nothing.
The business dialer is free forever with no account and no expiry: the keypad, contacts, caller ID, the call log and your call analytics, plus free WhatsApp sends every day. A plan adds the customer record after every call, follow-up reminders, list auto dialing, your team and WhatsApp automation.
Free WhatsApp sends every day with a free account: 15 a day for your first 15 days, then 3 a day. The dialer itself needs no login at all.
Try it free for 3 days: unlimited use, no credit card required.Prices are per user, exclusive of taxes.
Set it as your phone app in one tap. Everything works like before, and then it starts working FOR you.
₹159/user/month on yearly · every feature included · Prices are per user, exclusive of taxes.
Free forever: the business dialer never expires, and needs no account
Call recording supported · our team sets it up with you during training
On iPhone and Android. The iPhone app has every feature except the native call log.
