{"id":1544,"date":"2024-07-15T23:17:30","date_gmt":"2024-07-15T23:17:30","guid":{"rendered":"https:\/\/es.notificationbutton.com\/help\/index.php\/es\/automatiza-tu-tienda\/recuerdo-de-marca\/"},"modified":"2026-05-01T06:19:30","modified_gmt":"2026-05-01T06:19:30","slug":"brand-recall-protocol","status":"publish","type":"docs","link":"https:\/\/icortex.ai\/help\/automatiza-tu-tienda\/brand-recall\/brand-recall-protocol\/","title":{"rendered":"Brand Recall Protocol"},"content":{"rendered":"\n

The E-commerce environment demands a constant presence. Initial acquisition is only the threshold; maintaining brand awareness is the operational challenge. Proven methodologies exist to ensure your brand remains in the consumer’s mind. This mechanism is called Brand Recall.<\/p>\n\n\n\n

Analyze this critical functionality within the iCortex\u2122 ecosystem. Observe how continuous connection with your Profiles is optimized to ensure maximum brand recall. Efficiency in loyalty is established through precise implementation.<\/p>\n\n\n\n

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

Operational Definition<\/h2>\n\n\n\n

Brand Recall<\/strong> is a strategic utility within the iCortex Engineering Revenue Ecosystem, designed to maintain interaction with established Profiles. Unlike Engagement Flows, which focus on acquisition, Brand Recall focuses on revitalizing the relationship with the consolidated customer base.<\/p>\n\n\n\n

Mechanism of action:<\/strong> It consists of a series of automated orchestrations scheduled periodically to ensure brand persistence. The critical factor lies in creating high-impact communications that incorporate your corporate identity, logo, and relevant AI-generated information. Visibility is maintained without incurring saturation.<\/p>\n\n\n\n

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

Accessing Brand Recall<\/h2>\n\n\n\n

To initiate the implementation of this strategic capability, follow the technical navigation path below:<\/p>\n\n\n\n

    \n
  • In the side menu, access Lifecycles Strategies<\/strong>.<\/li>\n<\/ul>\n\n\n\n
      \n
    • Within the Orchestration submenu, select Brand Recall<\/strong>.<\/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><\/figure>\n\n\n\n
      <\/div>\n\n\n\n
        \n
      • The Brand Recall interface will load. From this location, recall orchestrations are configured efficiently.<\/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><\/figure>\n\n\n\n

        Navigation is complete. Proceed to define your Brand Recall cycles.<\/p>\n\n\n\n

        Configuring Brand Recall Orchestrations<\/h2>\n\n\n\n

        Having understood the purpose and location of Brand Recall, it is time for technical implementation. Review the configuration protocols to design your messages. Remember that each orchestration represents an opportunity to reinforce the relationship with your Profiles. Execute the creation with precision, maintaining brand consistency and delivering strategic value to your contact base.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Brand Recall is a set of automated orchestrations designed to maintain your brand presence before existing Profiles.<\/p>\n","protected":false},"author":6,"featured_media":0,"parent":2166,"menu_order":9,"comment_status":"closed","ping_status":"closed","template":"","doc_tag":[270,179,617,616],"doc_badge":[],"class_list":["post-1544","docs","type-docs","status-publish","hentry","doc_tag-brand","doc_tag-branding","doc_tag-recall","doc_tag-reminder","no-post-thumbnail"],"acf":[],"_links":{"self":[{"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/docs\/1544","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\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/comments?post=1544"}],"version-history":[{"count":15,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/docs\/1544\/revisions"}],"predecessor-version":[{"id":5126,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/docs\/1544\/revisions\/5126"}],"up":[{"embeddable":true,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/docs\/2166"}],"wp:attachment":[{"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/media?parent=1544"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/doc_tag?post=1544"},{"taxonomy":"doc_badge","embeddable":true,"href":"https:\/\/icortex.ai\/help\/wp-json\/wp\/v2\/doc_badge?post=1544"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}