Punjabi AI Receptionist Punjab Cost: ₹2/min

Every line that can appear on your bill is in this table. These are our own published figures (Dvaarik pricing, checked 29 Jul 2026), and all amounts are exclusive of GST — 18% GST is applied at the moment you load credits, not per call.

Two things follow from that structure. First, a quiet month costs you almost nothing beyond the number — there is no seat fee waiting for you whether the phone rings or not. Second, the whole-minute rounding is the only rounding there is: a 40-second call in Punjabi is one billed minute, ₹2. We do not bill per second and do not pretend to. Full terms sit on the pricing page.

A business call in Punjab does not open the way a textbook does. It opens with ਹਾਂ ਜੀ — *haan ji* — often before the caller has said what they want, and often before your side has finished saying the shop name. ਸਤ ਸ੍ਰੀ ਅਕਾਲ is the greeting on many lines, especially in Amritsar and among older callers, and the reply is expected in kind rather than with a corporate script.

The ਜੀ particle does most of the politeness work in the language, and it attaches to almost anything: *haan ji*, *theek aa ji*, *nahi ji*, *dasso ji*, *chalo ji*. A Punjabi agent that drops *ji* sounds curt even when every word is correct. Kinship address is the default register on a trade line — *veer ji*, *bhaji*, *paaji*, *bhabhi ji*, *bibi ji*, *chacha ji*, *sardar ji*, *madam ji* — and a caller who opens with *veer ji* is not being informal, he is being normal.

Then there is the ਤੁਸੀਂ / ਤੂੰ choice. *Tusi* is respectful and safe; *tu* is familiar. A Malwa caller who says *tu* to your receptionist is usually signalling warmth rather than disrespect, and an agent that stiffens into formal Punjabi in response reads as cold. Our rule for Punjabi builds is simple: the agent always uses *tusi* with *ji*, and never mirrors *tu* back at the caller.

The verbs also give the region away. Punjabi's *aa / ne* copula in Malwa and Doaba, against the *hai / han* forms a Hindi-schooled speaker in Chandigarh may reach for, is one of the most audible differences between a Ludhiana caller and a Chandigarh caller saying exactly the same sentence.

Punjabi callers do not switch languages so much as build one sentence out of three. The grammatical frame stays Punjabi, the commercial nouns come out in English, and in Chandigarh and Delhi NCR, Hindi words slot in without anyone noticing.

A real-shaped sentence from an auto-parts line, invented as an example and not taken from any client: *"Haan ji, tuhade kol Swift de front shocker available ne? Rate ki aa, te GST bill mil jauga?"* Five English items — front, shocker, available, rate, GST bill — inside a fully Punjabi sentence. An immigration enquiry does the same with its own vocabulary: *"Bai ji, overall 6.5 band aa, ik vich 6 aa — September intake da file lag sakda?"* Here *band*, *intake* and *file* are load-bearing terms with fixed English forms; translating them into Punjabi would make the sentence harder to understand, not easier.

There is a second layer in Delhi NCR and Chandigarh. Punjabi families there frequently speak Hindi with Punjabi phrasing and Punjabi discourse markers, and may start a call in Punjabi and finish it in Hindi without treating that as a change of language. An agent that tries to drag such a caller back into Punjabi mid-call is actively annoying.

So the rule we build to is: detect from the caller's first words, follow every switch, never announce the switch, and never run a press-1 language menu. A Punjabi caller should never hear *"for Punjabi, press 2"*. More on how that is wired sits on the multilingual page and the voice agent page.

This is where a language page earns its keep. These are mechanisms, not accuracy claims — we publish no Punjabi accuracy percentage, because a number we cannot let you audit is worth nothing.

1. Punjabi has tone, and almost no other big Indo-Aryan language does. Punjabi developed three lexical tones when the old voiced-aspirate series was lost, and Gurmukhi's ਘ, ਝ, ਢ, ਧ, ਭ letters now signal tone rather than a murmured consonant (Gurmukhi and Punjabi dialect entries, Wikipedia, and Evans, *Acoustics of Tone in Indian Punjabi*, both checked 29 Jul 2026). The textbook triple — ਘੋੜਾ *horse*, ਕੋੜਾ *whip*, ਕੋੜ੍ਹਾ *leprosy-afflicted* — differs largely in pitch. A recogniser tuned on Hindi can flatten exactly that pitch information, because in Hindi it carries nothing.

