Salesforce Decode
Salesforcedecode
Back to questions
AgentforceAdvancedproactiveoutboundmessagingorchestration

Design proactive outbound agents for appointment and payment reminders

Real World Scenario

A healthcare network wants agents to proactively remind patients of appointments and collect copay confirmations via SMS. TCPA and HIPAA constraints apply.

Expected Answer

• Verify consent and channel opt-in status via Data Cloud or CRM before any outbound agent message • Use scheduled Flow or Data Cloud activation triggers initiating agent sessions with templated openings • Limit proactive agents to narrow intents—confirm, reschedule, pay—not open-ended support • Implement quiet hours, frequency caps, and stop-keyword handling per regulatory requirements • Log lawful basis and consent snapshot ID with each outbound session for audit • Escalate to human when patient expresses clinical symptoms or billing disputes beyond script • Measure opt-out rate, confirmation completion, and complaint rate separately from inbound containment

Follow-Up Questions & Answers

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

Direct answer: Verify consent and channel opt-in status via Data Cloud or CRM before any outbound agent message Also consider: Use scheduled Flow or Data Cloud activation triggers initiating agent sessions with templated openings In practice: Limit proactive agents to narrow intents—confirm, reschedule, pay—not open-ended support Optimize for scale and operational observability.

Architect Perspective

Proactive agents are campaigns with conversational UI—architect consent, caps, and narrow scope first. Open-ended outbound agents generate regulatory and brand risk fast.