RMDialer, the auto dialer for leads, turns ad leads, web forms, portal enquiries and sheet rows into one queue that rings itself, and records how fast each lead was called.
Facebook lead ads, website forms, Google Sheet, any REST API, portals · Whole app free for 3 days, nothing to pay up front
Your own SIM, own Android phone, no virtual number · Mobile app + Web CRM in one plan · No card for the trial
Short answer
An auto dialer for leads turns the enquiry pile, ad leads, web forms, portal enquiries and sheet rows, into a queue that rings itself on a caller's phone. RMDialer pulls leads from a linked Google Sheet or any REST API, rings each one from the phone's own SIM, asks for the outcome in two taps, sets the callback, sends the WhatsApp, and shows leads by source and by caller in the Web CRM.
Key takeaways
Leads arrive in five places and get called from none of them. Six cards on the pile, the queue, the first-call time and what follows the call.
Ad leads, web forms, portal enquiries and sheet rows arrive all day in different places. An auto dialer for leads turns that pile into one queue on a caller's phone.
The caller presses start once. Each fresh lead rings in turn from the phone's own SIM, with a gap of a few seconds, and nobody copies a number out of an email.
A lead that filled a form is thinking about you now, not on Thursday. The gap between arrival and the first ring is what an auto dialer for leads exists to shrink.
Interested, not now, wrong number, call back at a time, booked. Two taps after the call, and the next lead rings. The answer is what moves the queue.
"Call me after six" becomes a reminder on the caller's phone at six, with the lead's name and what they asked for. Promised callbacks stop living in memory.
A template with the price list, the brochure or the booking link goes on the official API as the call ends, so the lead has something in hand while they are still interested.
Real businesses, real numbers: how owners and sales teams across India and 12+ countries use RMDialer every day.
“Telecaller software that my counsellors actually open, because it is the phone app itself. Demo bookings from the website land in the queue, get dialled the same hour, and the WhatsApp with the course link goes out after each call. Four stars: the Excel import wanted the number column named exactly, so my first upload took two tries.”
“Earlier I was dialling 80 to 100 portal leads a day by hand from Excel. With RMDialer auto dialer app I import the sheet, press start and it calls one by one from my own Jio SIM. Between calls I mark Interested or Site visit in two taps and the follow-up rings me on time. Closed 3 flats last month from leads I would have forgotten.”
“We tried two telecalling CRM software before this and my counsellors stopped filling them within a week. RMDialer is the phone app itself, so every admission enquiry gets logged whether they like it or not. The auto WhatsApp after call sends the fee structure by itself. I see all 4 counsellors' calls on the web CRM every evening.”
“For a clinic the win is call management: every missed call at the front desk becomes a call-back reminder, and the patient's last visit remark shows when they ring again. Appointment reminders go on WhatsApp automatically. Our no-shows dropped noticeably in two months.”
“We connected our website form and a Google Sheet as lead sources. New sign-ups appear in RMDialer within 15 minutes, get assigned round robin and dialled the same hour. Speed to lead went from a day to under an hour, and demo bookings roughly doubled. The call logs API pushes everything back into our own dashboard.”
“Arabic auto dialer and CRM app on our Vodafone SIMs. Showroom enquiries are followed up on time, the WhatsApp catalogue goes after every call, and I see each salesperson's calls for the day. Cheaper than any call centre product we were quoted and no virtual numbers customers ignore.”
Reviews are collected from customers on WhatsApp and on this website. Share yours on WhatsApp
Within minutes, and here is what those minutes contain. One lead, from the form to the manager's screen, with round times as an illustration.
0 min
Someone taps a Facebook lead ad, fills a website form, enquires on a portal, or a row lands in a Google Sheet. The lead exists, and a timer nobody can see has started.
1 min
The lead is in RMDialer: pulled from the linked Sheet or posted through the REST API, with its source, its name, its number and whatever it asked for.
2 min
It sits at the top of a caller's queue. If the pile is split between four callers, it is in exactly one of their phones and nobody else's.
5 min
The phone rings it. The lead sees a normal mobile number, not a call-centre line, and the caller sees the form answers on screen before the lead says hello.
8 min
The outcome sheet: interested and booked, wants a callback at seven, not reached. Two taps. The arrival time and the first-call time are both on the record now.
9 min
The WhatsApp template goes: the price list or the booking link, from the same number that just called. The next lead rings.
60 min
The marketing manager opens the Web CRM and sees the hour's leads by source and by caller: how many arrived, how many were rung, how fast, what they said.
The hour is short because nothing in it is typed. The lead is not copied from an email into a spreadsheet and then into a phone; it arrives in the queue with its source and its form answers, and the caller's only work is the conversation and two taps. That is the whole difference between an auto dialer for leads and a good intention to call people back.
Six places leads come from, how each reaches the queue, and one thing worth knowing about each.
| Source | How it reaches the queue | Worth knowing |
|---|---|---|
| Facebook lead ads | Send the lead ad results to a Google Sheet or post them to the REST API; RMDialer pulls the new rows into the queue. | Form answers travel with the lead, so the caller knows which ad and which offer. |
| Website forms | A form that writes to a Sheet, or a site that posts to the API. Either way the enquiry is dialable minutes after submit. | The page the form was on can ride along as a field, which tells the caller what to open with. |
| Google Sheet | Link the Sheet once. Every new row becomes a lead; the source column, if you keep one, becomes the source in the Web CRM. | The simplest route for a small team, and the one most ad platforms already support. |
| Any REST API | Your own software, a CRM or a form tool posts the lead directly. The call logs API sends the results back the other way. | How CRM leads reach the phones: through the API or a linked Google Sheet, never a copy-paste. |
| Property, education and trade portals | Portal enquiries usually export to a Sheet or offer an API; connect whichever the portal gives you. | Portal leads go cold fastest, because the same enquiry went to five businesses at once. |
| Assigned queues | A manager splits the pile between callers in the Web CRM. Each phone holds only its share. | A lead handled on one phone leaves every other queue, so no lead is rung twice in a morning. |
Two routes cover all of it: a linked Google Sheet, which nearly every ad platform, form tool and portal can write to, and the REST API, for anything with a developer behind it. RMDialer does not have a native button inside other CRMs; it has those two doors, and every source above walks through one of them.
Three things, and all three are quiet. The Web CRM makes the third one loud by showing the leads with no first call next to the ones with one.
The person who filled a form at ten was comparing three options at ten. By four they have spoken to one of the others, and by tomorrow the form is a vague memory.
An uncalled lead in an inbox or a Sheet has no status, so nobody knows it is uncalled. It looks exactly like a lead somebody is handling.
Every lead had a price on the ad platform. A lead nobody calls is that money spent for a phone number that will never be dialled.
The first call is where most lead tools stop. Six things that happen next, each of them without anyone remembering to do it.
The outcome sheet uses the statuses your team set up, so a dental chain sees consultation booked, not a generic "interested".
Promised callbacks ring at the promised time. A lead who said "Saturday morning" is rung on Saturday morning without a diary.
The template goes on the official API after the call. The lead replies to a number they recognise, and the reply sits on their record.
Leads that did not pick up stay in the list as their own group, worked again in the evening when more of them answer.
When a caller leaves, their leads and every remark are moved to somebody else from the Web CRM. Nothing walks out with the phone.
The Web CRM shows how many leads each source sent, how many were rung, how fast, and what each caller did with them.
Per caller, not per lead. Two currencies, one product, and the manager's Web CRM included.
A month of 400 leads costs the same seats as a month of 40. The calls go on each caller's own SIM, so the only airtime is the plan the phone already has. Making ordinary calls needs no account and costs nothing, and three trial days switch on the whole app for the team before any payment, with no card asked for.
When the year is paid at once. Paying three months at a time makes it ₹249 a month, and taxes are added. The seat holds the queue, the outcome sheet, reminders, the WhatsApp template and the Web CRM view of leads by source and caller.
Three months at a time is $12 a caller, in dollars. Four callers for a year come to $116, and the marketing manager who only reads the Web CRM needs no seat.
Prices are per user, exclusive of taxes. Leads from a Sheet or the API carry no extra charge.
An illustration with round numbers: four clinics, one marketing manager, four front-desk callers, and a Facebook campaign for implants and whitening.
Picture a dental clinic chain in Jakarta with four clinics from Kemang to Kelapa Gading and a marketing manager who spends the ad budget on Facebook lead ads for implants and teeth whitening. About 400 leads a month come in. They arrive in the ad platform, get exported to a Sheet twice a week by an intern, and are emailed to the four front desks, who ring them between patients. The manager knows the cost per lead to the rupiah and has no idea how many were ever rung.
She links the lead ad Sheet to RMDialer once. From then on every new lead lands in the queue within minutes, tagged with the campaign and the clinic the person chose on the form, and split between the four front-desk callers by clinic. The caller in Kemang sees a Kemang implant lead ring on her phone, from the clinic's own number, with the form answers on screen, while the lead is still looking at the ad.
The outcome sheet uses the statuses the chain chose: consultation booked, wants price on WhatsApp, call back at a time, not reached. A "call back after work" rings the caller at six. The whitening price list goes as a WhatsApp template from the clinic number as each call ends, and the replies land on the lead's record. Leads that did not answer are rung again at seven, when Jakarta traffic has delivered people home.
At the end of the month the manager opens the Web CRM and reads leads by source and by caller: 412 leads, 380 rung, an average of eleven minutes to the first call, 96 consultations booked, and Kelapa Gading letting leads wait an hour longer than the others. She moves budget toward the implant campaign, which books at twice the rate, and has a word with one front desk. Four seats for the year is $116; the intern never exports a Sheet again.
A marketing manager watching a cost-per-lead figure types "auto dialer for new leads" because new is the word that worries her. A front-desk caller writes "lead calling app" because calling is the job. An owner in India or the Gulf says "auto dialer for enquiries", since enquiry is the everyday word for the same person. A sales lead writes "lead dialer" and leaves it at that. Each of them wants the pile turned into a queue that rings itself, and that is what this page covers.
You will also see it called lead dialer, auto dialer for new leads, lead calling app, auto dialer for enquiries, dialer for leads and auto dial leads. They describe the same thing, so whichever phrase brought you here, this is the page for it.
Split the lead pile between callers in the Web CRM, by count or by hand. Each phone shows only the leads with that caller's name on them.
Link the Google Sheet the ad platform writes to, or point your form tool or CRM at the REST API. New leads arrive on their own from then on.
The Web CRM shows what each source sent, how quickly each lead was rung, and what every caller did with theirs, for the day or the month.
It puts every new lead into a queue on a caller's phone and rings them one after another, so the time between a form being filled and a phone ringing is minutes rather than a day. In RMDialer the lead arrives from a linked Google Sheet or the REST API with its source and its form answers, rings from the caller's own SIM, and leaves an outcome, a callback and a WhatsApp behind.
Within minutes, and in the same hour at the latest. Somebody who filled a form is thinking about the purchase at that moment and usually about two or three sellers at once; the first one to ring gets the conversation. RMDialer records the lead's arrival time and its first-call time on the record, so "how fast" stops being a feeling and becomes a number the Web CRM shows per caller.
It stays in the list as not reached, rather than vanishing. RMDialer keeps the unanswered leads as their own group so they can be worked again later in the day, and a lead that asked for a specific time becomes a reminder that rings at that time. What it never does is let the lead sit in an inbox with no status, which is how leads get forgotten.
Yes. Send the lead ad results to a Google Sheet or post them to RMDialer's REST API, and each new lead lands in a caller's queue with the answers from the form. The caller sees which ad and which offer before the lead picks up, and the lead is rung from a normal mobile number rather than a line they will not answer.
Yes, by the same two routes. A website form that writes to a Google Sheet is linked once; a site that can post JSON sends the enquiry straight to the API. The page the form sat on can travel with the lead as a field, so the caller opens with the right product. From submit to ring is a few minutes when a caller has the queue running.
RMDialer rings leads held in another CRM through the REST API or a linked Google Sheet. Zoho, HubSpot, Salesforce and GoHighLevel leads reach the phones that way, and the call logs API sends the outcomes back for your own reports. There is no native button inside those CRMs; the connection is the API or the Sheet, and it is set up once.
Facebook lead ads, website forms, a Google Sheet, any REST API, portals that export to a Sheet or offer an API, an Excel or CSV upload, the phone's own call log, WhatsApp contacts, and queues a manager assigns. Every one of those ends up as the same queue on the caller's phone, and the Web CRM keeps the source on each lead so results can be read per source.
Whatever statuses your team defined: booked, interested, wrong number, not now, call back at a time. A remark box takes the one line worth remembering, and a callback field sets the reminder. Two taps is the usual count, and saving it is what rings the next lead. RMDialer will not move on until the outcome is saved, which is why no lead ends the day without one.
It is marked not reached and stays in the list, grouped with the others that did not pick up. Most teams work that group again after five or six in the evening, when answer rates rise, and a lead that still does not answer after a few tries is marked as such rather than quietly dropped. In RMDialer every attempt is on the record with its time.
If you set a template, yes: it goes on the official WhatsApp API as the call ends, from the business number, with the price list, brochure or booking link you chose. The reply lands on the lead's record next to the call. RMDialer can also ask the caller first rather than sending automatically, for leads where a human should decide.
Yes, in the Web CRM in any browser. Leads are shown by source (which ad, which form, which portal), with how many arrived, how many were rung and how fast, and by caller, with what each person did with their share. It is the view that shows which source is worth the ad spend and which caller is letting leads wait.
In the Web CRM, by count or by hand, as they arrive or in batches. Four callers and 400 leads is 100 each if split evenly, or weighted so the senior caller takes the high-value enquiries. RMDialer puts each lead in exactly one caller's queue, and a manager can move a caller's leads to somebody else when they are off.
Not from the same list. A lead handled on one phone leaves every other caller's queue at that moment, so the double call that annoys leads and embarrasses callers does not happen. In RMDialer a lead lives in one queue, and the record shows who rang it and when if anybody asks.
Yes. The lead, every call, every remark and every WhatsApp message are on the record in the Web CRM, not in the caller's head or their personal phone. When a caller leaves, their queue is moved to someone else with the history intact, and the new caller opens each lead knowing what was said. RMDialer keeps the record with the business.
Per caller, never per lead. Indian teams pay ₹159 for each caller every month when the year is paid up front, or ₹249 monthly when paying three months at a time. Teams outside India pay $29 for each caller for the whole year, or $12 to cover three months, with taxes added at checkout. That RMDialer seat carries the queue, the outcome sheet, reminders, the WhatsApp template and the manager's Web CRM, and no meter runs on minutes since the SIM inside the phone makes every call.
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.
