Staging should exercise the intended agent behavior without silently accepting production traffic or changing live customer records. Environment separation needs enforced destinations and credentials, not only a label in the dashboard.
LiveKit documents non-production deployments and custom environment separation. Verify the supported model and installed versions for your project before choosing the boundary. A staging deployment name does not automatically isolate every external service.
Inventory all environment-specific assets
Record project or deployment context, phone entry points, agent selection, secrets, calendars, customer data, notifications, knowledge sources, media storage, and metering treatment. Explicitly document anything shared and its permitted side effects.
Keep production credentials out of ordinary test paths. The backend should derive authorized environment context and validate destinations before consequential operations. A copied prompt or tool schema can otherwise retain live identifiers.
Work through a fictional booking release
An agency tests a new scheduling policy in staging. The call uses controlled identity and a test calendar, and staff alerts reach reviewers. A background retry preserves the original staging context after the call ends.
When the tested package is promoted under the approved process, production mappings are verified separately. The release should identify what changed in code and what changed in local configuration. Passing staging does not prove every production account permission is correct.
| Environment case | Required evidence |
|---|---|
| Staging phone call | Intended test route and agent |
| Remote action | Authorized nonproduction destination |
| Shared provider service | Explicit controlled usage policy |
| Delayed retry | Original environment retained |
| Production promotion | Reviewed package and target mappings |
Account for environmental differences
Idle behavior, capacity, data volume, permissions, and provider entitlements can differ. Record those differences so a rehearsal is interpreted honestly. Do not compare first-call timing across environments without checking their current hosting behavior.
Separate projects can simplify identity and secret boundaries while adding provisioning overhead. Supported non-production deployment features can reduce repeated setup but still require careful external-resource configuration. Select the model the team can test and maintain.
Include negative tests that supply a live destination to a staging action. Review test/live agent separation for asynchronous work and billing paths.
Questions about environment separation
Does staging guarantee no live side effects?
Only the implemented and verified boundaries can establish that. External calendars, messages, and secrets need explicit review.
Can staging use production customer data?
Follow the approved purpose, access, and handling policy; prefer controlled fictional fixtures when they meet the test need.
What should a promotion record contain?
Tested package, configuration versions, target identity, accepted differences, verification evidence, rollback owner, and any controlled production checks still required.