In Salesforce Lightning Experience, Case object activity actions differ from those of other objects. These actions are not found on the standard Activity Timeline/Composer component. Instead, they are accessible through the Chatter Feed component when working with Cases. The 'Log a Call' option within the Case Feed also provides different functionality than the 'Log a Call' button on standard page layouts or in the general Activity feed.
On a standard page, the "Log a Call" button is a standard component found within the 'Activity History' related list for standard and custom objects. More details on this standard "Log a Call" button are in the "Customizing the Log a Call Action" documentation.
This article answers the question: how does the Case Feed 'Log a Call' action differ from the standard Activity 'Log a Call' button in Salesforce Lightning Experience, and why is the "schedule a follow up" task missing from the Case Feed? The Case Feed 'Log a Call' action does not include the follow-up task, while the standard 'Log a Call' button does.
The 'Log a Call' action in the Case Feed allows support agents to record notes and information about customer calls. By default, it is assigned to the creator of the logged call, and quick notes can be added.
A key difference exists regarding follow-up tasks:
In Lightning Experience, the 'Log a Call' action is available in the Activity related component. In Salesforce Classic, the 'Log a Call' button is available in the Activity History Related List.
Notes:
If you would like to customize the 'Log a Call' option, you can use a Visualforce page. More details can be found in the
Customizing the Log a Call Action documentation.
More details on the Case Feed and Related Lists can be found in the
Case Feed and Related Lists documentation.
See Also:
000381651

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.