When designing OmniScripts, the best practices that should be followed to optimize performance and user experience are:
Use a single DataRaptor to save the information: Instead of using multiple DataRaptors to update the account information after each step, it is better to use a single DataRaptor at the end of the OmniScript to save all the information at once. This reduces the number of database operations and improves performance.
Combine the three steps into one step: Instead of having three separate steps to capture the required information, it is better to combine them into one step with a simple layout. This reduces the number of page transitions and improves user experience.
The suggestions that are not best practices are:
Create a reusable OmniScript for this process: This may not be necessary if the process is specific to creating new billing accounts and not used by other OmniScripts. Creating a reusable OmniScript may add complexity and maintenance overhead.
Configure the save for later property: This may not be useful if the process is short and simple and does not require the user to resume it later. Configuring the save for later property may add unnecessary storage and retrieval logic.

Explanation
The consultant should suggest removing Step 1 and prefilling the account information automatically to improve the design. Since the OmniScript will be launched from an account detail page, there is no need to ask the user to enter the account name again. The consultant can use an Input Parameter element to pass the account ID from the page to the OmniScript, and then use a DataRaptor Extract Action element to retrieve the account information and display it in Step 2. This will save time and avoid errors

Explanation
Based on the user analysis exhibit, the three actions that should appear on the card are: verify a transaction, request higher limit, and make a payment. These actions have the highest frequency and importance scores among the six actions listed. The other actions, such as view credit score history, view statements, and view rewards, have lower frequency and importance scores, and can be accessed through other means

The three OmniScript elements that should be used to meet these requirements are: Select, DataRaptor Extract Action, and DataRaptor Post Action. A Select element can display a dropdown list of options for the user to choose from, such as payment type. A DataRaptor Extract Action can retrieve data from a Salesforce object, such as saved payment information, and store it in an Interface object or a JSON object. A DataRaptor Post Action can write data to a Salesforce object, such as new payment information, and perform insert or update operations