How to set up a Genesys Cloud sandbox org for development and testing

Before we can experiment with voice biometrics or any audio-based AI features, we need a proper sandbox environment.

Does Genesys offer a free developer org for testing, or do we have to purchase a separate production license just to have a safe place to experiment with the recording and audio stream APIs?

Genesys does offer a free Developer org through the Developer Center. It comes with limited licenses and a 60-day expiration (renewable).

However, it does NOT include the Bold360/Genesys DX module. If you need to test knowledge base integrations or chatbot handoffs, you will need a separate DX trial license from your account team.

From a change management perspective, having a sandbox is non-negotiable.

We rolled out a major Architect flow update directly to production because we didn’t have a sandbox. The flow had a logic bug that sent 100% of calls to voicemail for 45 minutes. The agent adoption score for that quarter tanked because the floor lost trust in the platform. Always test in a sandbox first.

If you set up a sandbox for SIP trunk testing, keep in mind that the sandbox org will have completely different SIP endpoints.

Your production BYOC trunk is configured with specific SIP registrar FQDNs. The sandbox org will assign different FQDNs. You cannot simply copy the SIP trunk configuration between orgs - you must reconfigure the SBC registration targets.

The network configuration for a sandbox is critical if your agents are remote.

If your production firewall rules only whitelist the GC production TURN/STUN server IPs, the sandbox WebRTC calls will fail because they route through different relay servers. Run a traceroute to your sandbox’s media endpoint to verify the path is open before wasting hours debugging phantom audio issues.