Inbound
Schedules, not a stopped campaign
DNIS, run state, scripts, overflow, schedules, and the pause between calls.
Inbound campaigns ยท practice ยท 12 min full read
The campaign admin tree includes IVR script schedules for autodial and inbound campaigns. The planning topic tells you to set the campaign IVR schedule after the script exists. A schedule swaps treatment by time. Stopping the campaign does not. Stopping it returns busy.
- Prefer a schedule to a stopped campaign
- Keep state running
This lab does not reproduce the schedule dialog field by field. Use the schedule when you need a night path, and confirm the campaign stays running.
The campaign stays running.
Write the night rule
One sentence that forbids stopping the campaign at close of business.
- Name the day script
- Name the night script
- State remains running
The sentence uses the word running.
- When is the schedule set? After scripts exist.
- Nightly stop? Causes busy, not a closed prompt.
- Which types have the schedule topic? Autodial and inbound.
- Campaign state at night? Running, with a different script.
- Planning your implementation. vendor. last checked 2026-10.
- Inbound campaigns. vendor. last checked 2026-10.
- Interactive voice response. wikipedia. last checked 2026-10.
Glossary. Call variable: Reportable only after the edit permission and the reporting flag. Not historical. Call variables for reporting
Sister technologies. CRM SDK. Bring-your-own CRM when no named adapter exists. APIs and SDKs
Config. One sentence that forbids stopping the campaign at close of business.
Troubleshooting. Someone's runbook says to stop Inbound at 18:00. Schedule the closed script and leave the campaign running.
Cross-platform bridge. A mapping to another PBX or contact center is a teaching bridge. It is not an import button.
Future hook. The guide's cloud endpoint stays unset. Confirm before relying on a dated catalog or a case-study number.