Explanation
The three OmniStudio tools that are needed to meet these requirements are: FlexCards, OmniStudio Actions, and OmniScript. A FlexCard is a tool that can display data and actions in a card format. The consultant can use a FlexCard to display the account information and icons for each action. An OmniStudio Action is a button that can invoke an OmniScript or an Integration Procedure from a FlexCard. The consultant can use OmniStudio Actions to launch guided processes for frequent tasks, such as change of plan, new sale, or loyalty. An OmniScript is a tool that can design customer interactions using elements and actions. The consultant can use OmniScripts to create the guided processes for each task

The two FlexCard features that the consultant should recommend to meet these requirements are Datatable and Repeat Block. A Datatable element can display a list of records in a tabular format, with columns for each field and rows for each record. The consultant can use a Datatable element to display the contacts for an account, with options to edit or send a message. A Repeat Block element is a container that can display multiple instances of a FlexCard based on a data source. The consultant can use a Repeat Block element to display a FlexCard for each contact, and use a condition to apply a blue border for the primary contact

A single massive OmniScript is a poor design because it mixes unrelated business journeys into one oversized guided process. Sales, Service, and Billing usually have different data needs, validation rules, actions, user personas, and branching paths. Combining them creates heavy conditional logic, makes regression testing harder, increases the chance of defects, and slows load/render performance because users may load logic they do not need. The stakeholder ' s " everything in one place " argument sounds simple, but it is not maintainable at scale. Better OmniStudio design separates complex processes into focused scripts or reusable subcomponents. Caching does not solve bad branching architecture. Reducing component count is not a valid goal if the result is fragile, slow, and difficult to test. Salesforce ' s Integration Procedure and OmniStudio best-practice guidance favors modular, maintainable component design.

The OmniStudio tool that should be used to meet this requirement is FlexCards. A FlexCard is a tool that can display data and actions in a card format. The consultant can use FlexCards to show all of the customer's related information on one screen, such as account information, contacts, cases, etc. FlexCards can also have actions that can invoke OmniScripts or Integration Procedures for further interactions, such as creating new records or updating existing ones