# Run the complaint. Keep the record.

> OpenOS takes inbound support on the channels a regulated firm already uses, resolves the routine majority, hands exceptions to a person with context, and audits every eligible closed interaction.

## Key Specifications
- **Target Audience:** Heads of customer service, compliance, and technology at Indian banks, insurers, and NBFCs
- **Primary Inquiry:** How does a complaint stay defensible when most conversations are never reviewed?

## Core Architecture & Mechanism
### 1. Receive
The message arrives on the client's WhatsApp number, mailbox, or — in controlled voice activation — their telephony provider.

### 2. Resolve or stop
The published workflow uses approved knowledge and authorized tools. If the boundary is not met, it escalates.

### 3. Audit
The eligible closed interaction is scored. Coverage is reported against that eligible population.

### 4. Decide
Repeated drift — falling containment, unassigned exceptions, repeat contact — becomes a Decision Card.

## Frequently Asked Questions
### Q: Do you replace our contact centre?
A: No. We run the inbound operation on the telephony, WhatsApp, helpdesk, and CRM you already have. People still handle exceptions.

### Q: Is a named institution live?
A: Not on the strength of this website. A walkthrough uses labelled demonstration data unless a tenant is on live traffic and we say so in the contract.

### Q: How do you charge?
A: Per resolved-and-audited interaction, plus a 60-day implementation retainer. If we do not beat the agreed baseline in 60 days, the pilot is free.

## Claim Boundaries
- No named bank, insurer, or NBFC is described as a live OpenOS customer on this page.
- The failed-dispense story is demonstration data, not a production result.
- OpenOS does not publish a measured resolution rate or audit score of its own.
- Voice is live on Exotel and Sarvam. 11 Indian languages today, 22 targeted.

---
Canonical Reference: https://www.openost.com/solutions/bfsi