--- schema_version: "1" id: 2dd513a717600bc47a3ab3c52b263e1c1849608674afd17c56a40a101e02831f title: Connect Related Voice Calls When Using Real-Time Streaming collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/ai/264-0-0/agent_connect_related_voice_calls_realtime_streaming.md canonical_url: https://help.salesforce.com/s/articleView?id=ai.agent_connect_related_voice_calls_realtime_streaming.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: c5f47725bc13ba76902222173c09ed06c7e5090cffa8326cd95552a83f0a3e3b description: If you’re a Salesforce Voice with Telephony Providers customer, Salesforce can create multiple voice call records for a single conversation. products: - Agentforce - Cross Cloud release: "264" --- # Connect Related Voice Calls When Using Real-Time Streaming If you’re a Salesforce Voice with Telephony Providers customer, Salesforce can create multiple voice call records for a single conversation. ### Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions with Foundations or Agentforce 1 Editions, and Salesforce Voice add-ons.
For instance, one record stores the interaction between the customer and the Agentforce agent, while another stores an escalated conversation between the customer and a human representative. Because these records don't share an identifier by default, Salesforce can't automatically associate them with the same call. To allow representatives to easily view the bot leg of a call, use custom fields to link the related voice call records. Salesforce automatically creates a voice call record for the bot leg and passes the Amazon contact ID in the `transactionId` flow variable of an Omni-Channel inbound IVR flow. To manually link the bot voice call record to a record created in the inbound flow, look up the other voice call based on the Amazon contact ID. For example, look up the rep leg record where the Vendor Call Key matches the contact ID. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ai-generative_ai-264-0-0-production-enus/f8ef6498-d7b2-44e3-9b34-ffd5a850aae9/images/icon_note.png) Note Linking related voice calls doesn't display the bot conversation transcript on the representative's voice call record. To view the transcript, representatives must open the bot voice call record directly. 1. In your Omni-Channel inbound flow, create a `transactionId` input variable that stores the Amazon contact ID. When the WebSocket connection starts, AWS passes the Amazon contact ID to your Omni-Channel flow as the `transactionId` input variable. 2. To look up the rep voice call (VC1) by Vendor Call Key: 1. Add a Get Records block to the flow. 2. Add a filter where the Vendor Call Key field = the value of the `transactionId` variable (the Amazon contact ID). ![In the original voice call record, set the Original Voice Call custom field to VC1 ID.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ai-generative_ai-264-0-0-production-enus/f8ef6498-d7b2-44e3-9b34-ffd5a850aae9/generative_ai/images/agentforce_voice_streaming_flow_get_vc1call.png) 3. To stamp the custom field in the agent voice call record (VC2): 1. Add an Update Records block. 2. To identify the agent voice call record, add a filter where the Voice Call ID field = the value of the `recordId` variable, which is the agent voice call ID. 3. Set the custom field = the value of the Voice Call ID field of the original call record, which is the rep voice call ID. In this screenshot, the custom field is named Original Voice Call. ![In the original voice call record, set the Original Voice Call custom field to VC1 ID.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ai-generative_ai-264-0-0-production-enus/f8ef6498-d7b2-44e3-9b34-ffd5a850aae9/generative_ai/images/agentforce_voice_streaming_flow_link_original_call.png) 4. To stamp the custom field in the rep voice call record (VC1): 1. Add an Update Records block. 2. To identify the rep voice call record, add a filter where the Voice Call ID field = the value of the Voice Call ID field of the original call record. 3. Set the custom field = the value of the `recordId` variable, which is the agent voice call ID. In this screenshot, the custom field is named Bot Voice Call. ![In the agent voice call record, set the Bot Voice Call custom field to VC1 ID.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ai-generative_ai-264-0-0-production-enus/f8ef6498-d7b2-44e3-9b34-ffd5a850aae9/generative_ai/images/agentforce_voice_streaming_flow_link_bot_call.png) Your inbound Omni-Channel flow might look something like this one. ![The Omni-Channel inbound flow with two Update Records blocks.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ai-generative_ai-264-0-0-production-enus/f8ef6498-d7b2-44e3-9b34-ffd5a850aae9/generative_ai/images/agentforce_voice_streaming_omni_inbound_flow.png) #### See Also - [Connecting Related Voice Calls](https://help.salesforce.com/s/articleView?id=ai.agent_connect_related_voice_calls.htm&release=264.0.0&type=5 "When a customer conversation involves call transfers, a separate voice call record can be created in Salesforce for each call segment. This action results in multiple voice call records for the same conversation. To provide a single, comprehensive view and preserve the full call context, connect these related voice call records. Connecting records enables more informed decisions. For instance, you can escalate the call to the appropriate rep based on all gathered information.")