NSK AI
Products
·
Leri

Agents that close the case.

Leri takes a request the whole way: reads it, finds the record, decides, writes the change back into your systems, and leaves the receipt. Eight faces, one loop, no handover unless it earns one.

Reply
Answers, then waits for a human.
Resolve
Acts inside the system of record, then reports what it did.
FACE 01 / 08

Intake

A request arrives on whatever channel your customers already use. It is turned into a case with an owner, a clock and a state.

case.open(source: whatsapp) → #48211

Read

Intent, entities and the thing actually being asked for. Ambiguity is recorded as ambiguity, not guessed away.

intent: refund · conf 0.94 · missing: order_id

Retrieve

The record is pulled from your systems, not from the model's memory. Every field it reads is cited in the receipt.

crm.get(order) · ledger.get(txn) · 2 sources

Decide

Your policy, expressed as rules the agent cannot argue with. The decision names the clause it came from.

policy R-14 → refund allowed ≤ 30d

Act

The write happens here. Scoped credentials, one transaction, reversible, and nothing outside the scope it was granted.

POST /refunds · idempotency-key set

Verify

The agent re-reads the record it just changed. If the world does not match the intent, the case does not close.

assert(balance −= 14200) · pass

Log

One receipt per case: inputs, sources, clause, action, result. Readable by an auditor with no context.

receipt #48211 · 7 events · signed

Escalate

The eighth face is the honest one. When confidence or authority runs out, a person receives the case already worked.

handover · 0 questions re-asked
close = act ∧ verify ∧ log

One case, end to end, with the receipt attached.

hover a step
01
Intake
case opened
source recorded, clock started
02
Read
intent parsed
entities extracted, gaps named
03
Retrieve
record pulled
two systems, both cited
04
Decide
policy applied
clause R-14, within window
05
Act
write committed
one transaction, idempotent
06
Verify
state re-read
world matches intent
07
Log
receipt written
seven events, signed
08
Escalate
handover ready
only when authority runs out

Where it sits in your stack

Channels
WhatsApp, voice, email, in-app
Systems of record
CRM, core banking, ERP, ticketing
Policy
Your rules, versioned and cited
Oversight
Receipts, replays and limits
Scoped

Every action the agent can take is declared in advance, with limits, and nothing else is reachable.

Authority
Reversible

Anything written can be replayed and undone from the receipt, without reconstructing what happened.

Recovery
Measured

Resolution rate, escalation rate and time to close are reported per queue, not as one headline number.

Evidence

The rest of the system

Own your own AI future.

Put an agent on one queue, with limits you set, and read the receipts.