Add AI Foundataion new business docs

_data/sidebars/pbc_all_sidebar.yml

@@ -5,6 +5,15 @@ entries:
 
       - title: AI Foundation
         url: /docs/pbc/all/ai-foundation/latest/ai-foundation.html
+        nested:
+          - title: AI Conversation History
+            url: /docs/pbc/all/ai-foundation/latest/ai-foundation-conversation-history.html
+          - title: AI Structured Responses
+            url: /docs/pbc/all/ai-foundation/latest/ai-foundation-structured-responses.html
+          - title: AI Tool Support
+            url: /docs/pbc/all/ai-foundation/latest/ai-foundation-tool-support.html
+          - title: AI Workflow Orchestration
+            url: /docs/pbc/all/ai-foundation/latest/ai-foundation-workflow-orchestration.html
 
       - title: Yves
         nested:
@@ -4020,12 +4029,12 @@ entries:
                         url: /docs/pbc/all/service-point-management/unified-commerce/manage-using-glue-api/manage-services/glue-api-retrieve-services.html
                       - title: Update services
                         url: /docs/pbc/all/service-point-management/unified-commerce/manage-using-glue-api/manage-services/glue-api-update-services.html
-              
+
               - title: Tutorials and HowTos
                 nested:
                   - title: "HowTo: Configure shipment types"
                     url: /docs/pbc/all/service-point-management/unified-commerce/tutorials-and-howtos/howto-configure-shipment-types.html
-                    
+
       - title: Shopping List and Wishlist
         url: /docs/pbc/all/shopping-list-and-wishlist/shopping-list-and-wishlist.html
         nested:

docs/pbc/all/ai-foundation/latest/ai-foundation-conversation-history.md

