LogoLogo
Get Demo
  • 💫NEXT-GENERATION PRODUCT
    • Introduction
    • Getting Started
      • 1. Invite System Users
      • 2. Add Target Users
        • Add Users via CSV
        • Add users via SCIM
          • SCIM Setup in Azure AD
          • SCIM Setup in Okta
          • SCIM Setup in Onelogin
          • SCIM Setup in Jumpcloud
        • Add users via LDAP
        • Add Users via API
      • 3. Email Deliverability
        • Microsoft 365
          • M365: Direct Email Creation
          • M365: Whitelisting
        • Google Workspace
          • Google: Direct Email Creation
          • Google: Whitelisting
        • Exchange 2013 and 2016
      • 4. Track Opened Emails
      • 5. Allow Phishing URLs
        • Whitelist for Office 365
        • Whitelist for Google Workspace
        • Whitelist for Exchange 2013/2016
        • Whitelist in Security Solutions
      • 6. Setup Phishing Reporter
        • Step 1. Download Phishing Reporter
        • Step 2. Deploy Phishing Reporter
          • How to Deploy Add-In in Microsoft 365
          • How to Deploy Add-In in Exchange Admin Center
          • How to Deploy Add-In in Google Workspace
          • How to Deploy Add-In in Outlook
            • Troubleshooting Phishing Reporter Add-In on Outlook Desktop
      • 7. Incident Responder Setup
        • Step 1. Integrate Threat Intel Partners
        • Step 2. Mail Configurations
          • Microsoft 365
          • Google Workspace (Gsuite)
          • Exchange (EWS)
    • Platform
      • Dashboard
        • Dashboard Widgets
        • Incident Responder Widgets
        • Threat Sharing Widgets
        • Phishing Simulator Widgets
      • Threat Intelligence
      • Email Threat Simulator
        • Start Scan
        • View Scan Report
        • Create Trusted Account on Exchange
        • Start Scan on O365 Email Account
        • Start Scan on Google Workspace Email Account
      • Threat Sharing
        • Communities
        • Incidents
      • Phishing Simulator
        • Manage Phishing Scenarios
          • Phishing Scenarios
          • Email Templates
          • Landing Pages
        • Phishing Campaign Manager
        • Phishing Campaign Reports
        • Settings
          • DNS Services and Domains
          • Exclude IP Address
      • Callback Simulator
        • Manage Callback Scenarios
          • Callback Scenarios
          • Callback Email Templates
          • Callback Templates
        • Callback Campaign Manager
        • Callback Campaign Reports
        • Settings
          • Callback Phone Numbers
      • Vishing Simulator
        • Vishing Templates
        • Vishing Campaign Manager
        • Vishing Campaign Reports
      • Smishing Simulator
        • Manage Smishing Scenarios
          • Smishing Scenarios
          • Text Message Templates
          • Landing Page Templates
        • Smishing Campaign Manager
        • Smishing Campaign Reports
        • Settings
          • Manage DNS and Domains
          • Exclude IP Addresses
      • Quishing Simulator
        • Manage Quishing Scenarios
          • Quishing Scenarios
          • Quishing Templates
          • Quishing Landing Page Templates
        • Quishing Campaign Manager
        • Quishing Campaign Reports
        • Settings
          • DNS and Domains
          • Excluding IP Address
      • Awareness Educator
        • Training Library
        • Enrollments
        • Certificates
        • Training Reports
        • Training Completion Queries
      • Incident Responder
        • Incident Responder Dashboard
        • Investigations
        • Integrations
        • Playbook
        • Mail Configurations
          • Microsoft 365
          • Exchange
          • Google Workspace
        • Cross Company Integration
      • Phishing Reporter
        • Phishing Reporter Customization
        • Phishing Reporter Deployment
          • How to Deploy the Add-in in Microsoft 365
          • Phishing Reporter Page View Failure Due to Deprecated Exchange Online Tokens
          • Microsoft Ribbon Phishing Reporter
          • Microsoft Page View Phishing Reporter
          • How to Deploy the Add-in in Exchange Admin Center
          • How to Deploy the Add-in in Google Workspace
          • Phishing Reporter Announcement Email Template
        • Diagnostic Tool
        • Integrating Microsoft Phishing Reporting Button with Keepnet
        • Integrating Microsoft Defender with Keepnet Phishing Reporter
        • Troubleshooting Phishing Reporter on Outlook Desktop
      • Reports
        • Advanced Reports
        • Executive Reports
        • Scheduled Reports
        • Gamification Report
      • Company
        • Target Users
        • Companies
          • Company Groups
        • Company Settings
          • Privacy
            • Account Privacy
            • Data Privacy
          • AI Ally Settings
          • SMTP Settings
          • Direct Email Creation
            • Direct Email Creation for Google Workspace
            • Direct Email Creation for Microsoft 365
          • Notification Templates
          • Google User Provisioning
          • REST API
          • White Labeling
          • Proxy Settings
          • SAML Settings
            • How to Configure SAML on ADFS
            • How to Configure SAML on Google Workspace
            • How to Configure SAML on Azure AD
            • How to Configure SAML on CyberArk
            • How to Configure SAML on Okta
          • SCIM Settings
            • Getting Started with SCIM
            • Azure AD SCIM Integration
            • Okta SCIM Integration
            • Onelogin SCIM Integration
            • Jumpcloud SCIM Integration
          • SIEM Integrations
            • Splunk Integration
            • Syslog Integration
          • LDAP
          • Allowed Domains
        • System Users
          • People
          • Roles
        • Audit Log
        • Job Log
      • Free Phishing Email Analysis Service
    • Miscellaneous
      • Whitelisting
        • How to Whitelist an IP Address in Office 365
        • How to Whitelist an IP Address in Exchange 2013 and 2016
        • How to Whitelist an IP Address in Google Workspace
        • How to Whitelist in Mimecast
        • Whitelisting in Other Security Solutions
        • Whitelisting the Pictures on Microsoft Outlook Apps
        • Keepnet Tools Whitelisting Guidelines
        • Understanding Email Delivery Errors
        • Tracking Email Opens in Phishing Simulations
      • User Profile
      • Multi-Factor Authentication (MFA) Settings
      • On-Premise Requirement Checker
      • Platform Requirements
        • Portal UI Requirements
        • Phishing Reporter Requirements
        • Diagnostic Tool Requirements
      • Maintenance Tool
      • Understanding the Preferred Language Setting
  • 📚RESOURCES
    • Platform Security
    • Volume & Performance
    • Customer Help Desk
    • Product Update/Maintenance
    • Research Methodology
    • Release Notes
      • 2025
      • 2024
      • 2023
      • 2022
      • 2021
      • 2020
  • ⚖️Legal Hub
    • For Customers
      • Customer Terms of Service
      • Product Specific Terms
      • Jurisdiction Specific Terms
      • Data Processing Agreement
      • Regional Data Hosting Policy
      • Product and Services Catalog
      • Acceptable Use Policy
      • Keepnet Security Program
      • Microsoft CoPilot Usage Policy
    • For Everyone
      • Website
        • Terms of Use
        • Privacy Policy
        • Cookie Policy
      • Free Phishing Email Analysis
        • Terms of Service
        • Privacy Policy
      • Transparency Report
