Design Trailblazers

Hi everyone,

We are working with Salesforce Agentforce Employee Agent, and we need to store the conversations that users have with the agent for auditing and analytics purposes.

Our goal is to save:

•  user questions 
•  agent responses 

We would like to know if there is any standard or recommended Salesforce configuration to store the full conversation between the user and the Employee Agent, so we can later perform analysis on those conversation records.

We are especially interested in understanding:

•  whether Agentforce already provides built-in conversation persistence 
•  recommended architectures or best practices 
•  if teams typically use custom objects, Platform Events, Data Cloud, Apex, Flows, or another approach 
•  and how other organizations are handling conversation logging in production environments 

Has anyone implemented this successfully or can share the recommended pattern?      @* Customer Success * @* Known Issues * @* Salesforce Administrators * @Salesforce Flow Automation @* Salesforce Developers * @Design Trailblazers @Slack + Agentforce

Hi Trailblazers! The design systems team is recruiting a limited cohort for two upcoming SLDS 2 pilots and want you involved! The two pilots are:

• Permission-Based Theme Activation (May '26) - Run SLDS 2 alongside your existing theme for a subset of users. Phase your rollout by business group, validate with a pilot audience, and migrate at your own pace — with zero disruption to the rest of your org.
• SLDS 2 Theme Builder (June '26) - Style your org globally with clicks, not code. Set brand colors, typography, and spacing directly in Setup → Themes & Branding. Accessibility guardrails are built in, and your theme stays compatible as Lightning evolves.

Pilot participants get direct access to the SLDS 2 product team and early configuration support. To join the pilot: 

1. Fill out the interest surveys: 
   • Permission-Based Theme Activation survey
   • SLDS 2 Theme Builder survey
2. Contact your Account Executive about your interest in the pilot

Spots are limited so please enroll by May 22nd! 

Hi, When converting a Lead into a Contact, the Contact was assigned the “Student” record type, but it should not have happened that way. 

The expected behavior is for the Contact to be created with the “Applicant” record type. 

Where can I configure the default record type for Contact during Lead conversion, without modifying the standard conversion component, since the conversion is being done through the standard Salesforce process? 

The curious part is that this only happens in the UAT environment.

In Production, when converting the Lead using the standard Salesforce conversion process, and without explicitly selecting a specific record type, the Contact is correctly created with the “Applicant” record type.

However, I cannot find where this behavior is defined at the configuration level, and I would like to understand what setting controls this default assignment.