NewRMDialer is now on iPhone as well as Android · every feature except the call log
RMDialer is a MagicBricks CRM integration for brokers: each MagicBricks enquiry email is parsed and posted to RMDialer, labelled, and handed to a broker.
No direct MagicBricks feed · A 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 MagicBricks through the enquiry email. Set up an RMDialer webhook with the name “MagicBricks enquiries”, add a mail rule that sends MagicBricks emails to an email-parsing service, teach the parser where the enquirer’s name and mobile are, and set it to post to the webhook URL. Each enquiry then lands in RMDialer with MagicBricks as its source and goes round robin to your brokers. Housing.com and 99acres follow the same pattern with a rule and a webhook each, so one inbox can feed all three. RMDialer has no direct MagicBricks feed; the parser needs a check whenever an email layout changes.
Key takeaways
A mail rule per portal keeps them apart all the way into RMDialer, so every lead carries its portal and reports stay honest.
| Portal | Mail rule | RMDialer webhook |
|---|---|---|
| MagicBricks | Mail from MagicBricks goes to parser mailbox A | “MagicBricks enquiries” |
| Housing.com | Mail from Housing.com goes to parser mailbox B | “Housing enquiries” |
| 99acres | Mail from 99acres goes to parser mailbox C | “99acres responses” |
MagicBricks
Mail from MagicBricks goes to parser mailbox A
Webhook: “MagicBricks enquiries”
Housing.com
Mail from Housing.com goes to parser mailbox B
Webhook: “Housing enquiries”
99acres
Mail from 99acres goes to parser mailbox C
Webhook: “99acres responses”
Make one RMDialer URL per portal, then paste the MagicBricks one into the parser mailbox that receives MagicBricks emails, as its webhook destination.
Step 1
Create the URL
In the RMDialer Web CRM, open Custom Webhook and name it, for example “MagicBricks enquiries”. 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 number alone makes for a slow first call. Four fields make it a short one.
Rental and sale enquiries need different first questions. A field saying which one it is lets the caller open right.
Locality and the listing title, so the caller does not ask “which flat?” on the first call.
Ask it on the first call and save it; tenants moving next month get called first.
Rent or price range, as a custom field the team can filter before a dialing session.
A composite rental agency; every figure here is illustrative.
Picture a rental agency in Whitefield with forty flats listed for IT professionals on MagicBricks and Housing.com. Tenant enquiries peak on Sunday afternoons and Monday mornings. The two agents used to scroll the shared inbox between viewings, and enquiries from Sunday were often answered on Tuesday, after the tenant had signed elsewhere.
The agency sets two mail rules and two RMDialer webhooks, “MagicBricks enquiries” and “Housing enquiries”, both shared round robin between the agents. Each enquiry lands with the flat’s locality; on the first call the agent asks move-in date and budget and saves them. Tenants moving within a month get a viewing slot and a reminder the evening before.
At month end the owner compares the two portals by viewings booked, not enquiries received, and moves listing spend towards the one whose tenants actually showed up.
The 99acres version of this setup, with a parser comparison, is on 99acres CRM integration. Calling property enquiries well is covered on telecalling CRM for real estate, and every other 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.
They go through one extra link: the MagicBricks enquiry email. A mail rule passes each email to a parsing tool, which you show once where the enquirer’s name and mobile appear; the tool then posts every enquiry to your RMDialer webhook. After that, each MagicBricks enquiry lands in a broker’s list without anyone copying it.
It integrates through the enquiry email and a parser, not a direct MagicBricks feed. That route works for any MagicBricks advertiser who receives enquiries by email. Should MagicBricks ever offer your account a lead push to a web address, point it at the RMDialer webhook and the parser can go.
Yes. Keep one broker inbox and add a mail rule per portal that forwards its emails to a separate parser mailbox. Each parser posts to its own RMDialer webhook, so every lead arrives labelled with its portal and can go to a different set of brokers if you like.
Yes, on the same pattern: forward Housing.com enquiry emails to a parser mailbox of their own and post them to an RMDialer webhook named for Housing.com. Test with a few real Housing.com emails, since each portal lays out its alerts differently.
Add a field for tenant or buyer, and ask move-in timing and budget on the first call. Save them as custom fields in RMDialer so the desk can filter before a session and call tenants moving next month before those just browsing.
Yes, when the listed number rings on a phone running RMDialer. Because RMDialer is the phone app, the call is logged with its time and duration, and the broker can save the caller as a lead with MagicBricks as the source while the details are fresh.
The enquiry does not reach RMDialer until the rule is fixed. Parsers show failed emails on their dashboard; check it weekly, adjust the rule when MagicBricks changes its email layout, and reprocess the failed ones so no enquiry is skipped.
Yes. Every RMDialer webhook is assigned to the brokers you pick, so a project’s webhook only feeds that project’s team. Split the emails by project with a parser rule or mailbox per project.
Yes. When the status becomes Site visit booked, set a follow-up reminder for the evening before; it rings on the broker’s phone with the enquiry’s details. A WhatsApp with the location pin can go out at the same time.
Each broker seat is ₹159 a month when paid for the year, GST on top, and the webhooks come with it at no charge. Budget separately for the parser and for your MagicBricks package.
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.
