The most efficient and standard way to automate case creation from inbound emails is by using Email-to-Case . When setting up Email-to-Case, the Platform Administrator configures "Routing Addresses" . For each routing address (e.g., [email protected] or [email protected]), the administrator can specify a default owner or queue for the cases created via that specific address . This ensures that when a customer sends an email to the "Support" address, it is automatically routed to the Support Queue, and an email to the "Billing" address is routed to the Billing Queue . This configuration is handled directly within the Email-to-Case setup pages and does not require additional escalation rules (Option A) or complex custom flows (Option C) for the initial assignment . While a custom email service (Option B) is possible, it is a developer-centric approach that is generally unnecessary given the robust native capabilities of the standard Email-to-Case feature . This setup streamlines the intake process and ensures that customer issues are immediately visible to the correct service team34.

Changing a field type is a significant configuration change that can have downstream impacts. When converting from Text to Picklist, a Platform Administrator must be aware of two critical consequences:
List View Deletion: Any list views that use that specific custom field as a filter will be automatically deleted or the filter will be removed. This happens because the filter logic for a text field (which uses operators like "contains") is fundamentally different from a picklist (which uses "equals").
Automation Impact: Assignment rules, escalation rules, and validation rules that reference the field may be disabled or function incorrectly. Because these automations rely on specific text strings, changing the field to a picklist requires the administrator to manually review and update the logic to ensure it aligns with the new picklist values.
Option A is incorrect because Salesforce does not automatically update code references. Option C is incorrect because data loss can still occur if existing text values do not exactly match the new picklist entries.

Grounding is the process by which an AI agent retrieves and uses specific, trusted data to ensure its responses are accurate and relevant41. During this process, Salesforce's Einstein Trust Layer performs several critical checks, including identifying Prompt Injection risks424242. Prompt injection refers to attempts by a user to "trick" the AI into ignoring its instructions or revealing sensitive data by entering malicious commands into the chat interface43. By checking for these risks during the grounding phase, the agent can ensure that the instructions it uses to generate a response remain secure and aligned with company policies44. While the agent respects field security, "Encrypted fields" (Option C) are handled at the data access layer rather than as part of the linguistic grounding check45. Standard Agentforce agents do not browse the open web for verification (Option D) as they are intended to remain grounded strictly in the company's verified internal data46.

Omni-Channel is a comprehensive service tool designed to route work items (like Cases, Leads, or custom objects) to the most available and qualified support agents in real-time. Unlike Case Assignment Rules, which are often static and require administrative intervention to update complex logic, Omni-Channel allows for more dynamic management through the use of Queues and Presence Statuses. By using Omni-Channel, a support manager or "Supervisor" can monitor agent workloads and adjust capacity or move people between service channels without needing to modify the underlying system configuration or involve the Platform Administrator. It supports various routing models, such as "Least Active" or "Most Available," ensuring that work is distributed fairly and efficiently. This flexibility is vital for growing organizations that need to scale their support operations quickly while maintaining high service levels. Furthermore, it provides the business with the autonomy to manage its workforce effectively, as managers can see who is logged in and what they are working on, allowing for immediate adjustments to handle spikes in case volume.

During the Lead Conversion process, Salesforce automatically transfers the history and interaction data associated with the Lead to the newly created Account, Contact, and Opportunity. This includes all activities, meaning both Open Activities (like upcoming tasks or events) and Activity History (like past emails or logged calls) are attached to the resulting records to maintain a complete customer timeline. Campaign history is also typically associated with the resulting Contact, but the question specifically asks about "related records" in a broader sense, and the transfer of all activities is a primary mechanical function of the conversion. Option A is incorrect because custom object records do not automatically move unless specific custom mapping or code is in place. Option B is incorrect because the system does not limit the transfer to only open activities.