2. The consonants Hindi does not have. The retroflex flap ੜ against ਰ, and ਣ against ਨ, are contrastive. So is the adhak gemination: ਪੱਕਾ is not ਪਕਾ. On a compressed phone line these distinctions are easy to lose.

3. Time and number arithmetic done in words. Appointment times arrive as ਸਵਾ, ਸਾਢੇ, ਪੌਣੇ, ਡੇਢ, ਢਾਈ — *paune teen* is 2:45, *saade chaar* is 4:30, *dedh vaje* is 1:30. Get the modifier wrong by one step and the customer arrives half an hour out. Punjabi's teens and twenties are also irregular enough that speakers often switch to English digits mid-sentence, so a single sentence can carry *saade sat* and *seven thirty* meaning the same slot.

4. Trade units. Land comes in killa, kanal and marla — 1 killa is 1 acre and 8 kanal, and in current Punjab practice a kanal is taken as 20 marla, though older revenue records use a 22-marla kanal (*Measurement of land in Punjab*, Wikipedia, checked 29 Jul 2026) — and crops in quintals and trolleys. A generic agent hears "das marle" and stores nothing useful.

5. Names and villages. Singh and Kaur are shared names by convention across a great many callers, so the surname does not disambiguate anybody; the given name spelling does (Gurpreet, Gurprit, Gurpret) and the village does ("Pind Rajewal, Nakodar de kol"). The agent has to be built to spell back and to capture the village as an address anchor.

6. The line itself. A Ludhiana shop floor with presses running, a tubewell motor behind a farmer at six in the morning, a hands-free on the Ludhiana–Chandigarh highway, and fast clipped speech from someone who repeats the same sentence all day. We build assuming those conditions are the ordinary case, not the edge case.

Punjabi-language call volume in Punjab, Chandigarh and Delhi NCR tends to sit in a handful of phone-heavy trades, each with its own failure mode. All scenarios below are invented examples, written to be realistic — none is a client and none describes an observed client. Treat the patterns as things to check against your own call log, not as findings we have measured.

Agriculture equipment and inputs. Seed, urea and DAP counters, pesticide dealers, tractor and implement showrooms, tubewell and pump repairers. You would expect volume to track the crop calendar — around ਝੋਨਾ transplanting in June and ਕਣਕ sowing in late autumn — and a fair share of calls to come early in the morning from a field, on speakerphone, over a running motor. *Invented example:* "Veer ji, 12 HP di motor da impeller aa? Te trolley te ghar tak pahuncha dyoge, pind Jagraon lagda?" What the caller needs is availability, a price, and whether you deliver. Nobody wants a callback four hours later.

Immigration and IELTS consultancies. A heavily phone-driven trade in the Doaba belt around Jalandhar, Hoshiarpur and Kapurthala, and present in Chandigarh and Ludhiana too. Enquiries cluster around intakes and result days. *Invented example:* "Ji, IELTS batch da fee kinni aa, te weekend classes hondiyan ne?" A consultancy's phone is its whole funnel, which is why our Leads agent is built to ring an enquiry back in roughly 60 seconds rather than at the end of the day. See coaching for how we set those flows up.

Auto parts and the Ludhiana industrial trade. Parts, fasteners, cycle components, hosiery and machine shops. The call is a specification exchange: model, year, variant, part number, quantity, whether a GST bill is coming, and which transport it goes on. *Invented example:* "Bhaji, part number PB-2214 da rate dasso, do dozen chahide ne, bill naal." See wholesale traders and automobile.

Sweets, halwais and caterers. Amritsar, Ludhiana and every NCR Punjabi wedding market. Volume is tied to wedding dates, Lohri, Diwali and Karva Chauth, and the questions are per-plate rate, menu, minimum plates, advance and delivery date. *Invented example:* "Ji, 22 tareek nu 300 bandeyan da vegetarian menu — per plate ki lagega, te advance kinna dena paina?"

