Dialer, Call Logs and Leads APIs From RMDialer

No. The app is proprietary. What is open, under the MIT licence, is the integration material: sample pages, lead-source scripts and API payload examples, so you can copy them into your own project.

No. A public Google Sheet or any GET endpoint returning a JSON array works as a lead source straight from the app, with no credentials on our side. The API is for reading calls and leads back out, and for pushing assignments.

In the RMDialer Web CRM, open Setup, then Outbound API: it shows your base URL and API token. The call log API reference lists every parameter and response field.

Yes. Every brand published on the platform talks to the same backend and the same API, so one integration covers RMDialer and any brand you run on it.

Any. Numbers with a country code keep their country; bare local numbers get the country you set on the source; leading zeros are treated as trunk prefixes. Rows whose number cannot be made valid are listed as skipped, not silently dropped.

Yes, in two ways. The simplest: point the app at your CRM's lead export (Google Sheet or REST endpoint) so leads flow in and get dialled. The full way: use the dialer API so calls, statuses, remarks and WhatsApp events flow back into your CRM by webhook, with leads and assignments pushed the other way.

Yes. Save the sheet as Excel or CSV with a mobile number column (name and any other columns are optional), import it in the app, and start a session. The dialer calls the rows in order and lets you mark each outcome. The same works from a Google Sheet, which can also be connected as a live source so new rows import themselves.

Import or connect the lead source once, then turn on round-robin assignment: each new lead goes to the next active employee in rotation, their phone pings, and the lead appears in their assigned queue with the auto dialer ready. Managers can reassign or transfer a lead any time and the transfer history stays on the record.

Tag every lead with its source when it arrives (Facebook, JustDial, IndiaMART, website, referral, walk-in) and let the calls carry that tag through to the outcome. The analytics then show calls, connects and won or lost per source, so you can see which platform produces buyers rather than enquiries and move budget there.

Connect the Google Sheet that Facebook writes leads into as a lead source. Rows are checked on a schedule you set, every 30 minutes by default, then de-duplicated and tagged with the source, so the enquiry reaches a rep's calling queue the same hour instead of waiting in a spreadsheet until someone exports it. Connect the same sheet under Live Sheets in the Web CRM to share new rows across your callers in turn.

Yes. Export or connect the portal's lead list (most portals email or expose leads by sheet or API), let the app import new enquiries on a schedule, and set the fresh leads to auto dial first. Speed to lead is what wins portal enquiries: the first supplier to call usually gets the order.

Yes, when the dialer on the phone provides one. RMDialer's call logs API streams every call on each user's SIM (direction, duration, outcome, the lead, the remark, the follow-up) to your own system by REST and webhooks, and accepts leads and assignments back. Working samples are open on GitHub.

One that runs on the phone, because property selling is calling: portal leads from 99acres, MagicBricks and Housing imported and called within minutes, the buyer's budget and location on the call screen, site-visit reminders that ring, and the brochure sent on WhatsApp after the call. A desktop CRM that brokers stop opening does not help.

An auto dialer app calls a list of phone numbers one after another so the caller never types a number. On Android, an app like RMDialer runs the session on the phone itself using the SIM already in it: you pick a list from Excel, a Google Sheet, an API or assigned leads, press start, and the app dials each number in turn while you mark the outcome between calls.