# Phishing With over 16,000 phishing 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!** ### Microsoft Policy Announcement – Microsoft Teams Microsoft: SETTINGS EXPIRE TODAY New Message on Teams Someone Sent a Document Sharepoint: IT Support shared “To be completed” with you Microsoft Teams: Director added you to a project team! ### Google Google Docs: You were mentioned in a document Google: Suspicious sign-in prevented Google: Shared Spreadsheet ### Common Threats DocuSign: Your Document Has BeenCompleted DocuSign: Signature Request IT: Back Up Your Emails LinkedIn: Deactivation Request Support Desk Alert HR: All Employee Meeting Mimecast: You have new held messages Your Benefit Program Account has invalid information ### Impersonation New Employee Impersonation Action Required: Storage Quota Exceeded CEO Fraud: Supplier Payment Approval CEO Fraud - Payroll confirmation CEO Fraud - Request IT Help, Locked Out ### Senior Leadership Team CFO: Financial Report HR: Annual Employee Growth Report Sharepoint: New shared document Sharepoint: IT Support shared “To be completed OpenAI: Invited to a ChatGPT Team ### **Example:** Sharepoint: IT Support shared “To be completed
Phishing scenario example — Sharepoint IT Support shared document.

Phishing scenario example — Sharepoint IT Support shared document.

--- # Agent Instructions: 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 current page URL with the `ask` query parameter: ``` GET https://doc.keepnetlabs.com/next-generation-product/customer-success/most-loved-scenarios/phishing.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.