When designing OmniScripts, the best practices that should be followed to increase user adoption are:
* Prefill data for users when possible (This reduces user effort and improves data quality)
* Divide complex processes into sections (This makes the script more manageable and user-friendly)
* Provide user help text (This guides the user through the script and clarifies any doubts) The best practices that should not be followed to increase user adoption are:
* Replicate existing processes as-is (This may not leverage the full potential of OmniStudio and may not address the pain points of the users)
* Provide keystroke commands for data entry (This may not be intuitive or accessible for all users and may require additional training)

The three OmniScript elements that the consultant should recommend to meet these requirements are:
DataRaptor Post Action, Multi-select Input, and HTTP Action. A DataRaptor Post Action is an action that can write data to a Salesforce object or invoke a Salesforce API. The consultant can use a DataRaptor Post Action to save the data back to Salesforce as a lead. A Multi-select Input is an element that can display a list of options for the user to choose from, such as energy products. A Multi-select Input allows multiple options to be selected at once, and can also have icons for each option. An HTTP Action is an element that can invoke a REST or SOAP service to retrieve data from an external system, such as current energy usage data. An HTTP Action can store the response data in a JSON object for further processing

The consultant should recommend adding a Set Errors element to meet this requirement. A Set Errors element can display an error message and prevent the OmniScript from proceeding if certain conditions are not met.
The consultant can use a Set Errors element to check if the email address field is empty when the agent selects the checkbox to email the receipt. If it is empty, the Set Errors element can show an error message and direct the user to return to the first step and enter the customer's email address

The consultant should recommend adding a Set Errors element to meet this requirement. A Set Errors element can display an error message and prevent the OmniScript from proceeding if certain conditions are not met. The consultant can use a Set Errors element to check if the email address field is empty when the agent selects the checkbox to email the receipt. If it is empty, the Set Errors element can show an error message and direct the user to return to the first step and enter the customer's email address

The OmniScript element that can be used to retrieve data from more than one source is Integration Procedure Action. An Integration Procedure Action can execute an Integration Procedure that can combine multiple DataRaptor actions, such as Extract, Transform, and Load, and also invoke REST or SOAP services. This way, the Integration Procedure Action can retrieve data from different sources, such as Salesforce objects or external systems, and store it in a JSON object for the OmniScript to display