Architecture
OpenOS runs the operation. The client's systems keep the record of truth.
Telephony, the WhatsApp provider, the mailbox, the helpdesk, and the CRM remain the client's. OpenOS normalizes evidence and invokes only configured, authorized paths.
What is in production
Inbound email on Google Workspace and WhatsApp L0 resolution are live, with escalate-to-Workspace, Quality on eligible close, and Trinetra Decision Cards. The platform is hosted on AWS ap-south-1 in Mumbai.
- Voice is live on Exotel and Sarvam. 11 Indian languages today, 22 targeted.
- The provider still carries the call. OpenOS keeps the operating record.
- Meta WhatsApp requires the customer's credentials and provider approval. Amcos WhatsApp is an implemented path.
What a logo means
The ecosystem page lists systems operations commonly run. An adapter in the product is not a live integration at a client. Production connections are scoped to that client's APIs, permissions, credentials, and acceptance.
What OpenOS will not claim
OpenOS does not become the carrier, the BSP, or the system of record. A generated answer is not a completed business action unless a configured tool returned evidence of it.
Questions
Direct answers
Do we have to replace our helpdesk?
No. Workspace is the OpenOS exception desk. Coexistence with an existing helpdesk is scoped per deployment.
Are CRM and ERP connections prebuilt for every tenant?
No. Connectivity is scoped against the provider API, the objects, the permissions, and the acceptance test for that client.
Tailored walkthrough
Walk through one workflow.
We will use labelled demonstration data and the channel, audit population, and baseline that match the operation you run.
- 01Your current loopChannels, systems, volume, and the operational gap.
- 02The product proofResolve, escalate, audit, and decide in one scenario.
- 03A scoped first deploymentOne workflow with explicit evidence and success measures.
Prefer email? sales@openost.com