A Screen Flow created in Flow Builder is specifically designed to collect information interactively from users. Administrators can present screens containing inputs, choices, record fields, instructions, and other components and then use the submitted information to query, create, update, or otherwise process Salesforce data.

Salesforce supports several standard methods for distributing a screen flow to internal users. A flow can be embedded directly in a Lightning page, started through a button or action, exposed through a URL, or surfaced through supported Lightning components. This directly matches the requirement in option A.

The remaining options correspond more closely to other automation capabilities. Very-large-scale operations can require other asynchronous or batch-processing approaches when Flow execution limits are inappropriate. Personalized recommendations can use dedicated decisioning or Next Best Action capabilities. Coordinating several flows across teams and individuals is characteristic of Flow Orchestration, which provides stages, steps, and work items rather than a standard standalone Flow Builder screen-flow use case.

For Agentforce Financial Services implementations, Screen Flow is particularly useful for guided internal processes such as identity verification, customer servicing, structured intake, and other processes in which an employee must enter information through a controlled user interface.