How We Build a Scam Lesson From a Real Phone Call

It starts with a message someone forwards

Most lessons in the scam module begin with something a learner sends us: a screenshot of a text, a voicemail transcript, or a few lines scribbled after a call that felt wrong. Learners often apologize for sending it, as if they should have known better. I tell them the opposite is true. A message that made you pause is exactly the material that teaches the most.

When one arrives, I read it the way a stranger would, with no context. I note what it asks for, what it threatens, and what it wants the reader to feel in the first five seconds. Urgency is nearly always the lever. Only after that do I look at the details such as the sender number, the wording of the link and the greeting.

Stripping out anything that could identify a person

Before a message goes anywhere near a lesson, it is rebuilt. Names, phone numbers, account digits and any reference to a particular branch are removed or replaced with plausible but unconnected details. The structure of the scam stays intact, because that is what we are teaching, while the person who received it stays out of it entirely.

This takes more time than copying a screenshot, and I think it is the right trade. A learner should never open a lesson and recognize a neighbour's message. It also forces me to decide what the essential pattern is. If the lesson still works after the specifics are gone, it is teaching something durable rather than a single trick that will be out of date in a month.

Writing the lesson in the order a person would live it

A scam is experienced in sequence: the message arrives, doubt flickers, a decision gets made. So we write the lesson in that order. First the message as it appeared, then a pause where the learner is asked what they notice, then what the sender hoped they would do next.

I avoid long lists of warning signs, because nobody scans a list while their phone is buzzing. Instead each lesson settles on two or three questions a person can carry in their head: Did I expect this? Is it asking me to hurry? Can I check it another way? Amrit reviews the security wording, and Marc reads for tone, since a lesson that makes people feel foolish teaches them to hide mistakes.

• Did I expect this contact?
• Is it pushing me to act quickly?
• Can I confirm it through a number I already trust?

Testing it on people who are not in the room

A draft is only finished when someone outside the team has read it cold. We ask a few learners from earlier groups to go through it and tell us where they hesitated. Their pauses matter more than their praise. If three people stumble on the same sentence, the sentence is wrong, not the readers.

Sometimes the feedback changes the lesson's direction. One draft assumed everyone knew what a verification code was for, and several readers did not. We added a short explanation before the example, and the whole lesson became easier to follow. Those small repairs rarely show, but they are most of the work behind a page that simply feels clear.

Deciding what to say about what to do next

The hardest paragraph to write is the one about action. People want a single instruction, but the right step depends on what happened. Ignoring a message is different from having clicked a link, and both are different from having shared a code. We describe each situation separately and keep the steps calm and ordered.

The common thread is to stop, contact your own bank using the number printed on your card or shown in your banking app, and write down what occurred while it is fresh. We do not promise outcomes, and we do not pretend a lesson can replace speaking with your financial institution. We simply make sure the first few minutes after a mistake are not spent in panic.

Keeping the material current through the season

Scam messages change with the calendar. In these weeks of mid autumn, learners report more messages about parcels, utility accounts and tax-style notices, so we adjust which examples sit near the front of the module. The core questions stay the same; the costumes change.

I review the examples regularly and retire any that no longer look like what people actually receive. An out-of-date example is worse than none, because it teaches people to look for the wrong thing. The goal is not to catalogue every trick but to keep learners practised at noticing the feeling of being rushed, which is the one signal that rarely changes.

Behind each scam lesson there is a forwarded message, a careful rebuild, a cold read by outsiders and a plain account of what to do afterwards. None of it is dramatic, and that is deliberate. We would rather you finish a lesson steady and slightly more suspicious of urgency than frightened. If something has landed in your inbox that gave you pause, that pause is a skill worth trusting.