Source record · tier 2 current vendor documentation
Contact Center Sandbox
- Publisher
- Cisco Systems (Webex for Developers)
- URL
- https://developer.webex.com/webex-contact-center/docs/sandbox_cc
- Published
- unknown
- Updated
- unknown
- Accessed
- 2026-09-22
- HTTP status
- 200
- License
- (c) Cisco Systems; proprietary vendor documentation; no-redistribution; short excerpts and locators only
Source notes citing this source
- A Webex Contact Center developer sandbox is provisioned with default hold music and a default greeting message as audio files. in context
- The auto-wrap-up desktop profile in a Webex Contact Center developer sandbox ends the call with a default wrap-up code instead of requiring the agent to choose one. in context
- The business hours mapped to the default inbound entry point and default basic flow of a Webex Contact Center developer sandbox are active for 60 days from the time the sandbox is created. in context
- The 60-day default business-hours window of a Webex Contact Center developer sandbox expires before the sandbox itself, so a sandbox can remain valid while its default entry point stops routing on the original schedule. inferred in context
- Cisco recommends the latest desktop version of Google Chrome or Mozilla Firefox for the Webex Contact Center portals and states other browsers may produce unexpected results. in context
- Webex Calling is the default calling platform provisioned in a Webex Contact Center developer sandbox. in context
- No change in Webex Control Hub is required to use a Webex Contact Center developer sandbox, although the administrator account can sign in to Control Hub to customise Contact Center settings and view metrics. in context
- A Webex Contact Center developer sandbox is provisioned with two desktop profiles, one with auto-wrap-up enabled and one without. in context
- A Webex Contact Center developer sandbox organisation is issued a DNS domain under wbx.ai and a Webex site URL under webex.com, both derived from a generated organisation name. in context
- Extending the validity of a Webex Contact Center developer sandbox is done by contacting Webex Developer Support; the documentation names no self-service extension mechanism. in context
- The two Contact Center user accounts in a Webex Contact Center developer sandbox are issued extensions 1001 for the premium agent and 1002 for the supervisor agent. in context
- The default flow in a Webex Contact Center developer sandbox plays the default hold music and redirects the call to the default inbound queue. in context
- Cisco instructs sandbox administrators to sign in to Webex Control Hub at https://admin.webex.com from a fresh private or incognito browser window using the credentials from the provisioning email. in context
- In a Webex Contact Center developer sandbox the main PSTN number, supplied in the provisioning email, is the number dialled to reach an agent signed in to Agent Desktop. in context
- The main PSTN number of a Webex Contact Center developer sandbox is assigned to the default Webex Calling location and is described as reserved. in context
- A Webex Contact Center developer sandbox is provisioned with one default multimedia profile. in context
- Cisco documents no procedure for converting a Webex Contact Center developer sandbox into a production tenant, and no procedure for transferring its licences, PSTN numbers or organisation identity to one. inferred in context
- The Webex Contact Center portals are not designed for mobile devices. in context
- As retrieved on 2026-09-22 the Contact Center Sandbox page documents what a sandbox contains and how to sign in to it but contains no step-by-step procedure for requesting one. in context
- A Webex Contact Center developer sandbox is provisioned with exactly one administrator user. in context
- After a Webex Contact Center developer sandbox is created the requester receives a provisioning email containing the Webex site name, DNS domain, administrator username, administrator password and Webex site URL. in context
- A Contact Center Developer Sandbox gives the requester administrator access to a licensed Webex Contact Center sandbox for creating and testing platform capabilities that are not available with Webex free plans. in context
- A Webex Contact Center developer sandbox is provisioned with one preconfigured inbound voice queue. in context
- Using a Contact Center Developer Sandbox requires first being signed in to the Webex Contact Center Developer Portal, and a new free Webex account can be created for that purpose. in context
- Problems with a Webex Contact Center developer sandbox are raised through the developer portal Support page. in context
- A Webex Contact Center developer sandbox is provisioned with one default agent-based team. in context
- A Webex Contact Center developer sandbox is provisioned with two default Contact Center users: a premium agent with Agent Desktop functions only, and a supervisor with additional supervisory metrics and functions. in context
- A Webex Contact Center developer sandbox is issued two PSTN numbers: a main number assigned to the default Webex Calling location, and an entry point number assigned to the Contact Center default inbound entry point. in context
- A Webex Contact Center developer sandbox is provisioned with five pre-configured user profiles: Administrator Only Profile, Administrator Profile, Premium Agent User Profile, Standard Agent User Profile and Supervisor Profile. in context
- All Webex Contact Center developer sandboxes have a validity period of 180 days. in context
- The documented contents of a Webex Contact Center developer sandbox cover voice only; no digital channel, outbound campaign, workforce optimisation or AI capability is listed as preprovisioned. inferred in context
- In the sandbox, business hours are mapped to the default inbound entry point and the default basic flow, and are active for 60 days from creation. in context
- To request a Webex Contact Center sandbox you must be a member of a Contact Center enabled organization, sign in to your Webex account on the developer portal and click Request a Sandbox. in context
- Contact Center sandbox creation may take up to 24 hours and the requester receives several emails during it. in context
- The final sandbox provisioning email carries the account credentials for the sandbox admin and user accounts. in context
- The sandbox's default basic flow plays default hold music and redirects the call to the default inbound queue. in context
- The sandbox comes with a default agent-based team. in context
- If you already hold any Webex sandboxes you must delete them before you can create a new Contact Center sandbox. in context
- Deleting a Webex sandbox can take up to 15 minutes. in context
- Sandbox agents sign in to Webex Contact Center Desktop at desktop.wxcc-us1.cisco.com using the Extension given for that agent in the provisioning email. in context
- In the sandbox the main PSTN number, given in the provisioning email, is the entry point for reaching an agent signed in to Agent Desktop. in context
- The sandbox comes with one inbound voice queue preconfigured. in context
- The sandbox includes a supervisor agent user with access to additional supervisory metrics and functions. in context
- Webex sandboxes have a validity period of 180 days, and Developer Support can be asked to extend a sandbox's validity. in context
- A sandbox agent needs a machine that runs Webex Contact Center Desktop together with the Webex App or the Webex Calling plug-in for Chrome to act as a virtual call center agent. in context
- Webex Calling is the default calling platform in a Webex Contact Center developer sandbox. in context
Cite this source record
APA
WarmTransfer. (2026, September 22). Contact Center Sandbox. WarmTransfer. https://warmtransfer.net/knowledge/sources/webex-dev-cc-sandbox
BibTeX
@misc{warmtransfer-webex-dev-cc-sandbox,
title = {Contact Center Sandbox},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/webex-dev-cc-sandbox},
note = {Cisco Systems (Webex for Developers), accessed 2026-09-22}
}