telvox

Glossary

The jargon,in plain English.

This industry runs on acronyms, and most of them hide something simple. Here is what 26 of them mean, what each one looks like on a working floor, and in a few cases what a vendor is really promising you when they use the word.

Dialing

How an outbound floor decides who to call, and how fast.

Predictive dialing

Calling more numbers than you have free agents, on the bet that most will not be answered, so an agent is talking again the moment the last call ends.

On the floor

It is the fastest of the four modes and the only one that can get you in trouble, because the bet is sometimes wrong and someone answers with nobody there. Progressive dials one number per free agent, preview shows the agent the record before it dials, and manual is click to call. Most floors run predictive for cold lists and preview for anything that needs preparation.

The four dial modes

Dial ratio

over-dial ratio

How many numbers the system dials for each available agent. A ratio of 1.0 is one call per free agent; 3.0 is three.

On the floor

In TelVox this is a per-campaign dial speed from 1.0 to 5.0 in half steps, and it changes live on a running campaign, so a supervisor can throttle without pausing. Underneath it, a self-tuning loop watches your live answer rate and adjusts tick by tick, with a warm-up cap on cold starts because a campaign with no answer history has nothing to learn from yet.

The pacing valve

Abandoned call

dropped call

A call that a person answered when no agent was free to speak to them. They say hello to silence, and hang up.

On the floor

This is the number regulators care about, and it is the direct cost of dialing aggressively. The FTC treats 3 percent of answered calls as the ceiling. It is worth being precise about the definition: a call nobody picked up is a no-answer, not an abandon. Only the ones where a human answered and got nothing count against you.

Abandon governor

the 3% FTC governor

A control that automatically slows a campaign down when too many of its answered calls are being abandoned, so the rate stays under the legal ceiling without anyone watching it.

On the floor

Ours is mechanical, not advisory. At 3.0 percent it forces the campaign to one call per agent with no over-dial at all. At 2.8 percent it downshifts early, cutting the ratio before the ceiling rather than after. Recovery is deliberately slow: full pacing returns only once the rate holds stable below 2.0 percent, so one quiet minute cannot bounce a campaign back into trouble. It is not a setting an administrator can relax. Dial speed tunes how hard a compliant campaign pushes; the governor decides what compliant means.

Watch the governor work

Answering machine detection

AMD

Working out whether a machine or a person picked up, in the first seconds of a call, and dealing with the machines automatically.

On the floor

Detection is never perfect, and the honest question to ask any vendor is what happens when it is unsure. Ours hangs up confirmed machines with their own outcome before an agent is ever occupied, and routes the uncertain ones to a human, because making an agent hear a voicemail greeting is cheaper than hanging up on a customer.

Disposition

call outcome, wrap-up

The outcome an agent records at the end of a call: sold, callback, not interested, wrong number, and whatever else your process needs.

On the floor

Dispositions are how a floor knows anything, and they are also the first thing to rot, because an agent under pressure will skip them. TelVox makes the outcome mandatory before the next call arrives, which is unpopular for about a week and then becomes the reason your reports are worth reading. Retry rules and lead recycling both key off these values.

Lead recycling

retries, rechurn

Returning a lead that did not connect to the calling queue for another attempt later, instead of retiring it after one try.

On the floor

Recycling is how a list gets worked properly, and also how a company accidentally harasses someone, so the interesting question is never how it retries but what stops it. Ours sets the policy per outcome, each with its own delay and attempt cap, so a busy signal can come back in minutes while a failed call waits longer. Dispositions layer their own rules on top: a fixed delay, a date the agent picks, or leaving the choice to them at wrap-up. It is safe by default, which is the part that matters: a lead whose outcome has no matching rule retires rather than looping forever because nobody wrote a rule for it. Attempt caps are checked twice, when the queue fills and again at the moment of dialing, and there is a global kill switch that stops all recycling at once.

Recycling and retries

Numbers and routing

Which number you call from, who you may call, and where a call lands.

DID

direct inward dialing number

