Applies to: Service Cloud Voice (Amazon Connect native + BYOT), Agentforce Voice
Voice call transcripts are generated in real time during a call and appear in the Conversation component on the Voice Call record page.
Important -Transcript Generation Delay:
After a call ends, the Conversation component may be temporarily empty for a few minutes while the transcript is being processed. This is expected behavior. To see the transcript, refresh the page. Full transcript generation can take anywhere from 15 minutes up to 24 hours depending on call length and system load. Do not assume the transcript is missing during this window.
Conversation data is stored off-core and is not accessible via SOQL queries. Do not use SOQL to retrieve transcript data - it will return 0 rows regardless of whether a transcript exists. Use the Connect API instead (see Resolution section).
Exporting Conversation Transcripts
1. Verify transcript generation status
Use the standard VoiceCall report to confirm transcript generation.
Navigate to Reports → Service Reports → VoiceCall reports.
Apply these filters:
Status: Completed
TranscribedLanguage: Not blank
If TranscribedLanguage is populated but the transcript is not visible, it may still be processing. Wait 15 minutes to 24 hours, then refresh the Voice Call record page.
Note: The Conversation component on the Voice Call page can remain empty for a few minutes after the call ends. Refresh the page to view the transcript when it is ready.
2. When to use the API
Use the Connect API to retrieve voice call transcripts programmatically. Do not use SOQL to retrieve transcript content, as conversation data is stored off-core.
Endpoint
GET /services/data/v{version}/connect/conversation/{conversationIdentifier}/entries
Steps
Retrieve the ConversationIdentifier using the VoiceCall record’s vendor call key:
SELECT Id, ConversationIdentifier
FROM Conversation
WHERE ConversationIdentifier = '<VendorCallKey>'
Call the endpoint using the returned ConversationIdentifier.
Other supported methods
| Method | Use case |
|---|---|
| Get Conversation Transcript invocable action | Use in Flows for real-time or post-call access within Salesforce automation. |
| Conversation Transcript Export Tool | Available in Setup for bulk exports. |
| Data Cloud Conversation Transcript streams | Use for analytics at scale in production orgs. |
3. Why SOQL does not work for transcript data
Conversation data is stored off-core. SOQL queries against ConversationEntry return 0 rows. This is expected and does not mean the transcripts are missing.
Use the Connect API described in Section 2 to retrieve transcript content.
https://help.salesforce.com/s/articleView?id=service.voice_transcripts.htm&type=5
https://help.salesforce.com/s/articleView?id=service.voice_perf_create_report.htm&type=5
https://help.salesforce.com/s/articleView?id=service.voice_limitations.htm&type=5
005460501

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.