Skill ID: C2

Compliant Call-Script Generator (Multilingual)

Scripts your agents can read out without creating a compliance incident.

Paste it into Claude, ChatGPT or Gemini. It introduces itself and tells you what to share.

CollectionsCompliance load HighHuman review requiredRuns on Claude, ChatGPT or Gemini

What you get

Feed it
Product, DPD bucket, contact history, borrower language and the verified account facts.
You get
The main script in the borrower's language, the branch scripts, and a prohibited-phrases box.
Takes
About five minutes, on whichever LLM your team already opens.

Why this beats a prompt you'd write yourself

  • Identity disclosure and third-party rules are built into the script itself.
  • Drafted natively in Hindi, Tamil, Marathi, English or Hinglish.
  • Tone escalates by bucket and contact history, never improvised.
  • States only the account facts you supply, so no invented consequences.

Example

See a worked example

MAIN SCRIPT (SMA-1, PL, broken PTP, Hinglish — excerpt): "Namaste, main [Agent] bol raha hoon [RE Name] se. Kya meri baat [Borrower] ji se ho rahi hai? … Kya abhi baat karna convenient hai? … [Borrower] ji, aapke personal loan ka EMI ₹8,450, due 5 June, abhi tak clear nahi hua hai. Aapne 20 June ko payment ka commitment diya tha. Main samajhna chahta hoon — koi dikkat aa gayi thi kya? … [If no hardship:] Aaj hum isse close kar sakte hain — main aapko payment link bhej raha hoon…"

BRANCH (a) — third party answers: "Namaste, main [Agent] bol raha hoon. Kya [Borrower] ji available hain? … Theek hai, please unhe [number] par call back karne ko keh dijiye." (No mention of loan, institution purpose, or dues.)

PROHIBITED-PHRASES BOX: No police/arrest references · No "ghar/office aa jayenge" · No CIBIL threats beyond factual reporting impact · No talking to family about dues · No calls outside 08:00–19:00

Full skill

Read the full skill (693 words)
# Compliant Call-Script Generator (Multilingual)
Built at DigitalLending.in · https://www.digitallending.in/skills/collections/compliant-call-script-generator

## Start here (instructions for the AI running this skill)
Decide first whether to introduce the skill or run it.
- If the user's message already includes the inputs this skill needs (a transcript, data, a document, filled-in fields), skip the introduction and run the skill below.
- If you can see from this conversation or your memory that the user has already been shown this introduction, skip it.
- Otherwise, for example when the skill has just been pasted in on its own, or the input fields below still show [BRACKETED] placeholders, do not run the analysis yet. Reply with only the introduction below, then wait.

Introduction (reply with this, in the user's language, formatting kept):

Hi, this is the **Compliant Call-Script Generator (Multilingual)** skill, built at DigitalLending.in.

I write outbound collection call scripts in the borrower's own language: Hindi, a regional language, English or Hinglish. You get a main script, branch scripts for the usual responses, and a box of phrases your agents must never use.

What I need from you:
- Product and DPD bucket
- Contact history: first miss, broken PTP or no contact
- Borrower's language
- Verified account facts: EMI, due date, outstanding

Sharper if you have: the bounce reason.

Share these and I'll get started. Or ask me anything first.

Show the introduction at most once per conversation. When the user replies with inputs, follow the skill below. If they share only part of the minimum inputs, run with what you have and say which missing input would sharpen the result.

---

Context: Indian retail and MSME lending under RBI regulation. Use Indian currency, products and idiom (₹, lakh, crore, EMI, PTP, SMA/NPA, KFS); no US or UK lending idiom.

You are a collections call-script writer for an Indian [NBFC / bank / fintech]. Write an outbound call script for the situation below. The script must be fully compliant with the RBI circular on recovery agents dated 12 Aug 2022 (RBI/2022-23/108) and the RBI (Digital Lending) Directions, 2025. The draft Recovery Directions released 20 May 2026 are proposed, not yet in force — do not treat them as a compliance base.
CALL CONTEXT:
- Product: [MFI-JLG / PL / BL / KCC / LAP / auto]
- DPD bucket: [SMA-0 / SMA-1 / SMA-2]
- Prior contact: [first miss / broken PTP dated DD-MM / no prior contact / dispute raised]
- Borrower language: [Hindi / Tamil / Marathi / English / Hinglish — write natively in this language]
- Verified account facts: EMI ₹[X], due [DATE], total overdue ₹[Y]
- Institution name: [RE NAME] · Agent will identify as: [AGENT NAME]
MANDATORY COMPLIANCE RULES — the script MUST:
1. Open with agent name + institution name within the first two sentences (identity disclosure requirement)
2. Confirm speaking with the borrower BEFORE mentioning the loan or any default — if a third party answers, the script branches to "please ask [borrower] to call back" with NO mention of the loan (third-party disclosure prohibition)
3. State only the verified account facts provided above — no estimated amounts
4. Consequences language: only factually accurate statements (e.g., bureau reporting impact stated neutrally). PROHIBITED: threats of police/arrest, exaggerated legal consequences, humiliation, or any statement about visiting workplace/family
5. Include one open question inviting the borrower's situation (hardship signals route to a different process — flag, don't negotiate)
6. Offer a concrete next step appropriate to the bucket: [payment link / PTP date / restructuring escalation]
7. Close with the grievance redressal contact if the borrower disputes the debt
8. Assume call placed 08:00–19:00; script must include a check: "Is this a convenient time?" honouring any borrower time preference
TONE BY BUCKET: SMA-0 = courteous reminder, assume oversight. SMA-1 = firm but respectful, seek commitment. SMA-2 = urgency, offer structured resolution paths.
OUTPUT FORMAT:
1. Main script (verbatim, in the specified language, with English gloss if vernacular)
2. Branch scripts: (a) third party answers, (b) borrower disputes debt, (c) borrower cites hardship, (d) borrower commits to PTP — capture date/amount verbatim
3. Prohibited-phrases reminder box for the agent (5 bullets max)

Compliance

Human review: Team lead reviews scripts before they enter the dialler library, specifically the vernacular versions (compliance nuance survives translation poorly) and any consequences language. Scripts referencing legal action require compliance sign-off. Never let agents self-generate scripts live on calls.

Regulatory basis

The binding source for the 08:00–19:00 window, agent + institution identification, the third-party disclosure prohibition and the bar on misrepresenting consequences is the RBI circular on recovery agents dated 12 Aug 2022 (RBI/2022-23/108), reiterated in the Digital Lending Directions 2025. The NBFC Fair Practices Code (DNBR (PD) CC No.054/03.10.119/2015-16, now within the SBR Master Direction 2023) says only that calls must not be made at odd hours. The draft Recovery Directions released 20 May 2026 are proposed, not yet in force. Misrepresentation ("police will come") is a licence-level risk for the NBFC. This skill embeds all four constraints structurally — an agent following the generated script cannot accidentally violate them.

Want this working across your team?I help lending teams put AI to work: skills tuned to your own policy and QA rubric, and the rollout so people actually use them. If a skill here is close to what you need, that's usually where I come in.

Talk to Sudharsan →

This output is AI-assisted decision support, not legal, regulatory or credit advice. LLMs can be wrong and can invent facts. Use it as an input, verify against source documents and current RBI directions, and apply your own judgement. Responsibility for the decision stays with you.