Telecaller · Tamil தமிழ்
Tamil telecaller interview questions: screen for Chennai BPO, EdTech and BFSI campaigns
Chennai is a major domestic BPO hub for Tamil-language insurance, banking and EdTech campaigns. Screen for rejection resilience, TRAI compliance and diglossia awareness in Tamil before training begins.
Start free trialShort answer
To screen Tamil telecallers for Chennai BPO, BFSI collections, insurance outbound and EdTech admission calling across Tamil Nadu, the highest-signal questions test rejection resilience in Tamil, TRAI DND rule awareness, and spoken Tamil register appropriate for a customer call — specifically the diglossia gap between literary Tamil (centamil) and spoken colloquial Tamil (koṭuntamiḻ). Shynsa conducts the full AI voice interview in Tamil and returns a scored shortlist. It does not verify employment records or background.
Market context
Why Tamil-language telecaller hiring needs a dedicated screen
Tamil is the primary language for domestic BPO campaigns targeting Tamil Nadu's 80 million population. Chennai's BPO market covers insurance outbound (LIC, HDFC Life, SBI Life Tamil campaigns), NBFC personal loan and home loan collections, EdTech admission calling (PhysicsWallah, BYJU's, regional coaching chains), government service outreach and FMCG survey calling. The Tamil telecaller pool spans Chennai urban Tamil, Coimbatore and Madurai regional registers, and candidates from northern Tamil Nadu (Vellore, Tiruvannamalai, Krishnagiri) with distinct phonological features.
Chennai (OMR, Ambattur, Guindy BPO belt)
Largest Tamil-language domestic BPO concentration. Chennai colloquial Tamil is the benchmark register for most Tamil-language campaigns. Candidates are often trilingual (Tamil, English, Hindi).
Coimbatore and Salem
Growing BPO presence, particularly BFSI and insurance telecalling. Kongu Tamil dialect with distinct vocabulary patterns. Important candidate source for Tier 2 Tamil Nadu campaigns.
Madurai and Tirunelveli
Southern Tamil Nadu. Madurai Tamil and Tirunelveli Tamil have distinct register and vocabulary features. Customer base for rural insurance and NBFC campaigns in this geography.
Vellore and Tiruvannamalai
Northern Tamil Nadu border region. Tamil spoken here has some phonological overlap with Telugu and Kannada regions. Growing source of first-time BPO candidates.
Dialect & register
Tamil register and diglossia notes for telecaller screening
Tamil has the most significant diglossia gap of any major Indian language — the gap between written/formal Tamil (centamil) and spoken colloquial Tamil (koṭuntamiḻ or pēccu Tamil) is wider than in Hindi, Telugu or Marathi. Telecaller screening must assess spoken colloquial Tamil — not formal or literary Tamil — because a formal Tamil register in a customer call sounds stilted and distant, reducing customer rapport.
Diglossia: literary Tamil vs. spoken Tamil
Tamil's diglossia means that the formal written form ('nīṅkaḷ eppōtu varukirīrkaḷ?') and the natural spoken colloquial form ('nīṅka eppa varuvaṅka?') are significantly different. A candidate who defaults to literary Tamil in a customer call sounds like they are reading a government notice — comprehensible but creating social distance. Screen for natural colloquial spoken Tamil, not literary Tamil.
Honorifics: second-person plural as respectful form
In spoken Tamil, the second-person plural ('nīṅka' — நீங்க) is the standard respectful form for adult customers — equivalent to 'aap' in Hindi. Using the singular 'nī' (நீ) with a customer is a severe register breach. Screen for consistent 'nīṅka' usage in the simulated customer call.
Regional dialect variation: not a disqualifier
Coimbatore Kongu Tamil, Madurai southern Tamil and northern Tamil Nadu border-region Tamil each have distinct vocabulary and phonological features. These are mutually intelligible across Tamil Nadu for practical customer communication. A Madurai-accented candidate calling a Chennai customer is universally comprehensible. Do not mark down regional accent — assess comprehensibility and colloquial register.
Number words and financial vocabulary in Tamil
Tamil financial amounts: 'āyiram' (ஆயிரம்) for 1,000, 'pattu āyiram' (பத்து ஆயிரம்) for 10,000, 'oru latcham' (ஒரு லட்சம்) for 100,000. Test articulation of financial amounts directly in Tamil — particularly for BFSI and collections campaigns where rural Tamil Nadu customers expect amounts stated in Tamil.
Hiring pain points
Tamil telecaller hiring pain points that standard screening misses
Literary Tamil used in call scripts creates customer distance
Many Tamil BPO call scripts are written in literary Tamil for 'professionalism'. A candidate who reads these scripts in full literary Tamil creates rapport distance with colloquial-Tamil-speaking customers. Screen whether the candidate can deliver the script's intent in natural spoken Tamil, not just read the literary text.
TRAI compliance awareness not tested in Tamil
DND rules and time-window awareness are tested in English questionnaires for many Tamil BPO hires. Test specifically in Tamil for Tamil-language campaigns.
EdTech admission season creates mass screening pressure
Tamil Nadu's large engineering and medical admission season (June–July) creates mass telecaller hiring pressure for EdTech and coaching chains. Quality of screens drops during peak hiring periods — structured screening is especially important when speed is highest.
Incentive discussion not held in Tamil for Tier 2 candidates
Candidates from Coimbatore, Salem or Madurai may not fully understand English incentive structures. Hold the incentive expectation conversation in Tamil to ensure genuine comprehension.
11 questions in Tamil
Tamil telecaller interview question bank
All questions presented with native Tamil text, English gloss, test signal and scoring signals. Minimum 12 questions across 4 categories. Conduct the full interview in spoken colloquial Tamil — not literary Tamil.
Rejection resilience in Tamil
Assess whether the candidate can maintain professional Tamil conduct under repeated simulated rejection.
Oru customer phone la romba kuṭṭam solrāṅka, arumaiyāka pēsāma irundāṅka — adukku apuram nīṅka eppa feel pannuvaṅka? Eppaṭi reset pannuvaṅka?
A customer speaks very rudely on the phone. After that, how do you feel and how do you reset yourself?
Tests: Emotional regulation between rejection calls — specific reset mechanism
Strong signals- Specific reset action described in spoken Tamil: short pause, breath, 'next call la focus panna try pannuvēn'
- No emotional bleed to the next call
- Frames rude customer as 'avāṅka samsya, en samsya illa'
Weak signals- Needs extended break — 'kaṣṭamā irukku, suvāsikkanum'
- No specific reset mechanism described
- Anger or deflation audible in spoken register after simulated aggression
Nāḷu poḷa 100 calls paNNiṭṭu oru conversion-um ille. Sāyankāla enna ninaikkirīṅka?
A whole day, 100 calls, zero conversions. What do you think at the end of that day?
Tests: Attribution of failure — internal learning vs. external blame for a poor conversion day in Tamil
Strong signals- Reflects in Tamil on what could change: list quality, timing, specific phrase that did not work
- Returns next day with adjustment; no generalised blame of product or market
Weak signals- All attribution to external factors in Tamil: 'product sari illa', 'market manda'
- No personal performance analysis
- Considers quitting or reducing effort
Customer phone la koṇḍam pēsāṭṭā, vayal moḻi pēsāṭṭā — nīṅka eṉṉa panṇuvaṅka? Step by step solluṅka.
If a customer speaks abusively, what do you do step by step?
Tests: Process under verbal aggression — policy adherence in Tamil
Strong signals- Calm Tamil warning; documented disconnection if abuse continues; escalation to supervisor; awareness of call recording
- Professional Tamil tone maintained — no matching abusive language
Weak signals- Argues back in Tamil
- Hangs up without documentation
- Absorbs silently with no process
TRAI compliance awareness in Tamil
Confirm the candidate understands DND rules and calling time restrictions — in Tamil, the language they will apply these rules.
Oru customer DND la register āgirāṅka. Avaṅkalukku call pannalāmā, pannakūṭādā?
A customer is registered on DND. Should you call them or should you not?
Tests: DND rule awareness assessed in Tamil — knockout criterion
Strong signals- 'Pannakūṭādu — avaṅka number list la irundā teṟikkaṇum' — clear do-not-call in Tamil
- Understands DND as a legal protection, not a customer preference to work around
Weak signals- 'Pākkalam enna solrāṅkaṉṉu' — tries anyway
- No awareness of DND meaning
- Thinks verbal consent overrides DND registration
Promotional calls paNNa TRAI time rule enna? Kāla ennana maNikku start paNNalām, iravu ennana maNikku varai paNNalām?
What is the TRAI time rule for promotional calls? From what morning time to what evening time?
Tests: 9 AM–9 PM time window awareness in Tamil
Strong signals- 'Kāla oṉpadu maNi mutal iravu oṉpadu maNi varai' (9 AM to 9 PM) — correct Tamil articulation
- Understands it is a legal restriction
Weak signals- No awareness of any time restriction
- States an incorrect window
- 'Customer eppavāvadu irundā pannalām'
Manager oru guarantee sollu nu sollāṅka — product la ille oru guarantee — nīṅka enna paNNuvaṅka?
If a manager tells you to give a guarantee not in the product, what do you do?
Tests: Ethical floor: refusing mis-selling instruction in Tamil
Strong signals- Refuses in Tamil; offers to escalate; understands personal risk: 'customer ku poyyā solradu tappu'
Weak signals- 'Manager solrāṅka, paNNaṇum' — blind compliance
- No awareness of personal liability
Tamil language quality and register
Assess spontaneous spoken colloquial Tamil register, honorific usage, number articulation and diglossia awareness.
Tamil la solluṅka: vāzhkayil yārāvatu oru product pathi explain pannirukkirīṅkala? Enna product, enna solliṅka?
Tell me in Tamil: in everyday life, have you explained any product to anyone? What was it and what did you say?
Tests: Spontaneous spoken colloquial Tamil production in a sales register — register, 'nīṅka' honorific, code-switching
Strong signals- Natural colloquial Tamil delivery ('koṭuntamiḻ') with 'nīṅka' honorific when referencing customer
- Benefit-first explanation even in a casual narrative
- Code-switching (English product terms in Tamil sentence) natural and comprehensible
Weak signals- Literary Tamil register that sounds like reading a government notice
- Uses 'nī' with customer — wrong register and rapport-damaging
- Cannot maintain colloquial Tamil — reverts to English for core content
Inda amounts Tamil la solluṅka: oṉṟu latcham irupadu āyiram rūpāy. Mari: iraṇdu latcham aimbadu āyiram rūpāy.
Say these amounts in Tamil: ₹1,20,000. And: ₹2,50,000.
Tests: Financial number articulation in Tamil — critical for BFSI and collections calls
Strong signals- 'Oṉṟu latcham irupadu āyiram rūpāy' and 'iraṇdu latcham aimbadu āyiram rūpāy' — clear and unhesitating in Tamil
- Natural Tamil number-word flow without reverting to English
Weak signals- 'One lakh twenty thousand' — English only
- Significant hesitation
- Mixes Tamil and English digits confusingly
[Roleplay] Nāṉ customer. Nīṅka eṉakku oru personal loan pathi Tamil la solluṅka. Nāṉ 'eṉakku interest illa' sonnā, eppaṭi handle paNNuvaṅka?
[Roleplay] I am the customer. Tell me about a personal loan in Tamil. If I say 'I am not interested', how do you handle it?
Tests: Full Tamil outbound call simulation in colloquial Tamil — opening, benefit statement, one objection handling
Strong signals- Professional colloquial Tamil opening with 'nīṅka' honorific; benefit-first explanation; handles 'interest illa' with one clarifying question before accepting rejection; professional Tamil close
- No mandatory disclosure missing; no literary Tamil register
Weak signals- Switches to English for core explanation
- Uses 'nī' without invitation
- Cannot handle the objection — over-pushes or immediately gives up
Shift commitment and income expectations in Tamil
Confirm shift availability and incentive understanding in Tamil for genuine comprehension.
Inda role la fixed salary thaviṟa incentive-um irukkum. Oru mādam incentive zero āṉāl — fixed mattum vanthāl — mee vīṭṭu kharchu ku podhum-ā?
This role has fixed salary plus incentive. If incentive is zero in a month — only fixed comes — will it be enough for household expenses?
Tests: Income expectation reality check in Tamil — genuine understanding of fixed/variable pay structure
Strong signals- Specific, calculated Tamil answer; confirms the fixed amount is manageable with reasoning
- No evident shock when the fixed figure is stated in Tamil
Weak signals- Expected only the total CTC; unaware of variable incentive structure
- Needs question restated in English before answering
Inda role ku [shift time] required, vaāram la 6 nāḷ. Nīṅka inda shift prathi vaāram exact-ā cover paNNa muḍiyumā?
This role requires [shift time], 6 days per week. Can you cover this shift exactly every week?
Tests: Unhedged shift commitment in Tamil
Strong signals- Clear 'ām, muḍiyum' in Tamil with no hedging when probed
- Home situation and commute discussed and confirmed compatible in Tamil
Weak signals- Conditional commitment in Tamil
- Undisclosed constraint surfaces on probing
- 'Pākkalam' — not a commitment
Scenarios
Roleplay scenarios for telecaller candidates in Tamil
Angry customer who has been called multiple times
[Roleplay] Nāṉ oru customer — inda vaāram mūṉṟu thaṭavai call vanthadu. Nīṅka call pannāl nāṉ kobbappaḍuvaṉ. Tayāra āṅka.
[Roleplay] I am a customer who has received three calls this week. When you call, I will be angry. Get ready.
Listen for
- Does the candidate open in natural colloquial Tamil ('Namaskāram, [name] sir/madam pēsurīṅkalā?') before the aggression begins?
- When the customer expresses anger in Tamil, does the candidate use acknowledgement language in natural Tamil?
- Does the candidate offer to flag the number for removal rather than arguing?
- Is the call closed professionally in Tamil even if unresolved?
Weak: Argues in Tamil about whether three calls is too many; uses defensive language; cannot close professionally
Acceptable: Acknowledges frustration; offers removal; closes professionally — but language slightly stilted rather than natural colloquial Tamil
Strong: Natural colloquial Tamil throughout; specific empathetic acknowledgement; number-removal offered unprompted; clean professional Tamil close
Customer claims DND status
[Roleplay] Nīṅka call pannāl, nāṉ solrēṉ: 'Nāṉ DND la irukēṉ, nīṅka call pannakūṭādu.' Nīṅka enna paNNuvaṅka?
[Roleplay] When you call, I say: 'I am on DND, you should not call me.' What do you do?
Listen for
- Does the candidate apologise and confirm number removal in Tamil immediately?
- Does the candidate avoid arguing under Tamil-language live pressure?
- Is the call closed professionally in Tamil within 30 seconds?
- Does the candidate confirm in Tamil that the number will not be called again?
Weak: Argues in Tamil; continues the pitch; hangs up without acknowledging
Acceptable: Apologises and closes; confirms no further calls — takes a moment to recall correct process in Tamil
Strong: Immediate Tamil apology; specific Tamil confirmation of number removal; professional close in under 20 seconds
Customer demands a guarantee
[Roleplay] Nāṉ customer. Nāṉ solrēṉ: 'Oṉṟu varuṣattila ennoda paṇam iraṭṭippāgum-ṉu guarantee kuduṅka, appuṟam mattum vaṅkiṟēṉ.' Nīṅka enna paNNuvaṅka?
[Roleplay] I say: 'Give me a guarantee my money doubles in a year, then I will buy.' What do you do?
Listen for
- Does the candidate refuse the guarantee in natural Tamil without being rude?
- Does the candidate explain what the product actually offers in honest Tamil?
- Does the candidate offer supervisor escalation rather than the false promise?
- Is the interaction closed professionally in Tamil even without the sale?
Weak: Gives the guarantee in Tamil to close the sale — a direct mis-selling event
Acceptable: Refuses; explains actual offer; loses the sale but stays within compliance
Strong: Refuses in empathetic natural Tamil; redirects to actual offer; offers escalation; keeps relationship open in professional Tamil close
Scoring rubric
Tamil telecaller scoring rubric
Score each dimension 1–5. Weights sum to 100. Conduct the full interview in spoken colloquial Tamil. Regional dialect (Coimbatore, Madurai, Chennai) is NOT penalised — only comprehensibility and appropriate register are assessed.
| Dimension | Weight | 1 — weak | 3 — acceptable | 5 — strong |
|---|---|---|---|---|
| Rejection resilience Assess resilience specifically in the Tamil roleplay. A candidate who maintains professional tone in English but becomes reactive in Tamil has language-specific emotional regulation that will show on live calls. | 28% | Becomes distressed or matches customer aggression in Tamil during roleplay | Maintains professional Tamil tone under moderate aggression; reset mechanism described though generic | Absorbs full Tamil roleplay aggression without tone change; specific colloquial Tamil de-escalation phrases used spontaneously |
| TRAI compliance in Tamil Compliance awareness must be tested in Tamil specifically. Candidates who know rules in English but cannot apply them in Tamil call pressure are a compliance risk in a Tamil campaign. | 22% | No DND awareness; cannot state calling time window in Tamil; would comply with mis-selling instruction | States 9 AM–9 PM window correctly in Tamil; correct DND response; some hesitation on mis-selling refusal | All TRAI responses immediate and correct in Tamil; mis-selling refusal principled; financial amounts articulated in Tamil fluently |
| Tamil communication quality Assess spontaneous COLLOQUIAL Tamil register — not literary Tamil. 'nīṅka' honorific is essential. Regional accent is NOT penalised. Literary Tamil register in a customer call is itself a scoring issue because it creates rapport distance. | 25% | Uses literary Tamil register; uses 'nī' with customer; reverts to English for core content; number articulation in English only | Natural colloquial Tamil delivery with minor code-switches; 'nīṅka' consistent; financial amounts in Tamil mostly correct | Fully natural colloquial Tamil throughout; 'nīṅka' honorific; financial amounts in Tamil without hesitation; code-switching purposeful and comprehensible |
| Shift and income commitment Income structure discussion in Tamil ensures genuine comprehension for Tier 2 Tamil Nadu candidates less confident in English. | 15% | Income expectation significantly above fixed component; shift commitment hedged in Tamil | Income expectation aligned; shift confirmed in Tamil with minor uncertainty | Income sustainability confirmed in Tamil with reasoning; shift unequivocally confirmed in Tamil |
| Script discipline and compliance awareness Does the candidate follow the Tamil script structure in roleplay — particularly in the natural colloquial register — or revert to literary Tamil or English for mandatory disclosures? | 10% | Skips mandatory disclosures in Tamil roleplay; improvises in English | Mostly follows script in Tamil; one omission; accepts script rationale | Full colloquial Tamil script adherence in roleplay; mandatory disclosures present; can articulate in Tamil why script exists |
Decision bands
Fast-track to Tamil BPO/collections team
Proceed; flag specific Tamil language gap to onboarding
Run all three roleplay scenarios before deciding
TRAI compliance gap, Tamil communication below threshold, or integrity concern
Fairness
Accent, dialect and diglossia bias guardrails for Tamil telecaller screening
Tamil has significant regional dialect variation (Chennai, Coimbatore/Kongu, Madurai/Nellai, northern Tamil Nadu) and a wide diglossia gap between literary and spoken Tamil. Screening must separate accent and dialect from competence, and must NOT penalise natural colloquial Tamil register.
- Regional dialect (Coimbatore Kongu Tamil, Madurai southern Tamil, northern Tamil Nadu border Tamil) is NOT penalised. Only comprehensibility — would the target Tamil Nadu customer understand this candidate? — is assessed.
- Using 'nī' instead of 'nīṅka' IS a register error that should be scored — this is conduct, not dialect.
- Using colloquial Tamil register instead of literary Tamil in a customer call is CORRECT — not a failure. Literary Tamil in a live customer call creates rapport distance.
- Only penalise dialect or vocabulary features that create genuine comprehension difficulty for the specific customer population of the campaign.
- Code-switching to English for product terms is natural and acceptable if the Tamil sentence structure remains dominant.
- Shynsa does not conduct facial analysis or emotion detection. All scoring is based solely on spoken content and competency signals.