OmniScript features include Dynamic Branching and Script Component Visibility.

OmniScript features include Dynamic Branching and Script Component Visibility.

• A. Dynamic Branching and Script Component Visibility
• B. Client-Side Execution to Maximize Speed and Scalability
• C. Real-time Call-Outs to Salesforce Objects and External Systems
• D. All data stored in Salesforce Object fields

Answer: (A)

OmniScript is built to adapt the user journey as you go, and two key ways it does that are Dynamic Branching and Script Component Visibility. Dynamic Branching lets the flow decide which path to take next based on data you’ve gathered or conditions you’ve defined, so different inputs or outcomes lead to different sequences without writing custom code. Script Component Visibility lets you show or hide parts of the script UI depending on runtime rules, keeping the interface clean and relevant for each user. Together, these features empower you to create flexible, responsive guided experiences inside OmniScript. The other options describe capabilities OmniScript can support in practice, but they aren’t the defining features in this context. For example, while you can perform callouts to Salesforce or external systems and you can map data to Salesforce fields, those are implementation details enabled by integrations and data flows, not the specific features highlighted here. And data in an OmniScript isn’t stored exclusively in Salesforce object fields—the script maintains its own data model and only persists data to Salesforce when you route it through the appropriate integration steps.

OmniScript is built to adapt the user journey as you go, and two key ways it does that are Dynamic Branching and Script Component Visibility. Dynamic Branching lets the flow decide which path to take next based on data you’ve gathered or conditions you’ve defined, so different inputs or outcomes lead to different sequences without writing custom code. Script Component Visibility lets you show or hide parts of the script UI depending on runtime rules, keeping the interface clean and relevant for each user. Together, these features empower you to create flexible, responsive guided experiences inside OmniScript.

The other options describe capabilities OmniScript can support in practice, but they aren’t the defining features in this context. For example, while you can perform callouts to Salesforce or external systems and you can map data to Salesforce fields, those are implementation details enabled by integrations and data flows, not the specific features highlighted here. And data in an OmniScript isn’t stored exclusively in Salesforce object fields—the script maintains its own data model and only persists data to Salesforce when you route it through the appropriate integration steps.