@@ -0,0 +1,233 @@
+---
+title: AI Conversation History
+description: Enable AI to remember context across multiple interactions for seamless, personalized customer experiences
+template: concept-topic-template
+last_updated: Feb 23, 2026
+label: early-access
+related:
+  - title: AI Foundation
+    link: /docs/pbc/all/ai-foundation/latest/ai-foundation.html
+  - title: AI Tool Support
+    link: /docs/pbc/all/ai-foundation/latest/ai-foundation-tool-support.html
+  - title: AI Structured Responses
+    link: /docs/pbc/all/ai-foundation/latest/ai-foundation-structured-responses.html
+  - title: AI Workflow Orchestration
+    link: /docs/pbc/all/ai-foundation/latest/ai-foundation-workflow-orchestration.html
+  - title: Manage conversation history with the AiFoundation module
+    link: /docs/dg/dev/ai/ai-foundation/ai-foundation-conversation-history.html
+
+---
+
+Conversation History enables your AI-powered features to maintain context across multiple customer interactions. Instead of treating each message as isolated, AI can reference previous exchanges, remember customer preferences, and build on earlier parts of the conversation to provide more relevant and personalized responses.
+
+## Business value
+
+### Seamless customer experience
+
+Customers can have natural, flowing conversations without repeating themselves. When a B2B buyer asks "What about the 500mm variant?" the AI knows which product family was discussed earlier and responds appropriately.
+
+### Reduced customer effort
+
+Conversation History eliminates the need for customers to provide the same information multiple times. This is particularly valuable in:
+- Multi-step product selection processes
+- Technical support scenarios requiring troubleshooting
+- Complex B2B procurement workflows
+- Shopping assistance across multiple sessions
+
+### Increased conversion rates
+
+By maintaining context, AI assistants can guide customers through complete purchase journeys without losing momentum. A customer who explores products today can return tomorrow, and the AI remembers their requirements and previous selections.
+
+### Better support efficiency
+
+Customer service interactions become more efficient when AI remembers the full history of a support case. Support agents can pick up where previous conversations left off, and AI can provide relevant suggestions based on the complete interaction history.
+
+---
+
+## When to use Conversation History
+
+Use Conversation History when customer interactions are not single-question scenarios:
+
+### Multi-turn shopping assistance
+
+**Scenario:** A B2B buyer is selecting industrial components that must be compatible with existing equipment.
+
+**Without Conversation History:** Each question starts from zero. The buyer must repeatedly specify equipment model, voltage requirements, and compatibility constraints.
+
+**With Conversation History:** The AI remembers the equipment model from the first question and uses that context for all subsequent recommendations. The buyer can ask "Do you have this in stainless steel?" and the AI knows which product is being discussed.
+
+**Business impact:** Faster product discovery, reduced frustration, higher order completion rates.
+
+### Extended support conversations
+
+**Scenario:** A customer is troubleshooting a technical issue that requires multiple steps.
+
+**Without Conversation History:** Each support message treats the issue as new. The customer must re-explain the problem, repeat what they have tried, and provide context repeatedly.
+
+**With Conversation History:** The AI tracks the complete troubleshooting history. When the customer says "That didn't work either," the AI knows which solutions were already attempted and suggests the next logical step.
+
+**Business impact:** Faster issue resolution, reduced support costs, improved customer satisfaction.
+
+### Cross-session personalization
+
+**Scenario:** A customer explores products during lunch break and returns in the evening to continue shopping.
+
+**Without Conversation History:** The AI treats the evening session as a new customer visit. Previous preferences, viewed products, and discussed requirements are forgotten.
+
+**With Conversation History:** When the customer returns, the AI greets them with context: "Welcome back. Would you like to continue reviewing the power tools we discussed earlier?"
+
+**Business impact:** Improved customer experience, higher likelihood of purchase completion, stronger customer loyalty.
+
+### Back-office workflows
+
+**Scenario:** A merchandising manager is working with AI to enrich product data across multiple sessions throughout the day.
+
+**Without Conversation History:** Each time the manager returns to the task, they must re-establish context and remind the AI of the data quality standards and formatting preferences.
+
+**With Conversation History:** The AI remembers the manager's preferences, the products already processed, and the specific quality standards for this product category.
+
+**Business impact:** Faster content operations, consistent data quality, reduced time spent on context switching.
+
+---
+
+## How it works
+
+Conversation History stores all messages from a conversation in your Spryker database. Each conversation is identified by a unique reference, such as a customer ID, session ID, or support ticket number.
+
+When a customer sends a new message, the AI automatically receives the complete conversation history, enabling contextually relevant responses. The system manages conversation size limits automatically to ensure optimal performance.
+
+### Conversation lifecycle
+
+1. **First interaction:** Customer starts a conversation. AI receives the initial message and creates conversation history.
+
+2. **Subsequent messages:** Customer continues the conversation. AI receives all previous messages as context and responds based on the full conversation.
+
+3. **Return visits:** Customer returns hours or days later. AI retrieves the stored conversation and continues where it left off.
+
+4. **Context window management:** As conversations grow long, the system automatically manages history size to maintain performance while preserving relevant context.
+
+---
+
+## Key capabilities
+
+### Persistent storage
+
+Conversations are stored in your database, not in temporary memory. This means:
+- Conversations survive system restarts
+- Customers can return days or weeks later
+- Support teams can review complete interaction histories
+- Conversations can be exported for analytics and compliance
+
+### Automatic context management
+
+The system handles conversation size automatically:
+- Maintains recent context for optimal AI responses
+- Prunes older messages when approaching model limits
+- Preserves conversation flow without manual intervention
+
+### Cross-channel continuity
+
+Because conversations are identified by business entities, you can maintain context across channels:
+- Customer starts conversation in web storefront
+- Continues via mobile app
+- Completes via customer service chat
+- AI maintains full context throughout
+
+### Privacy and data control
+
+Conversation data is stored in your Spryker database, giving you complete control:
+- Implement data retention policies aligned with GDPR
+- Delete conversations when customers request data removal
+- Audit conversation history for compliance
+
+---
+
+## Business scenarios
+
+### B2B product configuration
+
+**Challenge:** B2B buyers need to find products that meet multiple technical specifications and compatibility requirements. This rarely happens in a single interaction.
+
+**Solution:** AI shopping assistant with Conversation History guides buyers through a multi-step discovery process:
+- Session 1: Buyer describes the application. AI asks clarifying questions about environment and requirements.
+- Session 2: Buyer reviews recommended products and asks about specific variants.
+- Session 3: Buyer requests quote. AI knows exactly which products were discussed and their specifications.
+
+**Result:** Reduced time from inquiry to quote, higher quote accuracy, improved buyer satisfaction.
+
+### Technical customer support
+
+**Challenge:** Technical issues require step-by-step troubleshooting over multiple interactions, often spanning several days.
+
+**Solution:** AI support assistant maintains complete troubleshooting history:
+- Tracks symptoms reported by the customer
+- Remembers diagnostic steps already attempted
+- Knows which solutions did not work
+- Provides progressive support without asking customers to repeat information
+
+**Result:** Faster resolution times, reduced support ticket escalations, better first-contact resolution rates.
+
+### Personalized shopping experiences
+
+**Challenge:** Customers explore products across multiple sessions but lose context when they return.
+
+**Solution:** AI shopping assistant remembers preferences and browsing history:
+- Recalls products the customer viewed or discussed
+- Remembers budget constraints and feature preferences
+- Tracks questions asked and answers provided
+- Continues conversations naturally across sessions
+
+**Result:** Higher conversion rates, increased average order value, improved customer lifetime value.
+
+### Content and catalog management
+
+**Challenge:** Merchandising teams work with AI to enrich product data, but context is lost between work sessions.
+
+**Solution:** AI content assistant maintains workflow state:
+- Remembers which products have been processed
+- Recalls brand voice and content standards discussed
+- Tracks corrections and feedback provided by the team
+- Applies learned preferences to subsequent products
+
+**Result:** Faster content production, consistent quality, reduced time spent on rework.
+
+---
+
+## Comparison to alternatives
+
+### Traditional chatbots
+
+**Traditional approach:** Each interaction is independent. Chatbots follow predefined decision trees and cannot reference previous messages.
+
+**Conversation History:** Maintains full context across unlimited interactions. AI can reference any part of the conversation and build on previous exchanges.
+
+### Session-based chat
+
+**Session-based approach:** Context is maintained only during an active browser session. When the customer closes the browser or switches devices, context is lost.
+
+**Conversation History:** Conversations persist across sessions, devices, and channels. Customers can return days later and continue where they left off.
+
+### Manual context tracking
+
+**Manual approach:** Customer service agents manually read previous tickets and notes to understand history.
+
+**Conversation History:** Complete conversation history is automatically available to both AI and human agents, eliminating manual context gathering.
+
+---
+
+## Privacy and compliance considerations
+
+### GDPR and data rights
+
+Conversation data is personal data under GDPR. Ensure your implementation supports:
+- **Right to access:** Customers can request copies of their conversation history
+- **Right to deletion:** Conversations are deleted when customers request data removal
+- **Data minimization:** Store only conversation data necessary for business purposes
+- **Retention limits:** Implement automatic deletion of old conversations per your data retention policy
+
+### Data residency
+
+Conversation data is stored in your Spryker database. This gives you control over data location:
+- Choose database regions that meet data residency requirements
+- Keep EU customer data in EU-based infrastructure
+- Maintain data sovereignty for regulated industries