AgentforceIntermediateentitiesslot-fillingscheduling
Implement slot filling and entity extraction for booking flows
Real World Scenario
The agent books service appointments but frequently misrecords dates when users say "next Friday" or "the 12th".
Expected Answer
• Use structured action inputs with required slots: date, time, service type, location
• Normalize relative dates server-side using org timezone and business calendar
• Confirm ambiguous slots explicitly before write actions
• Persist partial slot state across turns in session context
• Validate against resource availability via lookup action before confirmation
• Handle corrections gracefully without restarting entire flow
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Use structured action inputs with required slots: date, time, service type, location Also consider: Normalize relative dates server-side using org timezone and business calendar In practice: Confirm ambiguous slots explicitly before write actions Balance speed of delivery with maintainability.
Architect Perspective
Never trust LLM date parsing alone—always confirm with deterministic Apex date logic.