> ## Documentation Index
> Fetch the complete documentation index at: https://docs.operata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sanas integration

> Operata reads the headset connected behind the Sanas application, so device attribution survives the audio processing layer.

Sanas processes the agent's audio between the headset and the softphone. The integration lets Operata capture the headset connected behind it, so you keep device attribution on calls that run through Sanas.

## Before you start

* Operata Agent Collector browser extension v1.9.6 or later.
* Sanas software version 3.1.6.0.
* The Sanas application (Node.js) installed on the agent's operating system, Windows or macOS.
* Local socket connectivity enabled on the agent's machine.

<Warning>
  Sanas needs local socket connectivity on the agent's machine. Raise this with your security team before you roll it out.
</Warning>

<Note>
  The minimum Chrome and Edge versions for this integration are being confirmed. Contact [support@operata.com](mailto:support@operata.com) for current requirements.
</Note>

## Verify

Open the **Headset Inventory** page. With the integration working, each agent row shows the headset connected behind Sanas.

## Troubleshooting

If Headset Inventory shows no headset for a Sanas agent:

* Confirm the Agent Collector extension is v1.9.6 or later.
* Confirm the Sanas application is running and on version 3.1.6.0.
* Confirm endpoint security software isn't blocking local socket connectivity.

## Related

* [Agent headsets and AI audio tooling](/docs/integrations-headsets-and-audio-tooling) — the capability and the other vendors.
* [Krisp integration](/docs/help/krisp-integration) — noise cancellation and accent conversion state.
* [Headset logs](/docs/headset-logs) — the fields Operata stores.