Powered by GitBook

Copyright © Keepnet Labs LTD. All rights reserved.

On this page
  • Shortcuts
  • FAQ
  • Q: How Is the Difficulty Level Determined?
  • Q: How can clients request a new phone number or area code?
  • Q: What data collection items are allowed for smishing?
  • Q: Are QR codes supported within smishing?
  • Q: Are email addresses required for smishing?
  • Q: If smishes are reported as junk by target users from other companies, will it affect the delivery of my campaigns?
  • Q: What happens if target users delete or report smishes as junk on their mobile devices? How does this impact future campaigns from the same number?
  • Q: Why are my SMS messages not being delivered to users?
  • Q: Why might a customer get the error message 'There must be at least one target user in the selected groups' ?
  • Q: How undelivered smish attempts due to Telco blocking are identified and resent

Was this helpful?

Export as PDF
  1. NEXT-GENERATION PRODUCT
  2. Platform

Smishing Simulator

PreviousVishing Campaign ReportsNextManage Smishing Scenarios

Last updated 2 months ago

Was this helpful?

The Smishing Simulator allows you to create realistic simulated smishing SMS messages sent to employees to assess their ability to recognize suspicious SMS messages and their response to attacks that could compromise organizational data and systems. The product provides the capability to customize and target a smishing campaign suited to your organization and to evaluate the results.

Shortcuts

FAQ

Q: How Is the Difficulty Level Determined?

A: The difficulty level of text message templates and landing pages is determined based on several factors, including but not limited to:

  • Sophistication of Phishing Techniques: The use of advanced spoofing methods, such as display name spoofing, domain similarity, and the inclusion of personalized information, can make a phishing attempt more difficult to recognize.

  • Quality of the Content: The presence of grammatical errors, unusual requests, or other indicators typically associated with phishing can vary. Templates with fewer errors and more realistic scenarios are considered more difficult.

  • Design and Presentation: For landing pages, the visual design and how closely it mimics legitimate websites play a crucial role. High-quality designs that closely resemble real sites increase the difficulty level.

  • Context and Relevance: Attempts that leverage current events, believable scenarios, or target specific job roles can be harder to identify as phishing, especially if they align closely with the recipient's expectations or experiences.

Criteria for Difficulty Levels

  • Easy: These attempts may contain obvious signs of phishing, such as poor spelling and grammar, generic greetings, or implausible requests. They are typically easier for users to identify with basic awareness training.

  • Medium: These attempts are smarter, with less clear mistakes and stories that seem more real. They may use email addresses and websites that look authentic, but there are still some errors you can spot if you look closely.

  • Hard: These are highly sophisticated attempts that closely mimic legitimate emails and websites, often using personalized information and current events to create convincing scenarios. Recognizing these requires advanced awareness of identity sms phishing tactics.

