Decide what may leave before connecting
Not every organisation can handle calls in the same way. OSSA supports approaches with different degrees of external connection. Selection happens before deployment, considering transaction data, required capacity and the services the institution permits.
What the system contributes
The architecture supports a connected edition, where only the reasoning component may use an external provider under policy, and an isolated edition where recognition, reasoning and synthesis run locally. The choice depends on data, regulation, security, required capacity and the actual integration.
Connected does not mean uncontrolled
In a connected mode, reasoning may use an external provider under defined policy while recognition and synthesis are planned locally. What crosses that boundary and how it is protected must be explained. An edition name does not replace inspection of the actual flow.
Isolated also needs evaluation
Running recognition, reasoning and synthesis locally requires suitable hardware and workflow-quality testing. It does not remove telephony infrastructure needed to receive calls. Both approaches are compared using representative cases so the choice follows operational needs rather than abstract privacy or performance promises.