Campaign Orchestration

Sumary: Campaign Orchestration is executed exclusively within the schedule parameters defined by the administrator, ensuring temporal relevance for Profiles.

The WhatsApp message delivery mechanism is governed by strict protocols. Delivery is not performed randomly, but is subject to the operational guidelines established in the iCortex Engineering Revenue Ecosystem.

Campaign Orchestration Process

When a Profile leaves an active Purchase Experience, the iCortex Engineering Revenue Ecosystem system detects the event and prepares the orchestration of a specific message directed at said Profile. Execution is subject to predefined temporal restrictions.

Operational Delivery Windows

Campaign Orchestration is conditioned by the defined operational windows. The objective is to maintain relevance and avoid interrupting Profiles outside of their expected activity hours. Messages are delivered via WhatsApp only within the time frame configured by the administrator in the application.

If an abandonment event occurs outside the configured operational window, the orchestration is postponed. The message will be released at the start of the next configured service cycle. This ensures that the communication is received at an optimal moment for interaction and potential response from the Profile.

Configuration Guideline: Precision in defining the operational schedule is fundamental to system efficiency. It is recommended to consult the documentation on configuring Orchestration Nodes to optimize these parameters.

Revenue Recovery Orchestration Content

The content of Revenue Recovery messages is designed to be informative and facilitate the resumption of the transaction. The orchestration includes:

• Identification of the issuing entity (to ensure traceability).
• A direct link for the reactivation of the pending Purchase Experience.
• Concise reference to the items retained in the cart.

The objective is to present a structured communication that drives action without generating friction in the Profile’s experience.

Optimal Latency in Revenue Recovery

A recommended execution window of 120 minutes after the detection of abandonment is established for the activation of WhatsApp orchestration.

This time interval is calibrated to coincide with the retention of the Profile’s purchase intent, minimizing the perception of excessive urgency.

Alternatively, the system allows for the configuration of an extended latency of 6 hours.

This automation guarantees the acquisition of precise metrics on the Revenue Recovery rate through the systematic execution of Engagement Flows, eliminating the need for manual intervention in the management of lost revenue. The implementation of this functionality optimizes the management of abandonment event volume.

Operational validation of these protocols is recommended during a 15-day cycle for the quantitative evaluation of the results obtained.