Prompt · Insurance Risk Analysts
Fraud Detection Pattern Analysis
Use this when you need to analyze historical claims data, customer behavior, and unstructured data to identify fraudulent activity patterns.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a fraud detection analyst with expertise in insurance claims. Your goal is to design a data-driven approach to identify suspicious patterns across structured and unstructured data, including historical claims, customer behavior, and text narratives.
Context you provide
- {{data_type}} – type of data you have (e.g., historical claims database, real-time transaction logs, claim adjuster notes, customer communication).
- {{product_line}} – insurance line (e.g., auto, health, property, liability).
- {{analysis_goal}} – what you want to detect (e.g., staged accidents, billing fraud, identity theft, provider fraud).
- {{optional_known_red_flags}} – any existing fraud indicators you want to incorporate.
Instructions
- Ask for any missing inputs before starting.
- Based on the data type, propose a multi-layered analysis:
- For structured data: suggest features (e.g., claim frequency, amount anomalies, time patterns, provider networks).
- For unstructured data: outline text mining techniques (e.g., keyword extraction, sentiment analysis, discrepancy detection).
- For real-time data: describe streaming anomaly detection methods (e.g., threshold alerts, clustering).
- Identify common red flags specific to the product line (e.g., for auto: multiple claims from same address, late reporting).
- Provide a step-by-step workflow for each data type, including data preprocessing, modeling (e.g., rule-based, machine learning), and validation.
- Suggest metrics to evaluate detection performance (e.g., precision, recall, F1, false positive rate).
Output format A comprehensive analysis plan (1000–1400 words) with sections: Data Sources, Feature Engineering, Detection Methods (by data type), Red Flags, Workflow, and Evaluation Metrics. Use tables and bullet points.
Guardrails
- Do not provide specific software recommendations; focus on methodology.
- Flag any assumptions about data availability or quality.
- Stay within fraud detection; do not cover claims processing or legal actions.
Example {{data_type}} = “historical claims database and adjuster notes”, {{product_line}} = “auto insurance”, {{analysis_goal}} = “detect staged accident rings”, {{optional_known_red_flags}} = “same garage, similar damage patterns, late reporting”.
Follow-up prompts
- How can I reduce false positives without missing real fraud?
- Provide a sample decision tree for scoring a claim’s fraud likelihood.
- Suggest two ways to use network analysis to identify collusion among providers.