NACALLER AI KNOWLEDGE BASE Every NaCaller AI product, price, policy and common question on one page: AI calling agents, Instant Leads, Miss OTP and Voice OTP. Last updated: 2 October 2026 Source: https://nacaller.com/knowledge-base ## What NaCaller AI is NaCaller AI — AI Telecalling for Andhra Pradesh & Telangana Businesses. NaCaller AI makes thousands of human-like sales and reminder calls in Telugu, Hindi & English. Built for businesses, agencies and entrepreneurs across Andhra Pradesh and Telangana. Launch AI calling agents in minutes. NaCaller AI is Telugu-first: its AI voice agents speak Telugu the way it is actually spoken across the districts, and also speak Hindi and English. It is built by Webchilly Infoways in Visakhapatnam, Andhra Pradesh. - Who it is for: businesses, agencies and entrepreneurs across Andhra Pradesh and Telangana — for example education (admissions), real estate, clinics and finance. - Areas served: Andhra Pradesh, Telangana, Hyderabad, Vijayawada, Visakhapatnam, Guntur, Warangal, Tirupati, Nellore, Rajahmundry, Karimnagar. - Languages: Telugu, Hindi and English on every plan; 10+ Indian languages from the Starter plan. - Company: Webchilly Infoways, Visakhapatnam, Andhra Pradesh. Founded 2024. - Website: https://nacaller.com. Sign in or sign up: https://app.nacaller.com. ### Products at a glance - AI calling agents — outbound calls in Telugu, Hindi and English that hold a real conversation, run as campaigns. - Instant Leads — Facebook and Instagram lead ad submissions called back by an AI agent within seconds. - Integrations — a private webhook per lead source, so website forms, automation tools and CRMs can trigger calls. - Miss OTP — phone-number verification by a missed call. No SMS, no DLT registration. - Voice OTP — we call the user and read a 6-digit code in English, Hindi or Telugu. The fallback to a missed call. - NaCaller API Reference — developer docs for Miss OTP, Voice OTP and webhooks at https://nacaller.com/docs. ## Contact and support - Email: hello@nacaller.com - Phone: +91-62812-47412 - WhatsApp: +91-62812-47412 — use WhatsApp for anything affecting a live campaign. - Contact form: https://nacaller.com/contact. A person replies within one business day. - Location: Visakhapatnam, Andhra Pradesh. - Support is answered in Telugu, Hindi or English, whichever the customer prefers. - Support by plan: community on Free, email on Starter, priority WhatsApp on Growth, a named contact (dedicated account manager) on Scale. - Developers can ask questions from the form at the end of every page of the API Reference (https://nacaller.com/docs). ## AI calling agents An agent is an AI caller you configure with your script, your knowledge base, your voice and your goal. It holds a real conversation rather than playing a recording. - Natural turn-taking: the caller can interrupt at any time and the agent stops, the way a person does. - Answers questions from your business knowledge base, handles objections and steers back to the goal — a booking, a renewal, a follow-up. - Opens by identifying itself, in words you choose (include the AI disclosure in the opening line). - Handles mixed Telugu and English in the same sentence; names, amounts and dates are said the local way. - Voicemail detection: hangs up on an answering machine instead of using minutes. - Press-1 confirmations: takes a keypress as an answer. - Warm transfer to a human on your team mid-call, with the context carried across (see below). - Opt-out phrases (for example 'don't call me again') are recognised in English, Hindi and Telugu, including romanised spellings; the number is blocked across the account automatically. - In-call WhatsApp links: if you configure a booking link or a brochure link on the agent, the agent can send it to the caller's WhatsApp during the call. The agent only offers what it is set up to send. ### Warm transfer You can configure a warm transfer to a human on your team (Transfer rules in the dashboard). The caller presses a key or asks for a person, and the call bridges across to your team member, who gets the context so the caller does not have to repeat themselves. ## Voices, dialects, cloning and the Voice Studio There are 54 Telugu voices in the app's voice gallery, plus professional Telugu, Hindi and English callers used by default. Segment a list by district and point each segment at the matching voice — same script, right accent. Telugu voice regions: Telangana; Hyderabad; Coastal Andhra; North Andhra (Vizag); East Godavari; Rayalaseema; Chittoor / Tirupati; Nellore; Guntur / Krishna; West Godavari; North Andhra (Srikakulam); South Telangana (Palamuru); North Telangana (Karimnagar); Andhra & Telangana; North Telangana (Warangal); North Telangana (Nizamabad); East Telangana (Khammam); North Telangana (Adilabad); South Telangana (Nalgonda); West Telangana (Medak / Sangareddy); Rayalaseema (Kurnool); Rayalaseema (Anantapur); Rayalaseema (Kadapa); Coastal Andhra (Prakasam / Ongole); Krishna (Vijayawada); Visakhapatnam; East Godavari (Kakinada); East Godavari (Rajahmundry); Guntur (Tenali); Hyderabad (Old City); Secunderabad; Tirupati; Vizianagaram; Visakhapatnam (Gajuwaka); Visakhapatnam (Duvvada); Visakhapatnam (Seethammadhara); Visakhapatnam (Sheela Nagar); Visakhapatnam (Marripalem); Visakhapatnam (Simhachalam); Visakhapatnam (MVP Colony); Visakhapatnam (Ukkunagaram); Visakhapatnam (Bheemunipatnam); Visakhapatnam (Rushikonda); Hyderabad (Ameerpet); Hyderabad (Gachibowli); Hyderabad (Madhapur); Hyderabad (Kukatpally); Hyderabad (Balanagar); Hyderabad (Nacharam); Hyderabad (Shamirpet); Hyderabad (Begumpet); Hyderabad (Mehdipatnam); Hyderabad (Dilsukhnagar); Hyderabad (LB Nagar); Hyderabad (Uppal); Hyderabad (Miyapur); Hyderabad (Kompally); Hyderabad (Shamshabad); Hyderabad (Alwal); Hyderabad (Banjara Hills); Hyderabad (Tolichowki); Hyderabad (Patancheru). The gallery also covers Hyderabad Dakhni Hindi, Gen-Z registers, Hindi and Kannada. Recorded samples you can play: https://nacaller.com/how-we-talk. ### Voice cloning - On paid plans. Record about two minutes on your phone; the cloned voice is ready in minutes. - Optional dialect variants — your voice, localised for a district you don't speak. - Consent is required: clone only your own voice or one you have explicit written consent for. Never a public figure or a customer. - A cloned voice can be deleted; deleting it removes it from future calls. ### Voice Studio The Voice Studio in the dashboard synthesises any text you paste in any voice, so you can hear your actual opening line before a customer does. You can also compare voices side by side. ## Campaigns, calling hours and retries - Import leads from a CSV or Excel sheet (every paid plan), or connect a form so new enquiries are called automatically. - Pick an agent and an occasion, then launch. First calls can go out within minutes; it's self-serve, with no onboarding call required. - Calling window: every campaign and lead source has a calling window the dialer will not dial outside, checked in IST. The default is 9 AM to 9 PM IST, and you can change it. A lead that arrives outside the window is kept and called when the window opens. - Automatic retries for no-answers. - Per-language greetings and scripts, so a Telugu campaign and a Hindi campaign never share a line. - Blocklists and opt-out capture work across the whole account. ### Events and RSVP calls The Events feature calls a guest list for an event and records each guest's answer — attending, declined or maybe — along with expected head counts, so you can see who has been called, who answered and how many people to expect. RSVP replies can also be emailed to you. ## Instant Leads (Facebook and Instagram lead ads) When someone submits your Facebook or Instagram lead ad form, the lead reaches NaCaller as Meta creates it and an AI agent calls them within seconds — provided the lead lands inside the calling window you set and the campaign has an agent assigned. A lead that lands at night is queued for the morning. - The agent asks your qualifying questions (budget, model, timeline, area, branch…) written in plain language. - It decides against your rules; qualified leads go to the salesperson you named, with a transcript and summary. Others are logged with the reason. - Leads are filed into queues by what they asked about; every lead keeps its answers, recording (if recording is on), transcript and outcome. - Connecting a Facebook Page requires Meta to approve the app's lead-retrieval permission, so there is a short review step — days, not minutes. - Calls are billed per minute from your plan's balance, like any other call. Instant Leads is how the call is triggered, not a separate meter. - Hindi, English, Tamil and Kannada are also available on the same campaign if leads are mixed. - Optional one-time done-for-you setup (Meta connection, form mapping, qualifying agent, calling window, handover, tested with a real call). The price is on https://nacaller.com/instant-leads. You can also set it up yourself in the dashboard for free. ## Integrations and webhooks - Every lead source gets its own private webhook URL, its own agent and language, its own calling window and its own person to hand qualified leads to. - Anything that can POST a name and phone number can trigger a call: a website form, Zapier, Pabbly Connect, Make, a CRM's outbound webhook, or your own code. Only phone is required. - The reply says whether a call was placed, and if not why (for example queued, no agent, opted out). Repeat sends update the same lead rather than duplicating it. - TalkingWP website assistant: authorise it once and its leads, appointments and conversations mirror into NaCaller (read-only). - API access and webhooks are on the Scale plan; CSV/Excel import works on every paid plan. - Details: https://nacaller.com/connect. ## Transcripts, sentiment and analytics - After every call: a full transcript, a summary, the sentiment, the outcome (for example interested, callback, booked, not now) and the fields your script asked for, as structured data. - Lead scoring from 1 to 10 ranks the leads worth calling back first. - Call recordings are available when recording is switched on for the account (it is off until you turn it on). - Dashboard views: live calls, call history and analytics. Leads, call history and transcripts are exportable. ## Caller ID and your own numbers - You can start calling on NaCaller's numbers — no new phone number is needed, and there is no charge for that on any plan. - A dedicated number of your own, used as the caller ID your agents dial from, is ₹399 a month per number. It is optional, billed separately from the plan, and the first month is paid at checkout. - On paid plans calls can show your own business number, subject to your telecom paperwork being in order. - Numbers are rented from the Numbers screen in the dashboard. Indian numbers show their city (for example Mumbai 022 or Bangalore 080) and work anywhere in India. - Indian numbers need a one-time KYC (business verification) that the carrier must accept before the number can be used. - A rental runs 30 days and is renewed from the same screen. If it lapses, the number stops being used as your caller ID and calls go out on NaCaller's numbers again; release it and it goes back to the carrier for good. ## Miss OTP — missed-call verification Miss OTP proves a user holds the phone number they typed: they give a missed call to a number you show, and the caller ID is the proof. Nothing is sent to the phone, so there is no SMS, no DLT registration, no template approval and no code to leak. - Two HTTP calls from your server: POST to start (returns the number to show), then poll the status or receive a signed webhook. - Typically verified two to four seconds after the user presses dial; they can cut the call as soon as it rings. - Each verification window is 5 minutes, with per-number throttling (5 requests per number per 10 minutes). - Webhook callbacks are HMAC-SHA256 signed. Start on the shared verification line, or move to a number of your own when volume justifies it. - Works with zero balance and no mobile data on the user's phone. - Billing: prepaid credits, charged only when a number verifies. Failed or unanswered attempts are free, credits never expire, no monthly fee. - Use cases: signup and login, high-drop-off forms (loan applications, admissions, KYC starts), delivery and service number confirmation. - API base: https://api.nacaller.com/api/verify. Product page: https://nacaller.com/missed-call-otp. ## Voice OTP — a call that reads a code For users who can't give a missed call, NaCaller rings the number and reads a 6-digit code aloud, twice, in English, Hindi or Telugu. Nothing else is said. No SMS, so no DLT templates. - Same API key, base URL and webhook as Miss OTP — it is method "voice" on the same start call. - A verification is valid for 10 minutes, with 5 attempts to enter the code. At most 3 voice calls to one number per hour and 10 per day. - Billed per answered call only; unanswered, declined or switched-off calls cost nothing. Prepaid credits, no monthly fee. GST applicable. - Per attempt a voice call costs more than an SMS; it is meant as the fallback under Miss OTP. - Not yet for banks, lenders, brokers and insurers regulated by the RBI, SEBI or IRDAI: TRAI requires their OTP calls to come from 1600-series numbers. - Product page: https://nacaller.com/voice-otp. ### Test on my phone In the dashboard, Verify → "Test on my phone" runs a real Miss OTP or Voice OTP verification to your own phone without writing any code. Each test spends a real credit. New accounts get 25 free verifications and 5 free voice calls — once per account, no card. ## NaCaller API Reference (developer docs) - Overview: https://nacaller.com/docs — The NaCaller API Reference: verify Indian mobile numbers with a missed call, or a voice call that reads a code. Get a key, one base URL, one auth header, and a prompt you can paste into your AI coding tool. - Miss OTP: https://nacaller.com/docs/miss-otp — Start a missed-call verification, show the number, poll status or take the webhook. Every field, status code and limit, with curl, Node and Python samples. - Voice OTP: https://nacaller.com/docs/voice-otp — We call the number and read a 6-digit code aloud. Start, check and status endpoints, limits and billing, with curl, Node and Python samples. - Webhooks: https://nacaller.com/docs/webhooks — The signed verification callback (X-MissOTP-Signature, HMAC-SHA256) with Node and Python verifiers, and the inbound webhook that posts leads into NaCaller. The docs include a prompt to paste into an AI coding tool (Lovable, Bolt, Cursor, Replit, v0, Claude Code). Plain-text summary for AI assistants: https://nacaller.com/llms-full.txt. The API key is a server secret and must never be put in browser code. ## Pricing AI calling plans are billed monthly in INR. No lock-in. From ₹3.99 a minute (₹3 on the largest plan). A one-time ₹1,499 setup fee is bundled into the first paid plan only — never the free trial, never again after that. Minutes beyond a plan are ₹3/minute. Each call counts its connected time, rounded up to the minute. GST-compliant invoices are issued in your business name. Plan | Price / month | Calling minutes | AI agents | Campaigns | Effective ₹/min Free Trial | Free | 10 | 1 | 1 | — Starter | ₹1,995 | 500 | 3 | 10 | ₹3.99 Growth | ₹7,000 | 2,000 | 10 | Unlimited | ₹3.5 Scale | ₹22,500 | 7,500 | 50 | Unlimited | ₹3 Enterprise | On request | Custom | Unlimited | Unlimited | — - Free Trial: Test the waters — make your first AI calls free. Includes: 10 free calling minutes; 1 AI calling agent; Telugu, Hindi & English; Browser test calls; Basic call transcripts; Community support. - Starter: For solo founders, agents & small shops getting started. Includes: 500 calling minutes / month; 3 AI calling agents; 10 campaigns; All 10+ Indian languages; Sentiment analysis; Lead import (CSV/Excel); Email support. - Growth: For growing businesses & agencies running real campaigns. Includes: 2,000 calling minutes / month; 10 AI calling agents; Unlimited campaigns; AI lead scoring; Automated data collection; Call recordings & analytics; Priority WhatsApp support. - Scale: For high-volume call centres & multi-location teams. Includes: 7,500 calling minutes / month; 50 AI agents; Unlimited campaigns; API access & webhooks; Custom voices & numbers; Dedicated account manager; Priority phone support. - Enterprise: Custom volume, on-premise options, SLAs & integrations. Includes: Custom calling volume; On-premise / private cloud; Custom AI model tuning; CRM & ERP integrations; 99.9% uptime SLA; Dedicated success team. Full pricing page: https://nacaller.com/pricing. ### Miss OTP credit packs Pack | Verifications | Price | Per verification Starter | 1,000 | ₹199 | ₹0.20 Growth | 5,000 | ₹749 | ₹0.15 Business | 25,000 | ₹2,999 | ₹0.12 Scale | 1,00,000 | ₹9,999 | ₹0.10 ₹0.10–₹0.20 per verified number. Only verified numbers are charged; credits never expire. ### Voice OTP call packs Pack | Answered calls | Price | Per answered call Voice 500 | 500 | ₹349 | ₹0.70 Voice 2,000 | 2,000 | ₹1,299 | ₹0.65 Voice 10,000 | 10,000 | ₹5,999 | ₹0.60 Voice 50,000 | 50,000 | ₹27,499 | ₹0.55 ₹0.55–₹0.70 per answered call. Unanswered calls are free. ### Free to try - Free Trial plan: 10 free calling minutes and 1 AI agent, no card. - Verification: 25 free Miss OTP verifications and 5 free Voice OTP calls, granted once per account. - Live demo at https://nacaller.com/demo: free, no signup. ## How to get started 1. Sign up at https://app.nacaller.com/signup. 2. Verify your mobile number by call (Indian mobile numbers only, one number per account). 3. A person at NaCaller reviews every new account before it can dial anyone. It normally clears within a few working hours, longer over a weekend. Nothing dials and nothing is billed while you wait. 4. Create an agent, upload a lead sheet or connect a form, and launch. The free trial's minutes are yours to test with. 5. For Miss OTP / Voice OTP: issue an API key in the dashboard, try Test on my phone, then follow the API Reference. ### Live demo At https://nacaller.com/demo a visitor enters their number, gives one missed call to prove the phone is theirs, picks Telugu, Hindi or English, and the demo agent rings them within seconds for a real call of about two minutes. Three demo calls a day per number; free, no card, no signup. The demo number is not used for sales calls. ## Compliance, consent and data - DLT and DND: promotional and transactional voice calls fall under TRAI's DLT regime (registered sender, templates where applicable, 140-series origination for promotional traffic, DND scrubbing). Registration, consent and the calling list are the customer's responsibility; NaCaller provides blocklists, calling windows, automatic opt-out capture and complete transcripts. - Consent must satisfy the DPDP Act. NaCaller does not make a purchased or scraped list legal. - Time of day: every campaign carries a calling window (default 9 AM–9 PM IST) and the dialer will not dial outside it. - AI disclosure: India's IT Rules require synthetic audio to be labelled; put the disclosure in the agent's opening line. - Call recording is off until you turn it on. When on, every recorded call opens by telling the caller, in their language; recordings delete themselves after a retention window you set; deleting a recording or its lead erases the audio at the telephony provider too. - Data: each account is isolated; the team accesses tenant data only when you ask for support. Leads, history and transcripts are exportable. Leads and recordings can be deleted from the dashboard; deleting the account removes the rest; email requests are actioned within 30 days. - Model training: consent for a service and for model training are treated as separate — your calls run your campaigns. - Voice cloning requires the voice owner's explicit, separate, documented consent. - Voice OTP is not yet for RBI-, SEBI- or IRDAI-regulated entities, which must place OTP calls from TRAI 1600-series numbers. - Uptime: a formal 99.9% SLA is part of the Enterprise plan. ## What NaCaller does not do - It is an outbound calling platform. It is not an inbound AI receptionist that answers calls to your business line. - Handing a call to a human is a warm transfer during an outbound call, as configured in Transfer rules — the caller presses a key or asks for a person. - It does not register you for DLT, scrub your list against DND for you, or make an unconsented list legal. - There is no native Salesforce or Zoho button, and it is not listed in automation tools' app directories — those connect through the webhook. - The lead webhook is for one lead at a time; bulk lists go in as a CSV/Excel campaign. - Miss OTP does not undercut SMS OTP on price at the entry tier; its advantage is going live without DLT and no code to leak. There is no SDK — the API is two HTTP calls. - Voice OTP is not yet available to RBI/SEBI/IRDAI-regulated entities. ## Frequently asked questions ### The questions owners actually ask Q: Is AI calling even legal in India? A: Yes — with conditions that are yours to meet, not ours to wave away. Promotional calls need DLT registration, a 140-series origination number and scrubbing against the TRAI DND registry; consent has to be DPDP-compliant. NaCaller gives you the tooling — per-number blocklists, campaign call windows, instant opt-out capture and a full transcript of every call — but registration and consent for your own list are your responsibility. Anyone who tells you their platform makes a scraped list legal is selling you a fine. Q: Will it sound like one of those robotic IVR calls? A: Press play on any voice on this page and judge for yourself — those are real agent recordings, not a studio ad. The difference isn't the audio quality, it's the dialect: a Telangana caller hears Telangana Telugu, not textbook Telugu read by a newsreader. Q: Can the customer interrupt it, or does it just talk over them? A: They can interrupt. The agent listens while it speaks and stops when the caller starts — the same way a person does. That barge-in behaviour is the single biggest thing separating a conversation from a recorded message. Q: What happens when it doesn't know the answer? A: It says so, and hands over. You can configure a warm transfer to a human on your team — the caller presses a key or asks for a person, and the call bridges across. The human gets the context, so nobody has to repeat themselves. Q: Do I have to tell people they're talking to an AI? A: You should, and you increasingly must — India's IT Rules now require synthetically generated audio to be labelled. You control the opening line, so put the disclosure in it. We'd rather you did: in our experience the calls that identify themselves get further than the ones that get caught pretending. Q: My customers speak half Telugu, half English. Will it cope? A: That's the normal case here, and it's handled — the same sentence can carry Telugu grammar and English nouns ('CSE seat', 'hostel', 'counselling') without the agent losing the thread. Hyderabad Telugu with Urdu borrowings is a supported dialect, not an edge case. Q: How long before my first call goes out? A: Create an agent, upload a lead sheet, launch. Minutes, not weeks. There's no implementation partner and no onboarding call you have to sit through first — it's self-serve, whatever plan you're on. Q: Do I need a new phone number? A: No — you can start on ours, at no extra charge on any plan. A dedicated number of your own as caller ID is optional and costs ₹399 a month per number, rented from the Numbers screen. If you let a rental lapse it simply stops being used as your caller ID and calls go out on our numbers again. Showing your own existing business number is configurable on paid plans, subject to your telecom paperwork being in order. Q: What if someone says 'don't call me again'? A: The agent recognises opt-out phrasing in English, Hindi and Telugu — including romanised spellings — flags the number the moment it hears it, and stops. It's automatic; nobody has to notice it in a transcript afterwards. Q: Can it work with my CRM or my website form? A: Yes. New enquiries can be called within seconds of the form submission, and outcomes push back out. Webhooks and API access are on the Scale plan; the lead import (CSV/Excel) works on every paid plan. ### Costs, billing and the fine print Q: What exactly counts as a 'minute'? A: Connected talk time. A call that rings out and is never answered doesn't consume your included minutes — you're paying for conversations, not attempts. Q: Is there a setup fee or an onboarding charge? A: A one-time ₹1,499 setup fee is bundled into your FIRST paid plan, and never charged again after that — no per-plan-change fee, no annual repeat. The free tier has none: you can start there without giving a card at all. Q: Is GST included in these prices? A: No — the prices shown are exclusive of GST, which is applied as per Indian regulations at checkout. Your invoice carries the GST breakup for input credit. Q: What happens if I run past my included minutes? A: Calling continues and the extra minutes bill at ₹3/minute. You're alerted before you get there — we'd rather warn you than surprise you on the invoice. Q: Do unused minutes roll over to next month? A: No. Included minutes are per billing period and reset when the period does. If you consistently finish the month with minutes to spare, you're on too big a plan — move down. Q: Can I change plans in the middle of a month? A: Yes, and you should when your volume changes. Upgrades take effect immediately; there's no lock-in and no cancellation penalty on any plan. Q: ₹3–4/min sounds higher than the ₹0.40/min I saw advertised. A: It is, and the difference is what's inside the minute. Sub-rupee rates are usually the telephony leg alone, billed before speech recognition, the language model, the voice, the recording and the transcript. Our number is the whole call, in one figure, with no per-feature add-ons behind it. Q: How does this compare to hiring a telecaller? A: One telecaller in AP or Telangana costs roughly ₹15,000–25,000 a month and makes perhaps 60–80 connected calls a day, on working days, during working hours. Run the slider on our home page with your own salary figure — the maths is the real Starter rate, not a marketing multiplier. Q: What payment methods do you take? A: UPI, cards and net banking through a secure Indian payment gateway, in INR. Invoices are GST-compliant and issued to your registered business name. Q: Is there a refund if it doesn't work for us? A: Start on the free tier — 10 real minutes, no card — and prove it works on your own customers before you pay anything. That's a better answer than a refund policy, and it's why the free tier exists. ### Dialects, cloning and what's really recorded Q: Are these real recordings or a demo reel? A: They're the exact voices your campaigns dial with. Nothing on this page is a studio performance recorded once for marketing — if it sounds good here, it sounds like that on the call. Q: Why does dialect matter? Isn't 'Telugu' enough? A: Because Telangana Telugu and coastal Andhra Telugu differ enough in vocabulary and pronunciation that a caller hears the mismatch in the first sentence — and a caller who hears a mismatch starts wondering who's really calling. Hyderabad urban Telugu carries substantial English and Urdu; Rayalaseema doesn't. Q: Which dialects do you actually have? A: 54 Telugu voices today, across Telangana, Hyderabad (Telugu and Dakhni Hindi), coastal Andhra, North Andhra/Vizag, East Godavari, Guntur, Rayalaseema, Nellore, Karimnagar, Palamuru, Srikakulam, plus Gen-Z registers, Hindi and Kannada. The ones on this page are recordings you can play; the rest are in the app's voice gallery. Q: Can I use my own voice? A: Yes, on paid plans. Record about two minutes on your phone and calls go out in your voice. You can also generate localised versions — you, in Rayalaseema — which is the part nobody else offers. Q: Is voice cloning legal? Do I need consent? A: You need the consent of whoever's voice it is, explicitly and separately — a general privacy policy is not enough under the DPDP Act, and personality rights are being actively litigated in India. Clone your own voice, or one you have written permission for. Never clone a public figure or a customer. Q: Can I delete a cloned voice later? A: Yes, and you should be able to — the right to withdraw consent is absolute under the DPDP Act. Deleting the voice removes it from future calls. Q: Can one campaign use different voices for different districts? A: That's the intended way to use this. Segment your list by district and point each segment at the matching voice — same script, right accent. Q: Male or female — which performs better? A: It depends entirely on who you're calling and about what. An older feminine voice tends to do better on household and education calls in this region; a younger masculine voice does better on some B2B calls. Test both on your own list; that's what the free minutes are for. Q: Can it read out numbers, amounts and dates correctly in Telugu? A: Yes — rupee amounts, ranks, percentages, dates and times are spoken the way a Telugu speaker would say them, not spelled out digit by digit. Q: Can I hear a voice saying my own script before I launch? A: Yes. The Voice Studio in your dashboard synthesises any text you paste, in any voice, so you can hear your actual opening line before a single customer does. ### How each business actually uses it Q: We're a college. When should the agent call an admission enquiry? A: Within a minute of the form. Speed-to-lead is the whole game in admissions — an enquiry called in the first minute is a conversation, the same enquiry called the next morning is an interruption. Set it to fire on the webhook and it never sleeps through one. Q: Real estate — can it qualify a lead, not just book a call? A: Yes. Budget, preferred locality, ready-to-move versus under-construction, loan status — whatever your script asks, captured as structured fields so your sales team only drives out for the ones worth driving out for. Q: Clinics — can it handle appointment reminders and reschedules? A: Reminders, confirmations and no-show recovery are the classic fit. It reaches the patient in their own dialect, which matters more with older patients than any feature on this page. Q: Is this suitable for loan or EMI collection calls? A: For polite reminders, yes, and the full transcript of every call is kept, which is exactly what you want if a conversation is ever questioned. Note that RBI rules on recovery conduct apply to you whether the caller is human or not. Q: E-commerce — will it cut my COD returns? A: Confirming COD orders before dispatch is one of the highest-return uses here, because an unconfirmed COD order is a shipping cost you're likely to eat twice. The agent confirms, and cancellations come back as structured outcomes. Q: We're an agency running campaigns for clients. Does that work? A: Yes — separate campaigns, agents, voices and numbers, with call history kept per campaign. That's the Growth plan and up. Q: Can it call at a specific time of day only? A: Yes, and it should. Every campaign has a local calling window and the dialer won't dial outside it — no 8 am calls to a customer who'll remember it. Q: What about festivals and regional holidays? A: Set the campaign window around them. A Vinayaka Chavithi morning is not when your admission call lands well, and no amount of good Telugu fixes bad timing. Q: Can it take an order or a booking, not just qualify? A: It can capture everything the booking needs and push it to you as structured fields. For anything requiring payment, hand off to a human or send a link mid-call. Q: How many calls can it make at once? A: Enough that your plan's minutes, not the dialer, will be your limit. If you're planning a burst of thousands in one window, tell us the volume and the window before you launch it. ### What happens when you press the button Q: Is the demo a real call or a recording? A: A real call, on the same pipeline our paying customers run. Nothing about it is staged — that's the entire point of offering it. Q: Why do I have to give a missed call first? A: So we know the number is yours. Without that check, anyone could type in someone else's number and have our agent ring a stranger. It takes ten seconds and it's the reason this demo is safe to offer publicly. Q: Will you use my number for sales calls afterwards? A: No. The demo number is used for the demo. If you want to hear from us you can ask, and if you don't, you won't. Q: Do you keep my number? A: Yes, once it's verified — as a record that this number tried the demo, which is also how the three-a-day limit works. It isn't used to call or message you for anything else. Q: What if my number is on your do-not-call list? A: The demo still calls you, once. You've just proved the number is yours and asked for the call, so we treat that as consent for this one call and say so on screen. Your opt-out stays in place for everything else. Q: How long is the demo call? A: About two minutes. Long enough to interrupt it, change the subject, test its Telugu and decide whether it's real. Q: Can I test it in Hindi or English instead of Telugu? A: Yes — pick the language before you request the call. If you're evaluating for a mixed customer base, do all three. Q: How many demo calls can I make? A: Three a day per number. The free trial, once you sign up, has no such limit — it's your ten minutes to spend however you like. Q: What should I ask it to really test it? A: Interrupt it mid-sentence. Change your mind. Ask something slightly off-script. Switch from Telugu to English halfway. Those are the moments where a scripted bot falls apart and a real conversation doesn't. Q: Can I hear the recording and transcript afterwards? A: On a signed-up account, yes — the transcript, sentiment and captured fields are always there, and call recording can be switched on for your account. When it is on, callers are told at the start of the call, recordings are deleted automatically after a retention window you set, and you can erase any single recording from your call history. The public demo is deliberately lighter on data retention. Q: Does the demo agent know about my business? A: No — it's a generic agent. Yours would be configured with your script, your knowledge base, your occasions and your voice, which is why your version will be noticeably better than this one. Q: Is the demo call free? A: Completely. No card, no signup required to try it. ### Who we are and how we operate Q: Who's behind NaCaller? A: Webchilly Infoways, operating out of Visakhapatnam, Andhra Pradesh. We're a small team building for the market we live in rather than adapting something built elsewhere. Q: Why Telugu-first instead of an all-India product? A: Because 'all-India' in practice means English with an accent option. Eighty million Telugu speakers across two of the country's fastest-growing state economies are not a localisation checkbox, and a Rayalaseema customer can tell within one sentence whether you thought about them. Q: Where is my data stored, and who can see it? A: Your call recordings, transcripts and lead data belong to your account, and each account is isolated from every other one. Our team accesses tenant data only when you ask us to for support. Q: Can I export my data and leave? A: Yes. Your leads, call history and transcripts are exportable. A product that holds your data hostage isn't confident about its own retention. Q: Do you train AI models on my customers' calls? A: Consent for a service and consent for model training are legally separate things under the DPDP Act, and we treat them that way. Your calls run your campaigns. Q: What's your uptime commitment? A: A formal 99.9% SLA is part of the Enterprise plan. On the standard plans we operate to the same target without contracting to it — we'd rather not sell you an SLA we haven't put in writing. Q: What support do I get, and in what language? A: Community on free, email on Starter, priority WhatsApp on Growth, a named contact on Scale — answered in Telugu, Hindi or English, whichever you'd rather use. Q: Are you hiring, or open to partnerships? A: Yes to both, particularly agencies and resellers across AP and Telangana. Use the contact form and say which. Q: Can I get an invoice in my company's name with GST? A: Yes — GST-compliant invoices are issued to your registered business name for input credit. Q: Something went wrong on a live campaign. How fast will you respond? A: Faster than the plan promises, in practice. Use WhatsApp for anything live and affecting real customers — that's what it's there for. ### The questions nobody likes answering Q: Is automated AI calling legal in India in 2026? A: Yes, within a framework. Promotional and transactional voice calls fall under TRAI's DLT regime: registered sender, registered template where applicable, 140-series origination for promotional traffic, and DND scrubbing before you dial. Consent must satisfy the DPDP Act. Sector regulators — RBI, IRDAI — add their own rules on top. None of that makes AI calling illegal; it makes cold-calling a purchased list illegal, which was already true before AI. Q: Whose responsibility is DLT registration and DND scrubbing — yours or mine? A: Yours, as the entity whose message is being delivered. We provide the controls that let you operate cleanly — blocklists, calling windows, automatic opt-out capture, complete transcripts — but the registration, the consent record and the list itself are yours. Be sceptical of any vendor who claims otherwise. Q: What are the penalties if I get this wrong? A: Per-violation financial penalties, and — the part that actually hurts — disconnection of the originating numbers. TRAI's detection has become considerably more aggressive; enforcement action against tens of thousands of numbers in a single quarter is now normal. Q: Roughly how many Indian numbers are on DND? A: A majority of active mobile numbers carry some DND preference. Plan on the assumption that most of a cold list is unreachable for promotional content, and build your calling around consented enquiries instead. That's also where the conversion is. Q: Does the DPDP Act change what I can do with call recordings? A: It formalises it. You need a lawful basis for the recording, the caller needs to be able to withdraw consent, and you need a real process to honour that withdrawal. That is why recording is off until you turn it on; why every recorded call opens by telling the caller so, in their own language; why you set a retention window after which recordings delete themselves; and why deleting a recording — or the lead it belongs to — erases the audio at our telephony provider, not just the row on your screen. Q: Do I legally have to disclose that the caller is an AI? A: India's IT Rules now require synthetically generated audio to be labelled, and the practical reading for voice calls is that the disclosure belongs in the first utterance. You control the opening line, so write it in. It also happens to work better. Q: Can I clone another person's voice for my campaigns? A: Only with that person's explicit, separate, documented consent. Indian courts have been actively protecting personality and voice rights, and a general company privacy policy does not cover biometric voice data. Cloning a public figure is not a grey area. Q: What about calling customers who are already my customers? A: Transactional and service calls to existing customers sit on a much firmer footing than promotional calls to strangers — reminders, confirmations, renewals, deliveries. This is where the majority of sensible use here lives. Q: Are there time-of-day restrictions on commercial calls? A: Yes — and it's not just a default you can widen. Every bulk campaign and every Instant Lead source is hard-capped to 9:00 AM–9:00 PM in that number's local time zone at the platform level; nothing you configure can dial outside it, even by mistake. Q: Does NaCaller retry a call nobody picks up? A: On campaigns, yes — an optional retry ladder, up to 10 attempts, with a gap you set from 5 minutes to 30 days between tries. Instant Leads deliberately don't retry: a fresh lead that goes unanswered is a one-shot dial, on purpose — redialing someone every minute the moment they don't pick up is how a legitimate business starts looking like a robocaller. If a lead needs a second attempt, run it through a campaign instead, where retries are visible and bounded. Q: What records should I keep if a customer complains? A: Every call carries its full transcript, timestamps, outcome and the captured fields, retained in your account and exportable — and the call audio too, if you have recording switched on. If a conversation is ever disputed, you have the conversation, which is one genuine advantage over a human telecaller's memory. The trade-off is honest: recordings are personal data under the DPDP Act, so they come with disclosure, a retention window and erasure on request. ### The questions you'd ask before your first commit Q: How does missed-call OTP verification actually work? A: You POST the number your user typed. We return a request id and a phone number. Your user gives a missed call to that number from the handset they are claiming — they can cut it the moment it rings. The network hands us their caller ID, we match it to your pending request, and your poll (or our webhook) flips to verified. Nothing is ever sent to the phone, which is why nothing can be delayed, filtered or undelivered. Q: Can I send OTP SMS in India without DLT registration? A: Not legally, and not reliably — since 2021 TRAI requires every enterprise sending transactional or OTP SMS to register its entity, its sender header and its templates on a DLT platform, and unregistered traffic gets blocked at the operator gateway. That is the whole reason this product exists. A missed call is not an SMS: there is no header and no template, so there is nothing to register and nothing to get rejected. You can be verifying real numbers today. Q: How long does DLT registration actually take? A: Entity registration is typically 1–3 working days, header approval 1–3 more, and each template 1–7 — so 3–7 working days when your paperwork is clean, and two to six weeks when it is not. Then every change to your message wording starts a fresh template approval. Teams find us on day two of that wait. Q: How does this compare to MSG91, 2Factor, SMSCountry or Twilio? A: Honestly: on raw price per message, direct-route Indian SMS providers beat us — quality transactional SMS lands around ₹0.10–₹0.20, and Twilio around ₹1.50–₹2.00 once forex and markup are in. We do not claim to be the cheapest per unit and you should not believe anyone in this category who does. What we beat them on is the two things that actually cost you money: the days you spend blocked on DLT before you can ship, and the verifications that never complete because the SMS did not arrive. Use us to launch, and to catch the users SMS loses. Q: Are there other missed-call verification providers in India? A: Yes — Cognalys is the best-known, and there are SMS providers that bolt a missed-call fallback onto their stack. We are not going to pretend we invented the mechanism. What we offer is a two-call API with no SDK, credits that are charged only on success and never expire, no monthly platform fee, and an account that also gives you AI voice calling if you ever need it. Compare us on those, not on novelty. Q: Why do OTP SMS messages fail to arrive in India? A: Four common causes, all outside your code. A template that does not byte-match the registered DLT template gets rejected at the gateway. Carrier spam filters flag traffic from headers with poor reputation. Peak-hour routing bottlenecks on Jio, Airtel and Vi delay delivery during festive or UPI surges. And handset-level filtering and DND settings quietly bin the rest. None of these apply to a live inbound call. Q: Does it improve completion rate, or just cost? A: Completion rate, in the places it matters most. In tier-2 and tier-3 markets — which is most of India — voice coverage is reliable where SMS delivery is not, and a user who has to wait 40 seconds for a code abandons the form. A missed call resolves in about three seconds and needs no data, no balance and nothing to read. That is where the number moves. Q: Is this secure enough for my app? A: For signup, login and lead capture, yes — it is proof of possession at the same practical strength as an SMS OTP, and it removes the two ways SMS codes actually leak: a code readable on a lock screen, and a user reading a code aloud to someone impersonating support. There is no code to read. For authorising a payment, a device change or a regulated KYC step, use it as one factor, not the only one — those flows want an explicit confirmed code with an audit trail. We would rather tell you that than sell you a verification you will regret at audit. Q: What stops someone spoofing the caller ID? A: Layered limits rather than a single claim. We only match 10-digit Indian mobile numbers, so the international routes where spoofing is practical do not resolve to a verifiable number. Each verification is bound to one request with a five-minute window, cannot be replayed, and cannot be read across accounts. Attempts are throttled per number and per key. The residual risk is comparable to SMS, which is spoofable at the SS7 layer in ways most teams never think about. Q: Do I have to poll, or can you send me a webhook? A: Either. Polling the status endpoint is one line and fine for a signup screen the user is watching. If you would rather not poll, set an HTTPS callback URL and we POST the moment a number verifies, with an HMAC over the exact body bytes in the X-MissOTP-Signature header so you can prove the call came from us and detect a replay. Q: What does it cost, and what am I charged for? A: Verified numbers only. A request that is started and never called costs you nothing, because an unanswered request costs us no telephony either. Credits are prepaid, they do not expire, and there is no monthly minimum, platform fee or per-seat charge underneath them. Your first 25 verifications and 5 voice calls are free, once per account, and run against the live line, not a sandbox that behaves differently. Q: Does my user pay for the missed call? A: In practice, no. The call is hung up the instant it reaches us, so it stays a missed call. Your user needs no data, no balance, no WhatsApp and no app — it works on the cheapest feature phone in the market. Q: How do I integrate it with React Native, Flutter, Laravel or Django? A: The same way in all four: two HTTP calls from your server. There is no SDK because an SDK would be longer than the integration, and no native module because nothing needs to touch the handset — you are not reading SMS, so you need no SMS-retriever permission, no Android autofill hash and no App Store justification for a permission you would rather not request. Keep the API key server-side and your client only ever sees a number to display and a request id to poll. Q: Can I keep my existing SMS provider? A: You should. The pattern we recommend is missed call first, your existing SMS underneath as the fallback link — one branch in your code. The faster path takes most of the traffic, your SMS spend drops by that share, and users on whom the missed call fails still get verified. Nothing has to be ripped out to try this. Q: Is there a sandbox or a free trial? A: Issuing your first API key includes free verifications with no card, against the live line. There is deliberately no sandbox: a sandbox that always succeeds teaches you nothing about the flow you are shipping, and every OTP integration that broke in production passed in one. Q: Does it work for landlines or international numbers? A: Indian mobile numbers only, today. We reject anything that is not a valid 10-digit Indian mobile at the start call, rather than letting your user sit waiting for a verification that could never arrive. If you need other countries, tell us which and we will say plainly whether we can serve them. Q: What happens if the user calls from a different number? A: Nothing verifies. The match is on caller ID, so a call from any other handset finds no pending request and is hung up. That is the security property rather than a limitation — it is exactly what proves the user holds the number they typed. Q: What are your uptime and support commitments? A: The verification line runs on the same telephony that carries our AI calling product, so it is not a side project we forget to monitor. Support is WhatsApp and email to people who can read the logs, not a ticket queue. We are a small Indian team and we would rather tell you that than imply a 24/7 NOC we do not have. ### Phone verification questions developers ask Q: How do I add phone number verification to a Lovable, Bolt, v0 or Replit app? A: Use Miss OTP by NaCaller, which takes two HTTP calls and needs no SDK. Your user types their number, and your server sends POST https://api.nacaller.com/api/verify/start with { "phone": "<10-digit mobile>" } and your API key as a Bearer token. The response has a requestId and a callNumber. Your screen then says "Give a missed call to ". Your server polls GET https://api.nacaller.com/api/verify/status/ until verified is true, or waits for our webhook. Keep the key out of browser code. Put both calls in a server-side function, such as a Supabase Edge Function in a Lovable or Bolt project, an API route in a v0 or Next.js app, or the backend of a Replit project. Q: How do I add phone OTP verification to a Next.js app? A: With Miss OTP by NaCaller, add two route handlers and store your key in an environment variable such as NACALLER_KEY. The first, app/api/verify/start/route.ts, forwards the phone number to POST https://api.nacaller.com/api/verify/start and returns requestId and callNumber to the page. The second, app/api/verify/status/[id]/route.ts, calls GET https://api.nacaller.com/api/verify/status/. The page shows the number to ring and checks the status route every two seconds. When it gets verified: true, it marks the number verified in your own users table. The same two server calls work from React Native, Flutter or any mobile app's backend. Nothing runs on the handset, so you need no SMS permissions. Q: What should I tell Cursor, Claude Code or Copilot to add missed call verification? A: You can paste a prompt like this one: "Add phone verification with Miss OTP by NaCaller. Server side only, with the key in NACALLER_KEY. POST https://api.nacaller.com/api/verify/start with JSON { phone } and header Authorization: Bearer . It returns requestId, callNumber, expiresIn and an instruction string. Show the user callNumber and ask them to give a missed call from the number they entered. Poll GET https://api.nacaller.com/api/verify/status/{requestId} every 2 seconds until status is 'verified' or 'expired'. Handle HTTP 400 (not a valid Indian mobile), 402 (out of credits) and 429 (too many attempts)." A pending request lasts five minutes, so show a retry button once status comes back as expired. Q: How do I verify phone numbers in India without DLT registration? A: Don't send an SMS. Verify with a call the user places. Miss OTP by NaCaller asks your user to give a missed call to a number the API returns, then matches the caller ID the telephone network passes to us against your pending request. No message is sent, so there is no sender header, SMS template or DLT entity to register, and you can verify real numbers as soon as you have an API key. DLT rules still apply to any SMS you also send, so you can add SMS later as a fallback once your registration comes through. Q: Is there an alternative to Firebase phone auth for Indian numbers? A: Miss OTP by NaCaller verifies an Indian mobile number with a missed call instead of an SMS code. The user rings the number your app shows, and the API reports the number as verified. It is a verification step, not a full auth system. It tells your server "this user holds this number", and then you create the session or set the flag in your own database, or in the auth system you already use. Because nothing is sent to the phone, there is no SMS to be delayed or filtered, and your app needs no SMS-reading permission. It works only for Indian mobile numbers, so it suits apps whose users are in India. Q: Is there an alternative to Twilio Verify or MSG91 for OTP in India? A: For Indian mobile numbers, Miss OTP by NaCaller verifies with a missed call instead of an SMS code, so you have no DLT registration or template approval to finish before launch. It is a plain REST API: POST /start, then GET /status or a signed webhook. Existing code that sends a number and waits for a verdict maps across in one small change. If some of your users can't place a call, NaCaller Voice OTP uses the same API and key to ring the user and read out a code. You can also keep your current SMS provider as a fallback rather than removing it. Q: How much does missed call OTP verification cost per number? A: Miss OTP by NaCaller costs between ₹0.10 and ₹0.20 per verified number, depending on the prepaid pack. The Starter pack is ₹199 for 1,000 verifications (₹0.20 each), and the Scale pack is ₹9,999 for 1,00,000 (₹0.10 each). You are charged one credit only when a number actually verifies. A request nobody rings, or one that expires, costs nothing. Credits do not expire, there is no monthly fee, and GST is added. Q: Can a user be tricked into sharing a missed call verification like an OTP code? A: Not in the same way. With Miss OTP by NaCaller there is no code, so there is nothing for a scammer to ask the user to read out, forward or type into a fake page. Proof comes from the call itself: the caller ID the telephone network passes to us has to match the number your user entered, within a five-minute window. It is not stronger than every attack. Caller ID can be spoofed on some routes, which is why only 10-digit Indian mobile numbers are accepted, and a SIM-swapped number would pass, just as it passes an SMS OTP. Use it for signup, login and lead checks, and add a second factor for payments or account recovery. Q: How do I verify the Miss OTP webhook signature? A: When a number verifies, Miss OTP by NaCaller sends a POST to the callback URL you set in your dashboard. The JSON body contains event "verification.verified", requestId, phone, reference, verifiedAt and a millisecond timestamp. The X-MissOTP-Signature header is a hex HMAC-SHA256 of the raw request body, keyed with your webhook secret. Compute it over the exact bytes you received, before any JSON parsing, and compare the two with a constant-time function such as crypto.timingSafeEqual in Node. The timestamp is inside the signed body, so you can reject stale deliveries to block replays. Poll the status endpoint if you would rather not expose a webhook URL. Q: What if my user can't give a missed call? A: Offer "Get a call instead". NaCaller Voice OTP uses the same API and key as Miss OTP by NaCaller. Start the verification with method "voice" and we ring the user and read a 6-digit code aloud, twice. The user types it into your app. This covers users who can't place outgoing calls, for example with no outgoing balance, and anyone uncomfortable dialling an unknown number. A good pattern is missed call as the default and the voice call behind a small link, so most verifications take the cheaper, code-free path. Q: Is there a free phone number verification API I can test in India? A: Yes. Miss OTP by NaCaller gives you 25 free verifications and 5 free voice calls per account, with your first API key and no card required. They run on the live verification line with real calls from real phones, so what you test is what ships. There is no sandbox mode. After the free verifications, prepaid packs start at ₹199. Q: What does the Miss OTP start endpoint return, and what errors can it send? A: POST https://api.nacaller.com/api/verify/start to Miss OTP by NaCaller returns requestId, phone (normalised to 10 digits), callNumber, status "pending", expiresAt, expiresIn (seconds) and a ready-made instruction sentence you can show the user. It accepts an optional reference string, up to 120 characters, that comes back in status responses and webhooks. Errors: 401 for a missing or invalid key, 400 for anything other than a 10-digit Indian mobile starting 6–9, 402 when your credits have run out, and 429 when one number has been started too often (five attempts in ten minutes) or your key sends too many requests. GET /status/{requestId} returns status as "pending", "verified" or "expired", plus verified, verifiedAt and expiresAt. ### Questions about OTP by phone call Q: What is voice OTP and how does it work? A: With voice OTP, the code is delivered by a phone call instead of an SMS. With NaCaller Voice OTP, your server starts a verification with method "voice". We call the user's Indian mobile number and read a 6-digit code aloud, twice. The user types the code into your app, and your server sends it to the check endpoint to confirm it. The code is valid for 10 minutes and allows up to 5 attempts. The call carries only the code, with no marketing and no menu. Q: How do I add a "Get a call instead" OTP fallback to my app? A: NaCaller Voice OTP is the second method in the Miss OTP API, with the same API key, credits dashboard and webhook. Your default path starts a verification as usual and asks the user to give a missed call. Under it, add a "Get a call instead" link that starts a verification for the same number with method "voice", then shows a 6-digit input. When the user submits the code, your server sends it to the check endpoint and treats a success as verified. It is one extra branch in your code, and users who can place a call never see it. Q: How much does a voice OTP call cost in India? A: NaCaller Voice OTP costs between ₹0.55 and ₹0.70 per answered call, depending on the prepaid pack. The Voice 500 pack is ₹349 for 500 calls (₹0.70 each), and the Voice 50,000 pack is ₹27,499 for 50,000 calls (₹0.55 each). The price is per answered call, not per minute. GST is added. Q: Am I charged if the user doesn't answer the voice OTP call? A: No. NaCaller Voice OTP charges only for calls the user answers. A call that rings out, is declined, or reaches a switched-off phone costs you nothing, because the unanswered call costs us nothing either. You can safely offer a retry without paying for the attempts that never connected. Q: Which languages does voice OTP support? A: NaCaller Voice OTP reads the code in English, Hindi or Telugu. The call carries only a short line and the digits, spoken slowly and read twice, so a user can write them down or type them as they listen. If you need another Indian language, tell us which one. Q: How long is the voice OTP code, and how long is it valid? A: NaCaller Voice OTP reads a 6-digit numeric code, twice on the same call. The verification is valid for 10 minutes from when your server starts it, and the user gets up to 5 attempts to type it correctly before the verification has to be restarted. Your server checks the code through the API, so the code never has to be stored or compared in your own code. Q: Can banks, NBFCs or other regulated companies use voice OTP? A: Not NaCaller Voice OTP, not yet. Entities regulated by RBI, SEBI or IRDAI, such as banks, NBFCs, brokers and insurers, have to place their service and transactional calls, including OTP calls, from TRAI's 1600-series numbers. NaCaller Voice OTP does not call from a 1600-series number today, so it is not suitable for those companies. Unregulated businesses such as marketplaces, delivery, edtech, SaaS and D2C apps can use it. Q: Do voice OTP calls break TRAI or DND rules? A: A NaCaller Voice OTP call is placed because the user asked for it on your screen, and it speaks only the verification code, with no offer, promotion or menu. That makes it a transactional call rather than a promotional one, and DND preferences are aimed at promotional calls. Keep it that way: trigger a call only from a user action such as tapping "Get a call instead", and never use the verification call to carry marketing. Promotional calling has separate rules. Q: Should I use missed call verification or voice OTP? A: Use both, in that order. A missed call with Miss OTP by NaCaller has no code for the user to type or be tricked into sharing, and it costs less per verification. NaCaller Voice OTP covers users who can't place an outgoing call or would rather receive one. Voice OTP costs ₹0.55–₹0.70 per answered call, against ₹0.10–₹0.20 per verified number for a missed call, so making missed call the default keeps most verifications on the cheaper path. Both run on the same API key and webhook. Q: Can I try voice OTP for free? A: Yes. NaCaller Voice OTP includes 5 free answered calls per account, so you can hear the call on your own phone and wire up the code check before buying a pack. These are real calls on the live line, not a simulator. After that, packs start at ₹349 for 500 calls. Q: Is voice OTP more secure than SMS OTP? A: About the same, and it is better to be honest about why. NaCaller Voice OTP still delivers a code, so like any OTP a user can be talked into reading it out to a scammer. It avoids some SMS weaknesses: nothing shows on the lock screen, and nothing sits in an inbox that other apps can read. It is not protected against a SIM-swapped number, and neither is SMS. For the lowest phishing risk, make the missed call the default, because that method has no code at all. Keep voice as the fallback, and add a second factor for payments or account recovery. ### What connects, what doesn't, and what it costs you to find out Q: What do I actually have to build? A: One HTTP POST. Your account carries a private webhook URL; send it JSON with a phone number — plus a name and a source if you have them — and you are integrated. There is no SDK, no plugin, no OAuth dance and nothing to install on your website. If your form tool can call a URL, you have already finished. Q: Do you have a Zapier app I can search for? A: No — and you don't need one. Every automation tool has a plain “Webhooks” action that posts JSON to a URL you paste in, and that is what Zapier, Pabbly Connect and Make all use here. It is one step at the end of a Zap, not an app to install or approve. Q: Can it call my Facebook and Instagram lead ads? A: Yes, through an automation tool. Zapier (or Pabbly, or Make) already reads Meta and Instagram Lead Ads; you add our webhook as the final step and the enquiry gets a phone call instead of a place in a spreadsheet. Be clear about what that means: we hold no Meta credentials and are not listed in their app directory, so the connection is only as alive as the automation tool you set it up in. Q: Which CRMs do you support? A: Any CRM that can fire an outbound webhook on a new lead, and any CRM an automation tool can watch. There is no one-click Salesforce or Zoho connector on our side, and we would rather say that plainly than put their logos on this page. If your CRM can do neither of those two things, this integration is not for you today. Q: How fast does the call actually go out? A: While they are still at the screen. The lead is written to your list and the call is queued the moment the request lands — there is no batch job that runs overnight and no list for somebody to work through in the morning. That is the entire point: the person who filled your form has not moved on yet. Q: What if a lead arrives at two in the morning? A: It is saved and queued, not dropped. Every lead source carries a calling window — a start hour, an end hour and your timezone — and a lead that arrives outside those hours is scheduled for the start of the next window instead. The response tells you so, with the reason “queued” and the exact time it will be dialled, so your own logs show what happened rather than going quiet. Q: How do I know whether the call went out? A: The response says so. You get back the lead id and a called flag, and when that flag is false it comes with a reason — the webhook is switched off, no agent has been chosen, or the lead arrived outside your calling window. No silent successes. Q: What if the same person is submitted twice? A: They stay one lead. A repeat submission of a number already on your list updates that lead rather than creating a duplicate, so a customer who fills two forms does not end up on two call lists — and your history for that number stays in one place. Q: Is the webhook URL a security risk? A: Treat it exactly like a password, because it is one: the token in that URL is the only credential, so anyone holding the URL can push leads into your account and queue calls. Don't paste it into a public repo or a shared doc. If it does leak, issue a new URL from your dashboard — the old one stops working immediately. Q: Can somebody flood it and burn my minutes? A: Each URL is rate limited to 30 requests a minute; anything beyond that is rejected outright. Your calling window and your plan's minutes are the other two brakes — and the switch that turns the whole thing off is one click. Q: What is TalkingWP and is it part of NaCaller? A: It is our own website chat and voice assistant, so it connects properly rather than through a middleman. Authorise it once and the leads, appointments, conversations and sites it captures mirror into NaCaller tagged by website. The access is read-only — we cannot delete anything on that side — and disconnecting removes the synced copies from here. Q: Can I send a whole list this way? A: You can, but don't. The webhook is built for one lead the second it appears; a list of two thousand belongs in a CSV or Excel import running as a campaign, where retries, calling windows and pacing are handled for you. Use the webhook for speed, the import for volume. Q: Which plan do I need for this? A: Instant lead calling is set up from the Integrations screen inside your account, and the free tier's 10 minutes are enough to watch a real form submission turn into a real call before you pay anything. Broader API access and outbound webhooks are listed on the Scale plan on our pricing page.