Phishing campaigns
Send realistic-but-fake phishing emails to your staff so they learn to spot real ones. TSNC ships templates that look exactly like the most common phishing patterns of 2026 โ Microsoft 365 password resets, fake invoices, tax notices.
Why bother with phishing simulations?
Real phishing emails get more sophisticated every year. Lectures don't teach people what the current threats actually look like โ getting fooled by a safe simulated email does. It's the muscle memory equivalent of a fire drill: nobody's burning, but everyone practices the response.
Anatomy of a campaign
Every campaign has four parts:
- Template โ the email content. We have 50+ pre-built templates; you can also build your own.
- Sending domain โ the "from" address. TSNC owns 30+ domains that look like Microsoft, Google, banks, vendors, etc. Your school's real email isn't spoofed.
- Recipients โ who gets it. Whole staff, a department, just one person, etc.
- Schedule โ send now, send later, or send on a recurring cadence (auto-campaigns).
Sending your first campaign
- 1Send to yourself firstAlways pilot a new template on yourself and your IT admin before sending to the whole staff. You see what they'll see, you click through the landing page, and you can spot any context that looks weird for your specific school.
- 2Pick a templateBrowse Templates โ Library. We sort them by realism and difficulty. Start easy (obvious typos and bad grammar) and work up to subtle (perfect-looking Microsoft 365 password reset).
- 3Choose a sending domainThe default works fine โ TSNC picks based on the template. If you want to test a specific scenario (e.g., make sure your team spots an email that looks like it's from your bank), you can pick the matching domain manually.
- 4Review and sendHit Send. The campaign appears in the Campaigns list as "Sent." Results stream in over the next 24-48 hours as people open, click, or report.
Auto-campaigns (set and forget)
Most schools don't want to remember to send a campaign every month. Auto-campaigns send a fresh template at a cadence you set (default: 2/month). You configure them once, and they run year-round.
Reading the results
After a campaign sends, every staff member ends up in one of four buckets:
- Caught โ they reported the email as suspicious. This is the goal.
- Clicked โ they clicked a link in the email. They saw the landing page, learned what they missed.
- Submitted โ they entered credentials on the fake landing page. (TSNC never stores what they typed; we just record that they did.)
- Ignored โ they didn't open or interact with the email at all.
"Caught" is the only one that earns trust-score points. Clicks are not punished โ they're a learning event. Repeat clicks across multiple campaigns are when we suggest you check in with that person directly.