Salesforce Decode
Salesforcedecode
Back to questions
AgentforceArchitect (Hardest)field-serviceschedulingdispatchagent-actions

Orchestrate Field Service dispatch agents with technician scheduling actions

Real World Scenario

A utilities company wants customers to reschedule field appointments via chat agent. Wrong dispatch windows cause truck rolls costing $400 each and SLA penalties.

Expected Answer

• Expose scheduling actions wrapping Field Service appointment APIs with territory and skill constraints • Confirm appointment slots with explicit customer acknowledgment before commit action • Validate service territory, resource availability, and entitlement before showing open windows • Handle emergency vs standard priority with different routing and escalation rules • Sync agent-created appointments to technician mobile apps with push notification triggers • Implement compensating cancel/reschedule actions with audit trail for dispatch center • Measure reschedule success rate, no-show rate, and agent-initiated vs human-initiated changes

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Direct answer: Expose scheduling actions wrapping Field Service appointment APIs with territory and skill constraints Also consider: Confirm appointment slots with explicit customer acknowledgment before commit action In practice: Validate service territory, resource availability, and entitlement before showing open windows Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Field Service agents sit on operational systems with physical world cost. Keep slot presentation deterministic; use the LLM for intent and confirmation, not calendar math.