Property. Mohali, Kharar, Zirakpur, the Chandigarh periphery and Punjabi-speaking pockets of NCR. The vocabulary is marla and kanal, ready-to-move, possession, registry, and the caller wants a site visit slot. See real estate.

Both businesses below are invented and sized to be ordinary rather than flattering. Minutes are *billed* minutes, meaning every call is already rounded up to the next whole minute. All talk time is at ₹2/min, all chat at ₹2 per conversation, and every figure is ex-GST — the 18% is charged once, when credits are loaded.

Example A — a Jalandhar immigration and IELTS consultancy

Heavy inbound in Punjabi and Punjabi–English, plus WhatsApp follow-up on their own number. Assume 900 billed minutes and 250 chat conversations in a month, on a number we supply.

Month one in practice: load the ₹10,000 minimum, billed ₹11,800 including ₹1,800 GST. That month's ₹9,300 of debits leaves roughly ₹700 of credit going into month two. Month two looks the same, because the Care Plan is required for the first three months — so a top-up of about ₹8,600 (billed ₹10,148 with GST) covers it. From month four the Care Plan is optional and the same usage costs ₹4,300 ex-GST. The ₹40,000 build is ₹0 as a founding client.

Example B — a Ludhiana auto-parts wholesaler

Shorter, denser calls: availability, rate, quantity, transport. Assume 450 billed minutes, 120 chat conversations, number supplied by us.

Notice what dominates at low volume: at 450 minutes the ₹2,000 number is more than double the talk time. If you already have a Ludhiana landline that customers know by heart, keeping it and forwarding it removes that line entirely and takes month four to ₹1,140. If you want to sanity-check the other side of the ledger — what unanswered calls are costing you now — the missed-call calculator does that arithmetic separately.

Described mechanically, because ₹2 a minute only means something once you know what is happening inside the minute.

Inbound. It answers every call, including at 11pm and during the lunch rush when your counter is already on another line. It opens in Punjabi with the *ji* register rather than a corporate script, identifies your business by name, and works through the flow you approved — answering the questions your counter answers all day, quoting rates you gave us, checking real open slots, holding one while it confirms details, and sending a WhatsApp confirmation from your own number. It handles Punjabi, Hindi and English in the same call and follows a caller who drifts from Punjabi into Hindi mid-sentence without restarting or announcing the switch.

Leads. When a form or an ad lead lands, the Leads agent calls that person back in roughly 60 seconds, in Punjabi, and writes the answers into a lead sheet you can read. For an IELTS consultancy that means a September-intake enquiry is spoken to while the person is still at their phone.

Booking, payments, chat. Booking locks the slot rather than double-promising it, and sends reminders — including for times given as *paune teen* or *saade chaar*, which it confirms back in both Punjabi and digits. Payments can send a payment link mid-conversation for an advance or a token — a caterer taking a wedding-order advance, say — with no commission taken by us. WhatsApp runs on your own number with your own Meta account, so Meta bills you directly at zero markup, and Instagram handles DMs and comment-to-DM.

Transcripts. Every call comes back as a transcript with a summary, and for Punjabi we can render it in Gurmukhi (ਪੰਜਾਬੀ) or in Roman Punjabi — whichever your staff reads faster. Structured fields come out separately from the transcript so they are usable: the spelling of a Gurpreet or a Gurprit, the village as an address anchor, a part number spoken with letters and digits mixed, a plate count, a plot quoted in marle or kille.

What it will not do: it does not call purchased lists. Outbound goes only to your own leads and your own customers. The legal position on that is set out in is AI calling legal in India.

Some Punjab businesses take enquiries from outside India — families connected to Punjab who live abroad and ring at their own evening, which lands in the Indian night or the very early morning. Whether that describes your phone is something you know and we do not, so check your own call log before you weigh it. If it does describe you, the shape is familiar: a son in Brampton phoning a Jalandhar consultancy about his cousin's file, a family in Southall calling an Amritsar caterer about a wedding date, an owner in Surrey calling a Mohali property dealer about a plot in the family name.

