Conversational Video Capacity Planner

How to use Conversational Video Capacity Planner

Average concurrency can hide a burst that exceeds a real limit. Compare a declared shift scenario with a separate evenly spaced burst before promising session capacity.

1. Enter a checked concurrency limit and measured or explicitly hypothetical fixed session duration.
2. State the offered shift rate, operating hours and a separate burst arrival count/window.
3. Inspect rejected starts and sessions continuing after closing, then validate with actual authorized capacity tests.

Good to know

• Each scenario uses evenly spaced arrivals starting at zero, constant duration and no queue. Busy starts are rejected. Arrival/end ties reuse the freed slot; accepted sessions may finish after the arrival window.
• At most 100,000 shift arrivals, 10,000 burst arrivals and 10,000 concurrent sessions; shift length at most 24 hours. Whole shift arrival count is floored from rate × hours.
• This is not a probabilistic queueing model, measured provider throughput, latency forecast, SLA or guaranteed reservation capacity.
• Each field is limited to 8,000 UTF-16 characters; CSV inputs use the exact displayed header and at most 100 data rows. Quoted commas, doubled quotes and quoted newlines are supported. Empty/duplicate identities, unsupported controls and unpaired surrogates are refused.
• Exports are editable review records. Spreadsheet-like text is apostrophe-prefixed in CSV to reduce formula execution risk; inspect your actual spreadsheet/import settings before sharing.
• Everything runs locally in your browser. No AI model, upload, provider account, calendar, call, video render, automatic outreach, publication or saved input. Enter only information you are authorized to process; declarations remain unverified.