OpenAI Software / SaaS North America

Doppel

Fraud Detection · Risk Management · Security and Compliance

Doppel needed to detect, classify, and stop phishing, impersonation, and other social-engineering threats at internet speed, long before human analysts could keep up with the volume and variation created by generative attacks.

3x threat handling capacity
80% reduced analyst workflows
Most threats classified automatically
Threat response times reduced from hours to minutes

Reported impact

Business outcome

Doppel automated most threat classification, reduced analyst workload, tripled handling capacity, and cut response times from hours to minutes while improving the transparency customers get around each takedown decision.

  • Productivity Improvement
  • Risk Reduction
  • Scalability

Solution

Doppel rebuilt its defense stack around OpenAI models so threat analysis could move from manual review into autonomous, explainable decisions. The pipeline starts with heuristic filtering and o4-mini-based feature extraction over millions of domains, URLs, and accounts. Each suspicious signal is then evaluated by multiple GPT-5 prompts tailored to different threat questions, such as impersonation risk, brand misuse, or social-engineering patterns. An o4-mini model improved through reinforcement fine-tuning synthesizes those confirmations into a structured classification, after which a second GPT-5 pass validates the decision, generates justification, and can automatically trigger enforcement when confidence is high. Low-confidence cases are routed to analysts, and those decisions flow back into the RFT loop so future judgments become more consistent. This architecture gives customers faster action and clearer explanations for digital surfaces where threats can do damage within minutes.

Data flow

Domains, URLs, accounts, and other threat signals enter Doppel's pipeline, where heuristics and o4-mini reduce noise and extract features. GPT-5 and RFT-enhanced classifiers then assess malicious intent, produce labels and justifications, and either auto-enforce or escalate uncertain cases to analysts.

Solution architecture

4 components · 3 layers
  1. Compute
    • GPT-5 Handles targeted threat reasoning, final verification, and customer-facing justifications.
    • o4-mini Filters signals, extracts features, and supports the RFT-based classification stage.
  2. Orchestration
    • LLM-driven pipeline Coordinates filtering, parallel confirmations, classification, verification, and enforcement.
  3. Governance
    • reinforcement fine-tuning Turns analyst judgments into structured training signals for consistent threat classification.

Architecture clues

  • Automated takedowns include AI-generated justifications for customers
  • Multiple GPT-5 prompts run in parallel for different threat analyses
  • RFT is trained on analyst decisions and graded for explanation quality
  • Threat pipeline uses heuristic filtering plus o4-mini feature extraction

Evidence from the source

"Doppel’s platform detects, classifies, and takes down threats autonomously"
"cutting analyst workloads by 80%"
"reduces response times from hours to minutes"
"triples threat-handling capacity"
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. OpenAI

    Doppel customer story

    First-party
    https://openai.com/index/doppel/
    Source type
    Vendor-published customer story
    Published
    Oct 28, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Oct 28, 2025 · OpenAI · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.