Understanding the Limitation

When teams running Agentforce hit this issue, it is essential to understand the platform-level limitation. The current implementation of Agentforce Voice in SDO does not support connection to providers like Amazon Connect.

The root cause of this issue is the restricted availability of Agentforce Voice in SDO, which is currently limited to the builder and does not extend to provider connections.

Potential Workarounds

Although there is no direct solution to this issue, teams can explore alternative approaches to demonstrate the capability to their clients. This might involve showcasing the feature in a different context or using a separate demo environment.

As the space is rapidly evolving, it is crucial to stay updated on the latest developments. Attending community events and webinars can provide valuable insights into new features and potential workarounds.

Next Steps

Checklist for Implementing Agentforce Voice

• Review the current limitations of Agentforce Voice in SDO
• Explore alternative approaches to demonstrate the feature to clients
• Stay updated on the latest developments and community events
• Consider attending webinars and workshops to learn about new features
• Collaborate with the community to share knowledge and best practices

What is the current status of Agentforce Voice in SDO?

Agentforce Voice is only available in the builder and cannot be connected to providers in SDO.

Are there any workarounds to demonstrate the feature to clients?

Teams can explore alternative approaches, such as showcasing the feature in a different context or using a separate demo environment.

How can I stay updated on the latest developments?

Attend community events, webinars, and workshops to learn about new features and potential workarounds.

Can I connect Amazon Connect to Agentforce Voice in SDO?

No, currently, Agentforce Voice in SDO does not support connection to providers like Amazon Connect.