A phone number you own that calls can arrive on, or that you can present as your caller ID when dialing out.

On the floor

In practice a DID is just a number in a pool. A campaign is assigned as many as you like and rotates across them, which protects any single number's reputation with the carriers. If you have ever had a number start showing as spam likely, this is the mechanism that spreads that risk.

Local presence

Showing a caller ID with the same area code as the person you are calling, because people answer local numbers more often than unfamiliar ones.

On the floor

The version that actually matters is the one people forget to ask about: stickiness. TelVox can match the area code, or it can make sure the same lead always sees the same number across every attempt, remembered for 30 days. A prospect who gets three calls from three different numbers learns to ignore all of them.

Do Not Call list

DNC

The record of people who have asked not to be contacted, which you are legally obliged to honour.

On the floor

The trap is timing. Screening at import is not enough, because a list imported on Monday and dialed on Thursday is three days stale. TelVox screens at import and again at the moment of dialing, keeps separate lists at organisation, campaign and list level, and purges queued leads the instant a number is added, so a request made mid-campaign takes effect immediately.

IVR

interactive voice response, the phone menu

The automated menu that answers an inbound call and routes it, the press 1 for sales part.

On the floor

Most IVR pain is a design problem rather than a technology one: menus built by whoever could edit the config, never revisited. Ours is a drag-and-drop builder with thirteen node types, which mainly matters because it means the person who understands the customer journey can change the menu without filing a ticket.

ACD queue

automatic call distribution

The queue an inbound call waits in, and the rules deciding which agent it goes to when one becomes free.

On the floor

The interesting part of a queue is never the happy path, it is what happens when nobody is free. Ours is built to fail politely rather than silently, and one detail is worth knowing: if an agent is offered a call and lets it ring out, the caller is put back with their position preserved. Nobody goes to the back of the line for someone else's missed ring.

Overflow

max wait, queue-full

What happens to a caller who has waited longer than you are willing to make anyone wait, or who arrives when the queue is already full.

On the floor

Every queue needs an answer to this and most inherit a bad one by default, which is why people end up on hold indefinitely. A max-wait threshold sends the caller somewhere else, with an announcement you record for exactly that moment rather than the general hold loop. A separate queue-full cap stops the queue accepting more callers than it could plausibly serve, so the honest outcome, a callback or a voicemail, happens straight away instead of after twenty minutes of hold music.

Inbound queues & IVR

Listen, whisper and barge

The three things a supervisor can do to a call in progress: hear it silently, speak to the agent without the customer hearing, or join the call outright.

On the floor

Whisper is the one that changes how a floor trains. Coaching a new agent through a live call, without the customer knowing anyone else is there, beats reviewing a recording the next day. All three work from the browser in TelVox, so a supervisor does not need to be sitting on the floor.

Live supervision

Voice infrastructure

What actually carries the call, underneath the software.

SIP trunk

The connection that carries calls between your phone system and the outside world, over the internet rather than physical phone lines.

On the floor

The number that matters is concurrency, how many calls it will carry at once, and traditionally resizing one meant a conversation with your carrier and a wait. On TelVox Connect trunks are self-serve: create, configure and resize them from the dashboard or the API, and point your existing carrier or softswitch at us if you would rather keep the contracts you have.

SIP and WebRTC

WebRTC

browser softphone

The technology that lets a browser tab make and receive real phone calls, with no software installed and no desk phone on the desk.

On the floor

For a contact centre this is mostly a procurement story rather than a technical one: no handsets to buy, no VPN for remote agents, and onboarding someone is sending them a link. The trade is that audio quality now depends on the agent's network, which is why TelVox surfaces live call-quality metrics rather than making you guess.

SIP and WebRTC

Pooled minutes

A monthly calling allowance shared across everyone in your organisation, rather than a fixed allowance locked to each individual seat.

On the floor

Pooling matters because floors are uneven. Ten seats with a thousand minutes each, not pooled, means your busiest three agents run out while quiet seats leave minutes unused. Pooled, the same allowance covers the same work. TelVox plans include minutes per seat that pool across the organisation and reset monthly, with overage itemised at your contracted rate rather than calls being cut off.

