Data destinations and model access

Before using customer information, inventory the destinations configured for this installation: model services, telephony, storage, tracing and business actions. The hosting location of the IntraCord application is only one part of that inventory.

Map each data flow

Listening services receive audio. Reasoning services can receive prompts, conversation history and tool results. Speaking services receive generated text. Realtime models handle spoken input and output. Document retrieval can send document content to the configured embedding service.

Webhook targets, MCP servers and HTTP actions receive the fields you configure. Check their request templates and authentication as part of the same review. Tracing is a separate destination when enabled.

Plan a local deployment

For local processing, select local model endpoints and verify the network path for every service. Test a conversation with external destinations blocked in a controlled environment. Do not describe an installation as entirely local while it still depends on an external speech or embedding service.

Retention and access

Decide who may view conversation records and recordings, how long they are needed, and how deletion reaches backup copies. Configure this for the actual storage and operating procedures in use. This guide does not imply that an automatic retention policy or a particular regional hosting guarantee is enabled by default.