AI for Banking · Retail · Corporate · Risk & compliance
Answer every call. Finish the work.
- Saudi Arabic, day and night
- Your phone system, your numbers
- Authentication before any lookup
- Limits and approval on money
- Inside your own network
04 · DESKS
Contact centre
→ Call answered, 2 a.m.
logged · recording kept
Disputes
→ DSP-20914 raised
logged · recording kept
Fraud
→ Card blocked
logged · recording kept
Onboarding
→ File screened
logged · recording kept
Financial crime
→ Evidence pack ready
logged · recording kept
Relationships
→ Visit note in CRM
logged · recording kept
03 · HARNESS
VOHO BANKING AI HARNESS
ANSWER · VERIFY · ACT · EVIDENCE
VOICE
Listen · speak · barge-in
TOOLS
Core · cards · case system
MODELS
Arabic speech · LLM · risk
AGENTS
One per desk
AUTHENTICATION
Your rules, before any lookup
LIMITS & APPROVALS
Anything that moves money
EVALUATIONS
Scored on your own calls
MODEL ROUTING · CONTEXT · RAG · GUARDRAILS · PII REDACTION · HUMAN APPROVALS · AUDIT TRAIL
02 · SYSTEMS OF RECORD
01 · WHERE CUSTOMERS REACH YOU
Swipe the drawing sideways.
One AI layer. Every channel and every system behind it. Read it from the customer up.
The Voho Banking AI Harness
A model that cannot see your core banking system is a chatbot.
It does not know the balance, the decline code, the dispute rules or who is on the phone, and it certainly should not be allowed to move money. Voho is one reusable harness that gives models and agents the systems, the identity checks, the limits and the workflows of a bank, and records everything they do inside them.
A model on its own
- Cannot see the account, so it improvises
- No idea whether the caller is the customer
- Quotes a policy it half remembers
- Cannot raise the dispute it just promised
- Leaves nothing an auditor can follow
The same model, in the harness
- Reads the account only after authentication passes
- Calls core banking, the switch and the case system as tools
- Answers policy questions with the paragraph cited
- Raises the dispute and applies provisional credit
- Writes recording, transcript and every action to one record
Bank systems and rails
What you already run, left in place
- Core banking
- Card management
- Payment switch
- mada
- SARIE
- SADAD
- SWIFT
- AML / transaction monitoring
- Sanctions and PEP screening
- Nafath
- SIMAH
- CRM
- Case management
- Cisco / Avaya / SIP
- Document stores
Voho Banking AI Harness
The runtime between your systems and the models
- Tool calling
- Model routing
- Banking connectors
- Caller authentication
- Memory
- Context
- RAG
- Workflow orchestration
- Permissions
- Transaction limits
- Human approvals
- Evaluations
- Guardrails
- PII redaction
- Audit trails
- Observability
Model layer
Routed per task, never one model for everything
- Saudi Arabic speech
- Speech synthesis
- Foundation models / LLMs
- Document and ID models
- Risk and fraud models
- Your own scorecards
Agent layer
Scoped to one desk each
- Contact Centre Agent
- Disputes Agent
- Fraud Agent
- Onboarding Agent
- Financial Crime Agent
- Collections Agent
- Relationship Manager Agent
Where the work lands
Finished in the system that owns it
- Calls answered
- Disputes raised
- Cards blocked
- Cases evidenced
- Files opened
- Payments verified
- Notes written
01
Answer.
Every call picked up in Saudi Arabic or English, at three in the morning and through Eid, on the phone system you already have.
02
Verify.
Who is calling, on what account, against your own authentication rules. Nothing is looked up before the caller is who they say they are.
03
Act.
The dispute raised, the card blocked, the transfer made, the case opened, inside core banking and your case system, within the limits you set.
04
Evidence.
Recording, transcript, every tool call, the authentication result and the approval, on one record your auditors and the regulator can read.
01 · AI calling
Calls answered in Saudi Arabic, finished in core banking.
Inbound and outbound, on the Cisco or Avaya phones you already have. The caller speaks the way people actually speak, switches into English mid-sentence, and the agent works the request in your systems while the call is still live. Here is one call with the lid off: what was said, what was called, and what policy allowed.
Transcript
Authentication
Nothing about the account is readable until these pass.
Tool calls
waiting for the caller…
Policy
- Releasing a risk block on a verified caller is inside the delegated limit, so the agent completed it in the call.
- A transfer above your threshold, or a new beneficiary, would have been drafted and held for a person instead.
Illustrative call · recording, transcript and every tool call above kept on one record
02 · The rest of the floor
Not one use case. The work a bank actually runs on.
Disputes, fraud call-backs, balances and transfers, KYC packs, AML triage and the relationship manager who would rather talk than type. Same harness, different desk. Play any of them.
1 of 6 · swipe for the rest
Press play to hear how this call goes.
Case
—
Provisional credit
—
Handled by
—
Want this running in banking?
We build the first one with you, on your own systems, and it is usually working within a month.
03 · Payments and fraud
Hold the payment, call the customer, stop the loss.
Scoring a transfer is the easy half. The value is in the ninety seconds before it settles: verifying it with the customer in their own language, and holding it for a person when nobody answers. On a night with a SIM swap, an SMS code proves nothing.
Grocery, Riyadh
Utility bill
Streaming service
New beneficiary · another bank
Coffee shop, Jeddah
Airline
Known beneficiary · salary
Scored on device, beneficiary age, velocity, the amount against the customer's own norm and the carrier feed. Everything under your threshold settles untouched.
SARIE 48,500 SAR · risk 0.94
Beneficiary added 22 minutes ago
First payment to this IBAN
Device changed this evening
New handset, same number
Carrier reports a SIM swap 2 hours ago
Telco feed
Amount is 12× the 90-day norm
SAR 48,500 against a 4,050 median
Fraud Agent: hold the transfer and verify with the customer before it settles. The SIM swap means an SMS one-time code proves nothing tonight.
04 · Onboarding, KYC and documents
The file is read before your officer opens it.
A corporate pack arrives in two languages, half of it photographed. It is read, checked against itself, screened against sanctions, PEP, adverse media and the bureau, and put in front of a compliance officer as a drafted rating with everything attached, including what does not add up.
01 · The pack arrives
Commercial registration
السجل التجاري
Articles of association
عقد التأسيس
Board resolution
قرار مجلس الإدارة
National IDs · 3 signatories
الهويات الوطنية
Audited financials FY25
القوائم المالية
Scans, phone photographs and a PDF export, in two languages and two numeral systems. Nothing is retyped.
02 · Read and cross-checked
legal_name_ar
شركة الواحة للتجارة
legal_name_en
Al Waha Trading Co.
cr_number
1010XXXXXX
cr_expiry
2027-03-14
paid_capital_sar
5,000,000
authorised_signatory
Signatory 2 of 3
ubo_ownership
3 owners · 62 / 23 / 15%
Signatory matches the board resolution
CR valid at submission, expires in 6 months
Ownership adds to 100% across the articles
Address on the CR differs from the application form
03 · Screened and rated
Sanctions
clearNo match on any owner or signatory
PEP
reviewOne owner related to a public official · declared
Adverse media
clearNo relevant findings in Arabic or English
SIMAH
clearFacilities consistent with the declaration
Drafted risk rating
Medium
Declared PEP relationship and an address mismatch, against a clean CR, consistent ownership and no sanctions or adverse media.
Awaiting the compliance officer · nothing is opened without a person
Across the bank
One harness. Every desk that answers a customer.
The telephony integration, the connectors, the authentication rules and the evaluation set are built once. Each new desk is an agent and a workflow on the same foundation, not another procurement cycle.
Retail and cards
The queue that never empties
- Balance, statement, transfer and standing-order calls finished without a person
- Card disputes opened with the transaction, the merchant and provisional credit applied
- Lost, stolen and blocked cards handled in one call, replacement ordered
- Outbound fraud verification before the customer notices the payment
- Limit increases, address changes and product questions, inside your rules
Corporate and SME
Onboarding and relationship work
- Commercial registration, articles and IDs read, checked and cross-referenced
- Screening against sanctions, PEP and adverse media before the file is opened
- Payment and beneficiary queries answered against the actual SWIFT or SARIE message
- Relationship managers dictate a visit note and the CRM updates itself
- Trade and facility documents read and tied to the limit they draw on
Risk, compliance and operations
The work nobody has enough people for
- AML alerts triaged with the evidence pack assembled, never closed automatically
- Reconciliation breaks explained against the underlying transactions
- Complaints classified, routed and answered within the regulatory clock
- Policies and procedures answerable with the paragraph cited
- Quality assurance on every call instead of a two per cent sample
Connectors
One AI layer. Every system behind the counter.
No core replacement, and no data lake before the first answered call. The harness reads and writes through connectors your information security team can review, with the same permission and audit model everywhere.
Core banking
Temenos, Finacle, Flexcube, Mambu and the rest
Cards and switch
Authorisations, declines, blocks, replacements
mada · SARIE · SADAD
Local rails, with SWIFT for the rest
AML and sanctions
Transaction monitoring, screening, case systems
Nafath · SIMAH
Identity and credit bureau, where you are entitled
CRM and cases
Salesforce, Dynamics, ServiceNow
Telephony
Cisco, Avaya, SIP. Your numbers, your queues
Documents
Policies, procedures, contracts, customer files
Built for a regulated bank
The questions risk asks, answered in the product.
Every boundary below is part of the harness rather than a promise in a slide: they are configuration your own teams set and can audit.
Authentication before anything is read
The agent gets nothing about an account until the caller passes your own authentication rules. Failed verification ends the call or goes to a person, and is logged either way.
Limits on anything that moves money
Transfers, credits and blocks run inside the limits you configure. Above them, or outside pattern, the action waits for a named person to approve it.
Inside your own network
On your servers, or in a Saudi region. Recordings and transcripts stay where your policy says, and models run where the data is.
Never trained on your customers
What your customers say and send is used to serve that request. It is not used to train models, ours or anyone else’s.
Evidence on every interaction
Recording, transcript, tool calls, authentication result, approvals and outcome, on one record, streamed to your own systems for QA, audit and the regulator.
Evaluated on your own history
Before go-live the agents are scored against your past calls and closed cases: what they would have answered, what they would have raised, and where they would have handed over.
From the library
What this would look like at companies you know.
Demonstrations, not customer work. We built five agents for each of these organisations from public knowledge of how they run; none of them asked, and none of them run this today. Open one to see this page’s argument applied to a bank or insurer you recognise.
Al Rajhi Bank
Banking
The largest Islamic bank in the world by market value, and the branch network most Saudis actually bank with.
Run the demos →Saudi National Bank (SNB)
Banking
A Saudi bank contact-centre demo spanning live agent assist, automatic wrap-up, policy retrieval, document work and dispute triage.
Run the demos →Burgan Bank
Banking
A Kuwaiti retail-bank demo spanning product questions, account servicing, bounded card actions, fraud disputes and personalised offers.
Run the demos →Riyad Bank
Banking
One of the Kingdom’s largest lenders to businesses, and the bank a great many government salaries land in.
Run the demos →Banque Saudi Fransi
Banking
A corporate and trade bank: the one an importer calls when a letter of credit is the only thing between a ship and a berth.
Run the demos →Saudi Awwal Bank (SAB)
Banking
A corporate and wealth bank with deep correspondent reach, which means most of its hard calls are about a payment that stopped somewhere else.
Run the demos →Bank Albilad
Banking
An Islamic bank whose remittance network makes it the bank a very large share of the Kingdom’s expatriate workforce actually uses.
Run the demos →Alinma Bank
Banking
A digital-first Islamic bank: most of its customers open an account without ever meeting anyone.
Run the demos →How a project runs
Start with one call type. Keep the harness.
The first project proves itself on a number your contact centre already reports. Everything it builds carries into the next desk.
01
Take one call type
Balance and card blocking, or disputes. Something with volume, a clear outcome and a number your contact centre already reports.
02
Connect the harness
Your telephony, core banking read access and the case system, inside your network, reviewed by information security before a single call is routed.
03
Replay your own calls
The agents are measured against real calls that already happened, and against your authentication and complaint rules, before any customer hears one.
04
Go live on a slice, then widen
A percentage of calls, out of hours first if you prefer, with handover to your people always available. The next desk reuses the same harness.
What risk, operations and the contact centre ask first.
If your question is not here, bring it to a technical session with our engineers.
01Can it move money, and what stops it moving the wrong money?
It can complete the transfers and credits you allow it to, and nothing else. Every action runs inside configured limits, against an authenticated caller, and anything above the limit or outside the customer’s normal pattern waits for a person to approve it. Every attempt, successful or not, is on the audit trail.
02How does it verify who is calling?
With your existing rules, not ours: the number, knowledge factors, OTP, card and ID details, and voice where you use it. Until those pass, the agent has no access to the account. You decide what each action requires, so a balance enquiry and a transfer need not be the same bar.
03Which systems does it connect to?
Core banking platforms such as Temenos, Finacle, Flexcube and Mambu, card management and switch systems, the local rails (mada, SARIE, SADAD) and SWIFT, transaction monitoring and sanctions screening tools, Nafath and SIMAH, CRM and case management, and your Cisco, Avaya or SIP telephony. Where a connector does not exist yet, we build it on the same permission and audit model.
04Does it really handle Saudi Arabic, not just formal Arabic?
Yes. Callers speak the way they actually speak, including Najdi and Hijazi, switch into English mid-sentence and say amounts in either language. The agent handles code-switching and reads numbers back the way a person would.
05What happens when it cannot help?
It hands over to one of your people, with the name, the summary and everything already done on screen. The customer does not start again, and the call is never dropped into a dead end.
06Where do the recordings and transcripts live?
Wherever your policy requires: your own data centre, or a Saudi cloud region. They are retained for as long as Saudi rules require and no longer, and only the staff you name can read them.
07How do you stop it making something up on a customer call?
Answers about an account come from a tool call into your systems, not from the model’s memory, and anything policy-related is answered from your documents with the paragraph cited. Where there is no source, the agent says so and hands over. Those boundaries are tested in evaluation before go-live and monitored after it.
08What does a first project look like?
One call type, connected in your network, replayed against your own history, then live on a slice of traffic with handover on. Everything it builds, the telephony integration, the connectors, the authentication rules and the evaluation set, carries into the next desk.