What plans include

Support and SLAs

The vocabulary of a helpdesk, where the clock is the promise.

SLA clock

A countdown on a support ticket measuring whether you answered and resolved it inside the time you promised.

On the floor

Most helpdesks run two clocks, first response and resolution, which leaves a real gap: a ticket can be answered quickly and then quietly stall for a week. TelVox Desk runs three. The next-response clock resets every time the customer writes back, so a long conversation cannot go quiet without someone noticing. All three respect your business hours and holidays, so a ticket filed at midnight is not already late at breakfast.

How the clocks work

Breach

Missing one of those deadlines.

On the floor

A breach you discover at month end is just paperwork. The useful behaviour is the warning before it: Desk sends a reminder a configurable number of minutes ahead of the deadline, to the assignee or a named list, and escalates on the same terms afterwards. The point is to be told while it can still be fixed.

WhatsApp session window

the 24-hour rule

WhatsApp's rule that a business may only send free-form messages for 24 hours after the customer's last message. Outside that window, only pre-approved template messages are allowed.

On the floor

This catches out every team that starts doing support on WhatsApp, usually as a reply that silently fails to send. Desk tracks the window per conversation and counts it down where the agent can see it, and outside the window it only offers approved templates, so the failure cannot happen quietly.

WhatsApp in Desk

Sticky agent

Routing a returning customer back to the person who dealt with them last time.

On the floor

It is the difference between explaining your problem once and explaining it every time. The cost is load balancing, since a popular agent accumulates returning customers, which is why it works best alongside routing by skill for everything else.

Routing in Desk

Compliance and security

The words that appear on procurement checklists, and what they actually commit a vendor to.

TCPA and the TSR

The two American rules that govern outbound calling: the Telephone Consumer Protection Act, and the FTC's Telemarketing Sales Rule, which is where the 3 percent abandon ceiling comes from.

On the floor

We are not your lawyers and this is not legal advice. What software can honestly promise is that the limits are enforced by the system rather than by someone remembering: abandon rate held mechanically, do-not-call screened at dial time, and calling hours respected in the customer's own time zone rather than yours.

PCI pause

Stopping the call recording while a customer reads out card details, then resuming it, so the card number never exists in your recording archive.

On the floor

The rule this serves is simple: the safest way to hold card data is not to hold it. Recording in TelVox is set per organisation and per campaign as always, on demand, or never, with pause and resume available on any call.

PHI and masking

protected health information

Health information about an identifiable person, which American law treats as a special category. Masking means storing it obscured so it is not readable to everyone with database access.

On the floor

If you run healthcare campaigns, the question to ask is where the data is masked. Masking in the interface but not at rest satisfies a demo and not an auditor.

Security posture

BAA

business associate agreement

The contract a vendor signs when handling health data on your behalf, making them directly accountable under HIPAA rather than leaving the liability entirely with you.

On the floor

This is the cleanest test of whether a vendor's HIPAA claim means anything. A company can describe itself as HIPAA compliant in marketing and decline to sign a BAA, and if they will not sign, the claim is decoration. TelVox signs one on Enterprise agreements.

SOC 2 and ISO 27001

Two independent audits of how a company runs its security. SOC 2 is a report produced by an external auditor; ISO 27001 is a certification against an international standard.

On the floor

The distinction worth insisting on, from us as much as anyone: holding one of these means an auditor has examined you and issued a report. Being built to the standard means the controls are in place but the audit has not concluded. Both are legitimate, they are not the same claim, and a vendor should tell you plainly which one they mean. TelVox is engineered to SOC 2 Type II and ISO 27001, with certification in progress. When that changes, this entry changes.

Where we stand

Illustrative panels · sample values

Still unclear

Ask us about the one that matters to you

If a vendor has told you something that does not match what you read here, bring it to a demo. We would rather argue about the definition than have you find out later.