A Manual Task is the correct orchestration item whenever fulfillment depends on deliberate human input. Associating an OmniScript with that task gives the technician or warehouse user a guided form to capture identifiers, tracking data, installation details, or other operational values with validation and a controlled completion path. Once the Manual Task is completed, Order Management can continue with the dependent automated steps. This is the decisive architectural point in this scenario because the Salesforce Industries model separates commercial selling concerns from fulfillment, lifecycle, and integration concerns. Auto Tasks and Callouts are intended for automated processing, while Push Events wait for externally initiated state changes. None provides the required user-facing guided data-entry experience by itself. Using the standard capability also keeps the design supportable across releases, reduces unnecessary custom code, and makes operational behavior easier to trace during troubleshooting. From an implementation perspective, the configuration should be tested with representative product structures and transaction volumes so that rules, mappings, and downstream dependencies behave exactly as intended. The resulting design is therefore both functionally correct and aligned with the managed Communications Cloud operating model.

Study Guide Reference:Manual Tasks; manual queues; OmniScript; human-in-the-loop fulfillment; order enrichment.