Capacity for separate conversations
Simultaneous call capacity: check the complete path
For a home-service office, simultaneous call capacity means the number of separate calls a particular setup can sustain at the same time. It is not the number of extensions that ring for one caller, and it is not a monthly allowance of answering minutes. Trace the entire path before relying on a capacity claim: the published number, carrier, phone system, answering destination and any transfer back to your office.
| Layer | Question to resolve | Evidence to keep |
|---|---|---|
| Published number and carrier | How many overlapping inbound calls does this exact service admit? | Product, account scope and carrier confirmation |
| Phone system or trunk | Which channel, session, license or account limit applies? | Current configuration and applicable limits |
| Answering destination | Does a separate simultaneous caller connect, wait, overflow or receive busy? | Provider terms and a controlled observation |
| Transfer back to office | Can another call reach the receiving endpoint while it is occupied? | Transfer type and destination behavior |
| Burst arrival | Is admission limited by call starts per second as well as active calls? | Direction-specific rate limit and allowed test plan |
| Beyond the agreed capacity | What is the next caller's final path? | Queue, rejection or fallback record with owner |
01 / Capacity for separate conversations
Keep three different quantities separate
Concurrent calls are calls overlapping in time. Simultaneous ringing describes attempts to reach several destinations for a single caller. Calls per second, often called CPS, describes how quickly new calls can start or be admitted in a specified direction. A system can have room for ongoing conversations while applying a separate limit to new call attempts.
Twilio's Elastic SIP Trunking documentation illustrates the distinction: it lists concurrent calls separately from origination and termination CPS. Its stated allowances depend on carrier support, and it warns that new accounts without an approved Business Profile have limited concurrency. These are Twilio SIP trunking terms, not a Revo limit or proof that an entire business call path is unlimited.
02 / Capacity for separate conversations
Locate the restriction instead of multiplying plan minutes
Draw one row for each service in the route. Ask whether its limit applies per number, account, trunk, licensed user or answering team. Record direction as well: an inbound call and a transfer that creates an outbound leg may face different controls. If the provider uses channels or sessions, ask how those units relate to a held or transferred call in your configuration.
A monthly minute allowance describes billed usage, not the number of simultaneous conversations your business can receive. Likewise, several purchased numbers do not prove independent capacity if they share an account restriction. Leave an undocumented limit unresolved in the matrix instead of assuming it is absent.
03 / Capacity for separate conversations
Agree a small acceptance sequence before making test calls
Choose the overlap your office needs from its own demand records and obtain the providers' permission for the test method. Use consenting participants, known test numbers and a staff-approved window. Do not flood the production number or discover a limit by repeatedly increasing traffic without authorization.
Keep the first test conversation connected, then place a separate authorized call to the published number. Record whether it connects independently, waits, reaches a fallback or fails. Repeat only up to the agreed scope. Where transfers are part of the required flow, include that leg in the approved test and record whether it changes the experience of another caller. A successful test establishes an observation at that load and time, not an unlimited-capacity guarantee.
04 / Capacity for separate conversations
Accept the overflow outcome as part of capacity
A capacity plan needs an agreed result for the next caller, not only a successful result below the limit. Specify whether that caller waits, hears an announcement, reaches another destination or is rejected. Identify who monitors unanswered requests and who can change the account's capacity when requirements change.
Recheck the matrix after changing the carrier, account, phone system, transfer destination or branch structure. Keep a provider's published limit, the account's configured limit and your observed acceptance result in separate fields. None alone establishes the others. Do not infer Revo concurrency, burst capacity or a service-level guarantee from this guide.
Common questions
Make the next step clear.
Resolve the details that matter to your team and callers.
Does ringing five phones mean we can answer five simultaneous callers?
No. Five destinations can be ringing for one call. Ask separately how many distinct overlapping calls the full setup can admit and handle.
Do more monthly minutes increase simultaneous capacity?
Not necessarily. The minute allowance and concurrency limit measure different things. Obtain the account-specific capacity rule instead of deriving it from a usage plan.
Can an unlimited concurrency statement still have qualifications?
Yes. Twilio's SIP trunking documentation, for example, distinguishes CPS and concurrency and states carrier and new-account qualifications. Read the scope and check every other service in the route.
Sources and current terms
Document concurrent capacity, arrival-rate limits and the overflow outcome across the full route, then verify the agreed operating requirement with an authorized test.
Review Revo’s current features and plans for the workflow your business needs.
Compare plans