When a Live Agent Chat (Salesforce Chat) button is configured with auto-accept and the agent does not immediately click on the chat tab after the chat is accepted, the case record associated with the chat may not be created.
Why this happens: The Chat records tab — which triggers the consoleajaxservlet call that performs the findOrCreate action (the operation that creates the case) — is only loaded when the chat tab is clicked and brought into focus in the Service Console. If the agent's connection changes (for example, the agent goes offline or loses connection) before they click the chat tab, the consoleajaxservlet call is never initiated and the case record is not created.
To confirm this behavior in your environment:
liveagent.addCustomDetail() to define case field values (for example, Case Subject and Case Status), then use liveagent.findOrCreate('Case') to map those fields to the Case object, save the transcript to a CaseId, and call showOnCreate().<script type='text/javascript'>
liveagent.addCustomDetail("Case Subject", "Test Subject");
liveagent.addCustomDetail("Case Status", "New");
liveagent.findOrCreate("Case").map("Subject","Case Subject",false,false,true).map("Status","Case Status",false,false,true).saveToTranscript("CaseId").showOnCreate();
</script>
This behavior is working as designed. Auto-accepted chats load in the background in the Service Console, but the console does not render the chat tab content until the tab is focused. Without the tab loading, the consoleajaxservlet is not called, and the findOrCreate operation that creates the case record is not executed.
Agents using auto-accept must click on the chat tab when a chat is accepted to ensure the case record is created.
Chat interactions do not create Case records
FindOrCreate cannot create transcripts records for missed chats in Live Agent routing
Chat transcript assignment for missed chats
Transcript record is not getting created when Visitor inadvertently disconnects from chat
000382631

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.