Insights
How the operation works, and where the claims stop.
These notes explain Decision Cards, the systems that stay with the client, and the buyers OpenOS is built for.
They do not name live customers. Product screens use labelled demonstration data.
What is a Decision Card?
A Decision Card is the generated artifact Trinetra uses to frame operational drift: issue, evidence, impact, recommendation, owner role, deadline, and confidence.
Read the guide → Architecture / 02Your telephony, WhatsApp, helpdesk, and CRM stay yours
How OpenOS connects to client-owned channels and systems of record without replacing them.
Read the guide → BFSI / 03Customer operations for banks, insurers, and NBFCs
How OpenOS runs inbound support and an auditable close for regulated financial companies in India.
Read the guide → Government / 04Helplines and utilities
How OpenOS runs a public or utility helpline without replacing the department's telephony or case system.
Read the guide →A useful reading order
Start with the record. Then the boundary.
- 01Decide
Read what a Decision Card contains, and what it does not do.
- 02Connect
See which systems stay with the client, and what is live today.
- 03BFSI
See the loop for banks, insurers, and NBFCs.
- 04Helplines
See the same loop for government and utility contact.
- 05Price
Read the commercial model before treating a range as a rate card.