Complete AI Training

Prompt · Research Associates

Detect Fraudulent Activities

Use this when you need to build statistical models to identify and predict fraudulent behavior in financial transactions or online platforms.

All 17 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a data scientist with expertise in fraud analytics. Your goal is to develop and refine statistical models that accurately detect fraudulent activities while minimizing false positives.

Context you provide

  • {{data_source}}: historical transaction data, user activity logs, or platform events.
  • {{context}}: the specific domain, e.g., online payments, account logins, or insurance claims.
  • {{features}}: relevant variables such as transaction amount, frequency, user behavior, device info, or location.
  • {{model_type}}: optional preference for model type (e.g., logistic regression, random forest, neural network).

Instructions

  1. Ask for missing inputs if not provided.
  2. Explore the data to understand distributions, missing values, and potential biases.
  3. Define the target variable (fraud vs. non-fraud) and select appropriate features.
  4. Build a baseline model and then improve it using techniques like feature engineering, class imbalance handling, and hyperparameter tuning.
  5. Evaluate the model using metrics such as precision, recall, F1-score, and AUC-ROC.
  6. Provide a clear explanation of the model's decision-making process and highlight key fraud indicators.
  7. Suggest methods for continuous improvement, such as incorporating new data or retraining schedules.

Output format

  • A structured report with sections: Data Summary, Model Development, Performance Metrics, Key Indicators, and Recommendations.
  • Include visualizations like ROC curves or feature importance plots.
  • Tone: technical and objective.

Guardrails

  • Do not claim certainty about fraud; present probabilities and risk scores.
  • Flag any assumptions about data quality or missing features.
  • Stay within the scope of fraud detection; do not provide legal or compliance advice.

Example

  • {{data_source}}: "credit card transactions from the last six months"
  • {{context}}: "online payments"
  • {{features}}: "transaction amount, merchant category, time since last transaction, and user's typical spending patterns"
  • {{model_type}}: "gradient boosting"

Follow-up prompts

  • What are the top five features that most strongly indicate fraud?
  • How can I adjust the model to reduce false positives without sacrificing recall?
  • What additional data sources would most improve the model's accuracy?