AgentforceIntermediateknowledgechange-managementlaunch
Manage agent knowledge freshness after product launches
Real World Scenario
A product launch changed return policies but the agent still cites old 30-day window for two weeks.
Expected Answer
• Tie knowledge publish workflow to product launch checklist with effective dates
• Use article metadata effective/expiry dates consumed by retrieval filters
• Run pre-launch regression conversations testing new policy utterances
• Temporary topic banner instructing agent to prioritize articles tagged launch-2025
• Monitor post-launch misinformation reports from CS agents
• Automated stale article alerts when products referenced in cases change
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Tie knowledge publish workflow to product launch checklist with effective dates. Use article metadata effective/expiry dates consumed by retrieval filters. Pick based on your integration pattern and team capability. Agents amplify stale content at scale—launch governance must include knowledge, not just code. Balance speed of delivery with maintainability.
Architect Perspective
Agents amplify stale content at scale—launch governance must include knowledge, not just code.