That is exactly the volume a human receptionist cannot cover and a missed-call callback handles badly. By the time your office opens at ten, the overseas caller is asleep, and the callback lands in their night — a loop that can run for days over a question that takes a minute to answer. An always-on agent removes the loop rather than compressing it: the call is answered when it arrives, in Punjabi, from your own answer sheet, with the details captured and a WhatsApp summary sent to both sides. Your team reads a filled-in enquiry at 10am instead of a missed number.

That traffic also skews toward questions nobody should answer casually, which is where the second half of this section starts. An immigration or IELTS consultancy's phone gets asked some version of *"6 band naal visa lag jauga?"* or *"pichli refusal si, hun file lag sakdi?"*. Those are outcome questions about a regulated process, and no AI agent — ours included — should answer them. We build the Punjabi flows so it does not try: acknowledge the question in Punjabi, capture the specifics a counsellor needs (scores, intake, prior refusal, target country), state plainly that a counsellor will assess the case, then book the slot or hand the call to a person. The same discipline applies elsewhere — a clinic agent books appointments and does not diagnose, a property agent gives listed prices and site-visit slots and does not opine on registry or title.

There is a commercial version of the same rule: the agent quotes only rates you have written down for us, and it will not bargain.

This page is only worth reading because this section exists.

Your call volume is genuinely low. Below roughly 200 minutes a month, the ₹2,000 number charge dominates everything — 200 minutes is ₹400 of talk time against a ₹2,000 line — and the honest answer may be a person and a phone. If you can keep and forward an existing number the maths improves immediately, because that line drops to ₹0.

Every call is a negotiation. If your price is discovered by haggling on each call — daily mandi-linked rates, second-hand parts, scrap — the agent can capture, qualify and book, but it will not bargain for you, and pretending otherwise would waste your money. Use it for capture and booking and keep the pricing conversation human.

You have no answer sheet. The agent is exactly as good as the rates, timings, policies and stock information you can give us. If availability lives in one person's head and a godown nobody has listed, build the list first. That is not a Dvaarik problem, it is a prerequisite.

Somebody already answers within two rings, always. A single-counter shop with a person permanently on the phone and flat volume does not have the leak this fixes. Spend the money elsewhere.

You need Shahmukhi. Punjabi in India is written in Gurmukhi. If your requirement is Shahmukhi-script correspondence for counterparties on the other side, say so up front so we can scope it honestly rather than discovering it at go-live.

You want a bought-list dialler. We only call your own leads and your own customers. If the plan is a purchased Punjab database, we are the wrong vendor, and you should read is AI calling legal in India before you buy from anyone.

Do not take our word for any of the language claims above. Our own agent is live and you can attack it in Punjabi right now: it answers on WhatsApp at +91 93923 98750, and there is a browser version at app.dvaarik.com/dvaarik-ai. Speak Punjabi to it, not English, and try the things this page says are hard.

A short test list, in the order we would run it:

1. Open the way a real caller does. Start with *"Haan ji, sat sri akal"* and say nothing else. See whether it comes back in Punjabi without a menu.
2. Break the sentence. Start in Punjabi, drop three English nouns in the middle — *available*, *rate*, *GST bill* — and finish in Hindi. It should follow you without restarting.
3. Give a time the Punjabi way. Say *"paune teen vaje"* or *"saade chaar"* and check what comes back on the confirmation. Then change your mind to *"dedh vaje"* mid-call.
4. Give a trade unit. *"Das marle da plot"*, *"do kille"*, *"do quintal"*, or a part number spoken fast with letters and digits mixed.
5. Spell a name. *"Gurpreet Singh, pind Rajewal, Nakodar de kol."* Check whether the spelling and the village both survive into the summary.
6. Talk over noise. Put it on speaker with a fan or a TV running, the way your customers actually call.

If it fails one of those, tell us which one — that is more useful feedback than any brochure. And when you are ready, we need three things to build: your answer sheet, your working hours and holiday pattern, and the number arrangement. The founder builds each agent personally and the usual turnaround is days, not months. How it works sets out the build sequence, and the pricing index has the wider market numbers if you are comparing quotes.