# Festive-Season Scam Watch: a free prompt pack

From the Novelty shelf at ReadSigil (https://readsigil.com/novelty.html)
Free. Available until Friday 30 October 2026, 11:59 PM IST.

## What this is

Eight prompts for people in banks, NBFCs and fintechs who write customer
communication or review fraud and complaint queues in the run-up to the
festive season. Paste one into any general-purpose AI assistant, fill in
the [brackets], and edit the output before anyone else sees it.

## Ground rules before you use any of these

1. Never paste real customer data (names, account numbers, phone numbers,
   card numbers, UPI IDs, complaint text with personal details) into a
   public AI tool. Use synthetic or redacted examples.
2. Everything the model writes is a first draft. Your fraud, compliance and
   brand teams own the final wording.
3. Check every factual claim, helpline number and link against your own
   institution's approved sources before publishing.
4. Nothing here is legal, regulatory or security advice.

---

## 1. Plain-language scam alert (SMS length)

You are writing for a retail bank customer who reads on a phone and may
not be a confident English reader. Write three versions of a scam alert
under 160 characters each about [scam pattern, e.g. fake festive-sale
links asking for card details]. Each must say what the scam looks like,
the one thing the customer must never do, and that the bank will never
ask for [OTP / PIN / CVV]. No fear-mongering, no exclamation marks,
no links.

## 2. Same alert, three languages, one meaning

Translate the alert below into [Hindi / Marathi / Tamil / your choice].
Keep it under 160 characters per language. After each translation, give a
back-translation into English so a reviewer can confirm the meaning did
not drift. Flag any word that has no clean equivalent.
Alert: [paste approved English alert]

## 3. Spot the pattern in synthetic complaints

Below are [10] synthetic, made-up customer complaint summaries. Group them
into likely scam patterns (for example: UPI collect-request fraud, fake
delivery or courier messages, fake customer-care numbers, screen-sharing
app requests, fake festive offers, other). For each group give the count,
the common tell-tale phrase, and one question an agent could ask the
customer to confirm the pattern. Say "unclear" rather than guessing.
Complaints: [paste synthetic examples]

## 4. Red-team your own customer message

Here is a customer message we plan to send: [paste draft]. Act as a
fraudster. Explain how you could copy its look, tone or wording to make a
convincing fake. Then suggest three changes that make our genuine message
harder to imitate (for example: never including links, pointing customers
to the official app, using a consistent sender ID).

## 5. Call-centre script for a worried customer

Write a short, calm script for a contact-centre agent speaking to a
customer who thinks they shared an OTP with a scammer [minutes / hours]
ago. Order the steps by urgency. Include where the agent should follow
our internal process [describe it briefly] and where to tell the customer
about the national cyber-crime helpline 1930 and cybercrime.gov.in.
Keep each agent line under 25 words.

## 6. Turn a scam trend into a 60-second explainer

Write a 60-second voice-over script for a branch screen or social video
explaining [scam pattern] to a first-time digital banking user. Structure:
what it looks like, why it works on people, the one habit that stops it.
Use one everyday analogy at most. End with: "Your bank will never ask for
your OTP."

## 7. Internal briefing note for branch staff

Summarise these [synthetic incident notes / internal circular extract]
into a one-page briefing for branch staff: three patterns to watch, what
to say to a customer at the counter, and when to escalate. Use short
bullet points. Mark anything you inferred rather than read as "[check]".

## 8. Fairness check before you send

Review this scam-awareness campaign copy: [paste]. Does any line blame the
victim, talk down to older customers, or assume a level of digital
literacy? Rewrite the weakest three lines. Keep the safety message
unchanged.

---

Built for The Signal, an independent magazine on AI in financial services.
ReadSigil is a personal publication. Views are the author's own and not
those of any employer.