> For the complete documentation index, see [llms.txt](https://doc.keepnetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.keepnetlabs.com/next-generation-product/customer-success/most-loved-scenarios/smishing.md). # Smishing SMS Phishing With over 6,500 smishing scenarios, our customers have a huge range of choice when planning their annual social engineering strategy. Our customer success team has cherry-picked our customers' most favourite scenarios across a number of different industries and tech stacks to help you streamline your efforts. **Top Tip: Simply copy and paste these Scenario Titles into Keepnet to find our favourites!** New Device Policy Company Survey Update MFA MS Dropbox Verification Notice LinkedIn Profile Notification LinkedIn Unusual sign-in detected Apple Apple ID login Suspicious Login Detected Amazon Delivery Failed Google Account Security Suspicious Activity on Your Google Account Slack Security Alert MS Teams Invite ### Example: New Device Policy
Smishing scenario example — New Device Policy.

Smishing scenario example — New Device Policy.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doc.keepnetlabs.com/next-generation-product/customer-success/most-loved-scenarios/smishing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.