Q: How can clients request a new phone number or area code?

A: Clients can request a new phone number or area code by contacting support@keepnetlabs.com. Our Customer Success team will coordinate with the support team to deploy the requested phone number onto the Smishing Simulator.

Q: What data collection items are allowed for smishing?

A: We do not collect sensitive data such as passwords or similar information. Additionally, we do not capture responses from target users via SMS.

Q: Are QR codes supported within smishing?

Q: Are email addresses required for smishing?

A: Email addresses are not directly required for smishing itself; however, they are needed to create target user profiles in the system.

Q: If smishes are reported as junk by target users from other companies, will it affect the delivery of my campaigns?

A: Yes, if the sending phone number has been previously used and blocked by cellular providers due to reports from target users at other companies, it may affect your campaign's deliverability. To prevent this, create a test group with numbers from various providers (e.g., AT&T, Verizon, Vodafone) to check if the number is blocked. Change the number as necessary.

Q: What happens if target users delete or report smishes as junk on their mobile devices? How does this impact future campaigns from the same number?

A: If target users report smishes as junk or delete them, it can affect the deliverability of future campaigns from the same number. It's advisable to change the sending phone number.

Q: Why are my SMS messages not being delivered to users?

A: Many telecommunication providers restrict message delivery to prevent spam and network overload through rate limiting, content filtering, and bulk messaging controls. To prevent your messages from being blocked, you need to understand and follow these guidelines:

  • Rate Limiting: Telecommunication providers limit the number of SMS messages sent from a single number within a specific timeframe. Spread out your message dispatches to avoid being blocked, e.g., send 50 messages over 20 minutes instead of 20 seconds.

  • Content Filtering: Telecommunication providers scan for repetitive content and specific keywords. Avoid sending identical messages to multiple recipients quickly and steer clear of spammy keywords like "Save big money," "Make money," "Free trial," "Free gift," "Guaranteed," "Risk-free," "Limited time," and "Act now."

  • Simulation Domain: The phishing simulation domain used in the SMS message could be blocked or marked as spam by telecommunication providers. Therefore, it is advisable to change the domain to another available domain on the platform and send the SMS message again to see if it delivers successfully.

  • Landing Page: The HTML landing page used in the SMS message could also trigger filtering and cause the message to be marked as spam. Ensure that the landing page does not include logos or branding from well-known companies like Microsoft or Apple, as this can lead to your message being flagged.

For further assistance on SMS delivery, please contact the support team.

Q: Why might a customer get the error message 'There must be at least one target user in the selected groups' ?

A: There a couple of reason you may receive this message

  • There are no users in the target group selected

  • The domain of selected users has not been verified

  • The target users do not have mobile phone numbers

To resolve, ensure the target group you are selecting contains at least one user with a verified domain. In the case of Smishing and Vishing, the user must also have a phone number associated with them.

Q: How undelivered smish attempts due to Telco blocking are identified and resent

Keepnet ensures successful SMS message delivery by actively tracking and managing undelivered messages, particularly those blocked by telecommunications providers. Here's how undelivered smishing simulation (smish) attempts are identified and resent:

1. Tracking Message Delivery Status

Keepnet monitors SMS delivery statuses in real time. Each message sent is assigned a status, such as:

  • Delivered – Successfully received by the recipient.

  • Failed – Unable to reach the recipient.

  • Rejected – Blocked by the recipient's carrier before delivery.

  • Undelivered – Encountered an issue preventing completion.

2. Identifying Carrier Blocking

When a message is blocked, an error code is logged, helping Keepnet pinpoint the reason for failure. Common indicators of carrier filtering include:

  • Content-related blocking – Carriers may filter messages based on words, URLs, or patterns flagged as spam or phishing.

  • Destination restrictions – Some numbers may be blocked from receiving messages due to carrier policies.

  • Rate-limiting or bulk message filtering – Some carriers limit or delay messages that appear to be part of bulk campaigns.

3. Analyzing and Adjusting Message Content

If a smish attempt is blocked, Keepnet analyzes the message structure and content. To improve deliverability:

  • Suspicious words and phrases that might trigger filtering are adjusted.

  • URLs are modified or shortened appropriately.

  • Messages are personalized to reduce the likelihood of being flagged as spam.

4. Resending Messages

Once adjustments are made, Keepnet resends the message, ensuring compliance with carrier guidelines while maintaining the integrity of the security simulation.

5. Preventing Future Blocking

To reduce future delivery issues, Keepnet follows best practices, such as:

  • Using reputable sender numbers.

  • Complying with carrier regulations.

  • Implementing adaptive message templates that reduce filtering risks.

By proactively monitoring message logs, analyzing failures, and refining content, Keepnet ensures smishing simulations reach intended recipients effectively, enhancing security awareness training and real-world preparedness.

A: QR codes are not supported in our SMS phishing simulator. For QR code simulations, Keepnet Labs offers a separate product called .

💫
How to create smishing scenarios
How to launch a smishing campaign
How to view campaign reports
QR Code Simulator (Quishing)