{"id":1555,"date":"2024-07-16T00:30:55","date_gmt":"2024-07-16T00:30:55","guid":{"rendered":"https:\/\/es.notificationbutton.com\/help\/index.php\/es\/configuracion-general\/mis-creditos\/"},"modified":"2026-04-30T18:39:44","modified_gmt":"2026-04-30T18:39:44","slug":"resource-allocation-for-orchestration","status":"publish","type":"docs","link":"https:\/\/icortex.ai\/help\/planes-y-creditos\/resource-allocation-for-orchestration\/","title":{"rendered":"Resource Allocation for Orchestration"},"content":{"rendered":"\n

The <\/mark>orchestration resources<\/mark><\/strong> are equivalent to the capacity for transactional messages that you can issue from the iCortex Engineering Revenue Ecosystem. Each resource allows for the delivery of hyper-segmented content to a target Profile. A larger inventory of resources increases the opportunities for Campaign Orchestration, asset promotion, and the consolidation of the Profile base.<\/p>\n\n\n\n

Definition and Location<\/h2>\n\n\n\n

Within the iCortex\u2122 Engineering Revenue Ecosystem, the capability to orchestrate the distribution of communications (e-mails) to your Profiles is enabled (if you need to optimize the sending configuration, consult the relevant documentation here<\/mark><\/a>). <\/p>\n\n\n\n

The execution of this Orchestration requires the allocation of resources<\/strong>, where 1 resource = 1 communication issued<\/strong><\/mark>.<\/p>\n\n\n\n

The volume of available resources is determined by the selected Service Tier<\/strong>. Each Service Tier establishes a maximum limit of managed Profiles; for example, if your Service Tier supports 5,000 Profiles, you will be allocated 10,000 resources, maintaining the established ratio.<\/p>\n\n\n\n

The allocated resources are visible in the following areas of the iCortex\u2122 Ecosystem: <\/p>\n\n\n\n

\u2705Top Navigation Bar <\/strong><\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Visualization of resources in the top bar of the iCortex\u2122 Ecosystem. <\/figcaption><\/figure>\n\n\n\n

\u2705Revenue Recovery Configuration <\/strong><\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Visualization of resources in the Revenue Recovery section of the iCortex\u2122 Ecosystem. <\/figcaption><\/figure>\n\n\n\n

\u2705Orchestration Module <\/strong><\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Visualization of resources in the Orchestration module of the iCortex\u2122 Ecosystem. <\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Operational Considerations<\/h2>\n\n\n\n
<\/div>\n\n\n\n
    \n
  • Resources obtained through Service Tiers are valid for 30 calendar days<\/strong> \ud83d\uddd3\ufe0f. The expiration date is set 30 days after the activation of the Service Tier. <\/li>\n<\/ul>\n\n\n\n
    <\/div>\n\n\n\n
      \n
    • Resources do not accumulate between billing cycles<\/strong>. Any resource not consumed within the 30-day period is deactivated and does not transfer to the subsequent cycle. Optimization of monthly consumption is recommended.\ud83d\udc4c<\/li>\n<\/ul>\n\n\n\n
      <\/div>\n\n\n\n
        \n
      • If demand exceeds the current allocation, recalibration of the Service Tier<\/strong> to a higher structure that accounts for greater Profile capacity is recommended. <\/li>\n<\/ul>\n\n\n\n
        \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
        iCortex\u2122 Service Tiers menu. <\/figcaption><\/figure>\n\n\n\n
        <\/div>\n\n\n\n

        Impact of Resource Insufficiency<\/h2>\n\n\n\n

        Recurring resource scarcity requires an immediate review of the Service Tier or the activation of a temporary capacity injection.<\/p>\n\n\n\n

        The lack of resources directly impacts the efficiency of your Orchestration strategies and the projected Return on Investment (ROI).<\/p>\n\n\n\n

        \ud83d\udccc Message Orchestration stops for the following flows:<\/p>\n\n\n\n

          \n
        • Revenue Recovery.<\/li>\n\n\n\n
        • Automated welcome messages.<\/li>\n\n\n\n
        • Brand reminders.<\/li>\n\n\n\n
        • Recommendations, social validation, and loyalty strategies.<\/li>\n\n\n\n
        • Orchestrations generated by iCortex\u2122 AI Stylizer.<\/li>\n<\/ul>\n\n\n\n
          <\/div>\n\n\n\n

          Ensure constant resource availability to maintain the continuous operation of your growth infrastructure. \ud83d\udee0<\/p>\n\n\n\n

          <\/div>\n\n\n\n

          Temporary Resource Injection<\/h2>\n\n\n\n

          An alternative is to request an injection of additional resources<\/strong> by contacting the support team directly. Temporary resource injection carries an additional cost; therefore, Service Tier recalibration is the preferred path for recurring needs.

          – If a one-time injection is required, these additional resources do not expire and remain available for use according to operational needs.

          – If the Profile base consistently approaches the limits of the current Service Tier, migrating to a higher Tier is more cost-efficient.<\/p>\n\n\n\n

          <\/div>\n\n\n\n

          <\/p>\n\n\n\n

          \n\n\n\n

          <\/p>\n","protected":false},"excerpt":{"rendered":"

          Detail of the resource allocation (credits) required for the execution of campaign orchestration within the iCortex\u2122 Engineering Revenue Ecosystem.<\/p>\n","protected":false},"author":5,"featured_media":1823,"parent":1815,"menu_order":2,"comment_status":"closed","ping_status":"closed","template":"","doc_tag":[294,66,509,508,506,507,505],"doc_badge":[],"class_list":["post-1555","docs","type-docs","status-publish","has-post-thumbnail","hentry","doc_tag-credits","doc_tag-email","doc_tag-expiration","doc_tag-expire","doc_tag-purchase","doc_tag-recharge","doc_tag-upload"],"acf":[],"_links":{"self":[{"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/docs\/1555","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/comments?post=1555"}],"version-history":[{"count":16,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/docs\/1555\/revisions"}],"predecessor-version":[{"id":4987,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/docs\/1555\/revisions\/4987"}],"up":[{"embeddable":true,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/docs\/1815"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/media\/1823"}],"wp:attachment":[{"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/media?parent=1555"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/doc_tag?post=1555"},{"taxonomy":"doc_badge","embeddable":true,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/doc_badge?post=1555"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}