Phishing simulation for companies

Native email phishing and QRishing, tailored to each risk profile. Each fail triggers training. Smishing and vishing run as a professional service.

Simulations
How it works

How a phishing simulation works

Analyzes

The Agent evaluates each user's history and behavior to determine their level of exposure.

Simulates

Launches the right campaign for that profile: channel, scenario, and difficulty adjusted individually.

Intervenes

If the user falls for it, activates immediate training contextualized to the specific error made.

Simulations

The mistake becomes a lesson, right there

Anyone who falls for a simulation doesn't get a scolding: they get a 3-minute micro-lesson that explains the trick while they still remember it.

Inboxsimulation
HRPayslip — March
IT SupportYour password expires today: verify hereSimulated phishing
LeadershipNotes from the quarterly meeting
Micro-lesson: the domain read “it-support.co” and pushed urgency. Two signals, one click avoided. 3 min to see them all.
Interactive

Can you find the 5 signals?

This is a real email used in our simulations. Hover the marked areas and learn to read phishing the way an analyst does.

From:Human Resources
Subject:

Dear team member,

We found an inconsistency in your August payslip. To avoid delays in the transfer, .

Access the portal from this link:

Regards,

Five signals a phishing email usually carries together

The exercise is recognising the pattern. We do not publish a campaign rate.

What is native and what runs as a service

Email
phishing

Native email campaigns, adjusted to each user's risk profile, with difficulty based on history.

QRishing

Native QR-code simulations. The QR jumps to the phone; the mail filter does not see it as a link.

Three
modalities

Click-only, credential capture and ransomware by attachment. Three depths of the same email channel, not three products.

Professional
services

Smishing, vishing, USB drop, 2FA attacks and deepfake are not builder buttons. They run as a service, with scope and a report.

Email
phishing

Native email campaigns, adjusted to each user's risk profile, with difficulty based on history.

QRishing

Native QR-code simulations. The QR jumps to the phone; the mail filter does not see it as a link.

Three
modalities

Click-only, credential capture and ransomware by attachment. Three depths of the same email channel, not three products.

Professional
services

Smishing, vishing, USB drop, 2FA attacks and deepfake are not builder buttons. They run as a service, with scope and a report.

Email
phishing

Native email campaigns, adjusted to each user's risk profile, with difficulty based on history.

QRishing

Native QR-code simulations. The QR jumps to the phone; the mail filter does not see it as a link.

Three
modalities

Click-only, credential capture and ransomware by attachment. Three depths of the same email channel, not three products.

Professional
services

Smishing, vishing, USB drop, 2FA attacks and deepfake are not builder buttons. They run as a service, with scope and a report.

METRICS

Actionable visibility, not just click rate

Every campaign generates behavioral data to understand real exposure, prioritize interventions, and demonstrate evolution.

  • Click rate by user, team and organization
  • Report rate: who detected and reported the threat before falling
  • Evolution: how the risk profile improves over time
Impacto de campaña de simulación
REAL CASES

Simulations for the real world

Executive fraud, credential theft, fake vendors, compromised access. Whalemate replicates the most frequent attack vectors with templates by industry, role, and operational context — designed to replicate what your teams face day to day.

Nueva simulación
In this module

Program capabilities

Modalities

Click-only, credentials and ransomware

Three modes of the same campaign: measure the click, the hand-over of data, or the ransomware gesture. The library classifies them. Not three separate products.

Landing

Post-fail landing

The screen whoever falls sees. It measures the gesture — open, hand over, execute — without being a customer microsite or a form that asks for a real secret.

Calendar

Launch calendar

When each campaign goes out. The annual plan lives with the analyst; here you see the cadence so the roster is not flooded and months are not left silent.

Reinforcement

Automatic enrollment after a fail

Whoever falls enters the course for that error. The simulation fires; training assigns. Reinforcement does not wait for the quarterly pack.

Advanced simulations

Phishing simulation for companies: email, QRishing and three modes

Campaigns adapt to the profile, not to a monthly blast. We do not publish click rates or industry averages. We publish the criterion: channel, difficulty, and what happens after the error.

A phishing simulation that works measures behavior; it does not produce a ranking for a photo. The payroll email and the store QR exist because the real attack uses those native channels. The Agent picks difficulty and frequency from history. Treasury and the sales floor do not get the same lure on the same Tuesday. If the person falls for it, the cycle continues in contextual training. If they do not, the bar can rise. The security team sets rules. It stops slicing lists.

Adaptive phishing covers email. QRishing covers the scan gesture — not a PDF about codes. Three modes on the same email channel: click-only, credential capture and ransomware by attachment. Smishing, vishing, USB drop, 2FA attacks and deepfake run as professional services, not as builder buttons. Here we do not sell a pack with an improvement percentage. We declare what is native and what is measured: exposure and habit, not a loose rate.

What we do not do matters as much as the catalog. We do not publish customer click rates or a “LATAM average.” We do not use the result for a file. We do not install an endpoint agent to “see the click.” The simulation is a controlled exercise. The report says what happened in that campaign. The index accumulates the signal. Leadership sees evolution, not a hall of shame. If someone quotes you a program with a click rate printed on the cover, ask where the number came from.

Questions about phishing simulation

Which channels does a native phishing simulation cover?
Email and QRishing, natively, with adaptive difficulty and three modes: click-only, credentials and ransomware. Smishing, vishing, USB drop, 2FA and deepfake are not builder buttons: they run as professional services. Your contract detail is confirmed in the proposal. We do not invent a native channel to close a checklist.
What is the typical click rate?
We do not publish one. It depends on the roster, the scenario, and whether the campaign is calibrated or a blast. A loose rate does not prove maturity and is misused in the board pack. The demo shows how to read a campaign. Analytics shows how it enters the index. If you need a number for a slide, use the one from your own run when it exists — not an invented average of ours.
What happens when someone falls for it?
The event is recorded and immediate reinforcement can fire, contextualized to the error. The score updates. A reprimand email is not sent. The design assumes learning, not public exposure. People and security agree the communication tone. The module does not publish a ranking on the internal channel.
Do templates look like our flows?
There are templates built for real flows — payroll, vendors, help desk, floor QR — and they can be customized. How far customization goes depends on the plan and on professional services. The level of detail is defined in implementation. Scenarios are chosen in implementation. The demo shows examples, not your letterhead.
Do smishing, vishing, or deepfake come in every plan?
Not as a native channel. Email and QRishing are native to the module. SMS, voice and advanced scenarios run as professional services. Plans and services say so without a price. We do not list a channel here so the contract can deny it later.

Measure your response to real threats

Book a demo and see how Whalemate designs simulations adapted to each user's risk profile.