AI operations for Saudi insurance carriers
Your claims playbook, run end-to-end, in Arabic, under SAMA's clock.
An agent runs your claims playbook, calls your integrations, and writes an auditable trace. Every decision carries its reasoning, and the adjudication clock sits on every claim.
The deadline
Your adjudication window is shrinking. Intake already spends most of it.
Claim evidence arrives as Arabic PDFs from regulatory portals, email attachments, and paper handed across the counter. An adjuster copies fields across four systems before any decision math runs. The median claim spends six to nine days in ingestion before it reaches review.
Regulators measure these windows per-claim; breach rates reach the board. Every day lost to intake is a day a complaint gets closer to SAMA's desk.
Daqiq reads the same documents in seconds, runs your rule-set inside an agent, writes the decision, and persists the trace. The clock becomes a line on every claim — visible, reported, defensible.
Live product preview
An adjudication, rendered on this page.
A claim decided in 52 seconds at 98% confidence. The full trace deep-links from every decision inside your console.
c8f9a3motor claims
Riyadh sideswipe · two-vehicle · claimant at-fault party
Rationale
Single-vehicle third-party damage claim covered under comprehensive Section 3. Taqdeer estimate of SAR 14,200 within policy limits; no fraud indicators.
Agent trace
- 01classify_documentNajm NAOS liability report + Taqdeer assessment + police reporta03f · 310ms
- 02extract_partiesClaimant, other party, policy holder, 1 witness7b12 · 1240ms
- 03lookup_policyPolicy P-204877 · active · comprehensive motorf4e1 · 180ms
- 04verify_coverageSection 3 — third-party property damage — in scopec019 · 92ms
- 05evaluate_fraud_ruleRule #4 (staged collision pattern) — no hit9a27 · 420ms
- 06compute_quantumTaqdeer estimate matched to workshop schedule → SAR 14,2002e55 · 640ms
- 07emit_decisionApproved · routed to carrier reviewer for sign-offb8ac · 88ms
Evidence reviewed
- Najm NAOS liability reportDriver at fault — other party
- Taqdeer loss assessmentSAR 14,200 · matched to workshop schedule
- Policy P-204877Active · comprehensive motor · Section 3 in scope
- Fraud ruleset v34 rules evaluated · no hit
Capabilities
What it does.
01
Reads Arabic documents natively.
Najm NAOS liability reports, Taqdeer property assessments, NPHIES health payloads, and your own carrier-authored forms parse into a typed schema per document class. Classification runs first. No heuristics, no regex.
Najm report · PDF
Structured
{
ref: "c8f9a3",
parties: [
{ role: "claimant" },
{ role: "other" }
],
incident: {
type: "sideswipe",
city: "Riyadh"
},
at_fault: "other",
coverage: "section_3"
}Decision
APPROVED · 14,200 SAR
confidence 92% · tat 0:52
traced · signed · exportable
02
Runs your claims playbook.
Your adjudication playbook — triage, fraud rules, decision tree — is written in plain bilingual prose. Your admin edits a paragraph; a version-controlled rule compiles. No code deploy.
Playbook editor
§2.3fraud.triage
If the police report cites driver_at_fault AND fault_party !== insured, escalate to the senior adjuster queue.
Otherwise, route to auto-approve.
Otherwise, route to the auto-approve queue with confidence ≥ 0.85.
edited by noor.alghamdi@carrier · 3 min ago
Compiled rule
rule "fraud.triage" {
when:
police_report.driver_at_fault == true
&& fault_party != "insured"
then:
escalate("senior_adjuster")
else:
route("auto_approve", min_confidence: 0.85)
}03
Writes an append-only audit trail.
Every decision emits a trace: tool calls, retrievals, rule evaluations, rationale. Traces chain by SHA-256 hash. The same hash chain backs claim decisions, invoices, and credit notes.
Who this is for
Daqiq is for carriers running motor, health, property, marine, or engineering lines, where claim volume moves faster than the team hired to handle it.
Start a conversation.
Tell us about one business line under pressure, and the current adjudication flow behind it.