Raqeeb

Raqeeb · compliance engine

The message that breaks the rule never gets sent.

Raqeeb checks every outbound collections message against SAMA's rules at the moment of send — and refuses the ones that would breach them. Compliance as a gate, not a report.

Every compliance tool on the market tells you a violation happened. Raqeeb stops it happening.

Monitoring

Raqeeb

  • Findings arrive days after the call

    The decision is made before the send

  • A sample of interactions is reviewed

    Every message is checked — no exception

  • The agent is coached not to repeat it

    The send is refused, so there is no repeat

How it works

Three checkpoints, one decision log.

Before send

Gate

A synchronous check in the send path: allow, hold or refuse — with the reason. No answer means no send.

  • Attempt count on a rolling 30-day window, per financing product
  • Time of day, recipient identity, required disclosures
  • Message content matched to its approved template
On inbound

Detection

Reads what the customer said — in Arabic, including dialect — and routes it to the obligation it triggers.

  • Hardship → affordability path, dispute → dispute path
  • A request for a human, honoured immediately
  • Wrong person answered → the interaction ends
After the fact

Trail

A queryable record, not a log file. Any decision reconstructed in seconds, without an engineer.

  • Every decision carries the rule version and the clause
  • Refusals recorded as fully as sends
  • Ten-year retention, append-only, four-eyes on changes
The gate, working

Three sends allowed. The eleventh attempt stopped at the cap.

What it enforces

SAMA's collection rules, in code.

Drawn from the Debt Collection Regulations and Procedures — which bind creditors and, explicitly, third parties acting for them. Every rule carries its clause.

  • Ten calls per thirty days, per financing product — on a rolling window

    Art. 4(3)

  • Contact during official working hours only, in the customer's local time

    Art. 4(3)

  • The customer or the guarantor — nobody else, identity verified first

    Art. 4(2)

  • Recording disclosed at the start of the call, as a required element

    Art. 4(4)

  • No visits to a home or workplace — the capability is absent, not restricted

    Art. 4(5)–(8)

  • Collection paused automatically while a complaint is open

    Regs + Principle 7

  • Every communication documented and retained for at least ten years

    Art. 4(4)

  • Rules are versioned and dry-runnable — replay last month before going live

    Built in

Getting it in

It sits in front of what you already run.

One API call in the send path

Returns a decision. The failure mode is refusal — never a silent allow.

No rip and replace

Sits alongside your dialler, CRM and messaging gateway.

Built for in-house teams

You don't outsource collection to us to use it.

Data stays in the Kingdom

Your rules, your decisions, nothing pooled across clients.

See what it would have refused last month.

A shadow run on your own traffic — you keep the output either way.