Menu
Portfolio · Operational AI

Suri turns conversation into governed work.

Identity, knowledge, context, memory and workflow connect the request to people and enterprise applications.

A working reference for our engineering capability. Client solutions are designed around their own workflow, controls and selected technology.

Tenant portalDemo environment
Suri tenant portal in a demo environment, with dashboard, modules and the Ask Suri conversation entry point
SuriWhatsApp
Today
Hi Suri, can I claim this taxi trip?09:41
Receipt · imagetaxi-receipt.jpg09:41
SGD24.00 for a client visit. Submit for approval?09:42
Yes, please.09:42
Submitted · CLM-024. Waiting for your manager.09:42
SuriTelegram · bot
Today
Approve CLM-024 and update Expenses.10:15
Approved. Shall I record it in Expenses?10:15
Yes, update it.10:15
Expenses updated. Employee notified.10:15
Illustrative chats · fictional claim
Familiar conversation. One connected workspace.
The work between applications

One request.
Too many loose ends.

“I sent the receipt.”Employee
“Where is the evidence?”Operations
“Who can approve?”Manager
“Has the system been updated?”Finance
The operational gap

Requests arrive. People reconstruct the process.

Most organisations already have capable applications. The expensive work sits between them: interpreting a request, finding context, checking policy, securing authority, updating records and explaining the outcome.

01Request arrivesEmail · chat · form
02Evidence is chasedDocuments · facts · policy
03Authority is foundOwner · manager · exception
04Systems are updatedOne record at a time
How the reference works

One operating layer connects the experience to governed execution.

Suri identifies the user and role, retrieves approved knowledge and current context, remembers case state, follows defined workflow, coordinates approvals and uses approved integrations. Exceptions return to people with their context and evidence intact.

Interaction journey · illustrative receipt claim

A person can act. Suri can act. The outcome stays visible.

The workflow can hand execution to a manager—or let Suri update the application within its permitted authority and inform the people involved.

Human · requester

Employee asks

WhatsApp Telegram Tenant portal

“Suri, submit this receipt.”

AI · coordination

Suri prepares

Identity & context Policy & permissions

Checks the evidence and allowed action. Seeks human approval where required.

Route A · human-led
Manager / HR

Manager updates application

Application UI / tenant portal

The person reviews, decides and writes the record.

or
Route B · Suri-led
Suri

Suri updates application

Approved API / connector

Performs the permitted update; escalates exceptions to a person.

Application · record

System confirms

HR / finance record Confirmed status

The actual application result returns to the workflow.

AI → human · feedback

Suri informs people

Chat / portal notification

“Expenses updated.” The requester and relevant manager see the confirmed outcome.

Both routes follow policy, permissions and required approvals. Suri reports confirmed results—not an assumed success.
Representative workflows

The same controlled pattern, applied to real operating work.

Twelve reference workflows show how the operating pattern applies across departments. A client engagement selects and validates the workflow, authority and integrations it needs.

People operationsLeave requestEmployee request → policy and balance check → manager decision → HR record and notification
Expense operationsReceipt claimReceipt and purpose → fact extraction → policy check → approval and reimbursement status
Customer operationsCustomer issueCustomer message → approved context → owned case → cross-department answer and timeline
Finance operationsInvoice to paymentBilling request → validated invoice → customer delivery → payment matching and evidence
People operationsAdd employeeOwner or HR request → required facts → employee record → authorised setup and recorded identity
Sales operationsQuote approvalCustomer and products → commercial facts → authority check → approved customer delivery
Payroll operationsPayroll runPayroll inputs → reviewable run → second approval → payslips and controlled bank file
Statutory operationsStatutory filingApproved payroll facts → authority-specific file → submission status → retained receipt and audit evidence
Finance operationsSupplier paymentVendor bill → policy and approval → controlled payment file → bank confirmation and record
Finance operationsBank reconciliationStatement activity → likely matches → exception review → confirmed period close
Compliance operationsExpiring documentRegistered expiry → scheduled risk scan → employee or HR reminder → updated record and visible exception
Care operationsBenefit questionEmployee or agent question → identity and authority → current People projection → grounded answer or HR exception
Demonstrates

Controlled orchestration

AI coordinates without silently becoming the decision authority.

Demonstrates

Operational continuity

Relevant user and case state can continue across conversations and hand-offs.

Client relevance

One bounded workflow

The same pattern can inform a Blueprint or controlled pilot using client-selected technology.

Contact us

Which operating problem should we start with?

Tell us what is slowing the work down, what you want to change and which people or systems are involved. We can discuss a Blueprint, a pilot, an implementation or a defined enterprise technology mandate.

The problemWhat is happening today?The outcomeWhat should improve?The environmentWho and what is involved?
Singapore
Malaysia