Salesforce Decode
Salesforcedecode
Back to questions
AgentforceArchitect (Hardest)voicetelephonyservice-cloud-voicelatency

Design voice-enabled Agentforce with telephony integration

Real World Scenario

A healthcare provider wants patients to call IVR and speak naturally with Agentforce for appointment scheduling, with HIPAA constraints on spoken PHI.

Expected Answer

• Integrate Service Cloud Voice or partner telephony with low-latency speech-to-text and text-to-speech pipelines • Design shorter conversational turns—voice users tolerate less verbosity than chat readers • Implement strong caller authentication before discussing PHI; use last-four SSN or patient portal PIN flows • Configure barge-in handling so callers can interrupt prompts naturally • Apply stricter retention policies on voice transcripts and recordings per HIPAA • Plan fallback to human nurses for clinical questions—hard boundary in topic design • Test acoustic edge cases: accents, background noise, and DTMF fallback paths

Follow-Up Questions & Answers

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

Direct answer: Integrate Service Cloud Voice or partner telephony with low-latency speech-to-text and text-to-speech pipelines Also consider: Design shorter conversational turns—voice users tolerate less verbosity than chat readers In practice: Implement strong caller authentication before discussing PHI; use last-four SSN or patient portal PIN flows Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Voice magnifies latency and error costs—a misheard date of birth is worse than a typo in chat. Architect authentication early and keep clinical boundaries explicit in topic design, not buried in prompts.