Customer support glossary
A customer support glossary defines the operational vocabulary of contact centres — the queues, timings, and outcomes that support leaders report on every week. It covers the core metrics: average handle time, first contact resolution, backlog, abandonment rate, and full resolution time. It also covers the mechanics behind them: routing, escalation, disposition codes, business rules, and ticket deflection. Support operations run on precise numbers, and precise numbers depend on precise definitions. A team that measures handle time with after-contact work and a team that measures it without are not comparing the same thing. Each entry gives a plain-language definition and the terms most often used alongside it.
Abandonment rate
Abandonment rate is the share of customers who leave a queue, chat, or callback line before ever reaching an agent. Contact centres track it alongside wait time because abandonment climbs sharply once queues pass a customer’s patience threshold, making it an early signal that staffing or deflection is not keeping pace with demand.
Agent scorecard
An agent scorecard rates a single customer interaction against fixed criteria. Categories typically include greeting and identity verification, accuracy of the resolution, compliance adherence, tone, and completion of required process steps. Each category carries a weight. Category scores combine into one percentage that feeds coaching sessions and QA reporting, and often rolls up into a team-level customer satisfaction index. Reviewed manually, scorecards cover only a small sample of conversations. OnClarity’s AI Agent QA applies a team’s existing scorecard rubric to every conversation across voice, chat, email, and WhatsApp.
Air-gapped deployment
An air-gapped deployment runs software, including AI models, on infrastructure with no connection to the public internet, so data cannot leave the network boundary. Regulated industries such as banking, insurance, and healthcare request this isolation when compliance rules or internal policy prohibit customer data from touching any external link. The trade-off is that updates and model refreshes must be delivered manually instead of pulled automatically, and integrations with outside systems are constrained. This differs from on-premise or private cloud setups, which may still route traffic through encrypted internet connections for vendor management or updates. A contact center example: a bank running its support assistant entirely inside its own isolated network, so call transcripts never cross an external connection. OnClarity holds SOC 2 Type II certification and is GDPR and HIPAA Ready, with Saudi PDPL alignment, for enterprises evaluating strict deployment requirements.
Audit trail
An audit trail is a chronological, tamper-resistant record of who did what, to which record, and when. A usable trail captures the actor, a timestamp, the action taken, and the before-and-after state of the record. Entries cannot be edited or deleted after the fact. Auditors and regulators rely on this record to verify that controls worked as described and to resolve disputes about a specific decision. In customer service, a QA lead investigating a disputed quality score can pull the full history: the original AI-generated evaluation, the reviewer who adjusted it, the reason given, and the exact time of the change. OnClarity (www.onclarity.com) records every AI and human action in reviewable audit logs, and its Agent QA keeps each score traceable to the transcript moment that produced it, giving teams this record without manual log-keeping.
Average handle time
AHT
Average handle time is the mean time an agent spends on a single contact, including talk or chat time and after-contact work. Because the definition varies between teams, comparisons are only meaningful when both sides confirm whether wrap-up time is included inside the calculation being reported.
Average speed of answer
ASA
Average speed of answer is the average time a contact waits in queue before an agent connects, timed from queue entry to answer and typically excluding IVR navigation. It differs from average wait time, which may include abandoned calls, and from service level, which reports the percentage answered within a target such as the common 80/20 standard. Because ASA is a mean, it can look acceptable while masking a long tail of extreme waits, so pair it with wait-time distribution or service level percentiles for a fuller picture. Example: 500 calls with a combined wait of 4,000 minutes yields an ASA of 8 minutes.
Backlog
Backlog is the set of unresolved tickets carried past their target response window. A growing backlog signals that arrival rate has outpaced capacity, and because ageing tickets attract follow-up contacts, backlog tends to generate additional volume rather than simply waiting quietly to be cleared later.
Business rules
Business rules are the conditions that decide how a contact is prioritised, routed, or escalated. Typical rules combine customer tier, channel, detected intent, and elapsed time to determine where a conversation goes and how quickly it must be answered under the applicable service level agreement.
Call barging
Call barging happens when a supervisor joins a live customer call as an active participant. Both the agent and the customer can hear the supervisor once they join. This differs from listen-only monitoring, where the supervisor stays silent, and from whisper coaching, where only the agent hears the supervisor. In AI-assisted centers, barging can also mean a human stepping into a call that an AI voice agent is handling. For example, a supervisor sees a compliance phrase flagged in real time and joins the call to resolve the issue directly with the customer. Because barging grants access to a live conversation, permissions and logging matter. Teams should record who can barge, when, and why. OnClarity’s AI Agent QA can export QA scoring as part of a full audit trail, which matters for regulated contact centers that need to show reviewers exactly who touched a given call.
Call monitoring
Call monitoring is the practice of reviewing live or recorded customer calls to check quality, compliance, and outcomes. Supervisors can listen in real time, or they can review recordings after the call ends. Traditionally, teams sampled only 5 to 10 percent of calls by hand. That left most conversations unreviewed. AI quality tools change this math. OnClarity’s AI Agent QA scores 100 percent of conversations against a company’s existing evaluation rubric within minutes of call end, instead of waiting days for a supervisor to catch up on a backlog. Recording consent rules vary by US state, and some states require consent from every party on the call, not just one. Recordings are commonly stripped of sensitive data through PII redaction before they are stored, so a reviewer can read a transcript without seeing a customer’s card number or social security number.
Call recording
Call recording is the capture and storage of audio from a customer call. Companies keep recordings for quality monitoring, agent training, dispute resolution, and regulatory compliance. It differs from call transcription, which converts that audio into text. Recordings preserve tone and exact wording. Transcripts make conversations searchable. US consent law varies by state. Some states require only one party’s consent to record. Others require all parties to agree. Retention periods and encryption at rest should match company policy and applicable regulation. Payment calls should pause recording during card capture to keep cardholder data out of storage. When a customer disputes what was agreed on a cancellation call, the stored recording settles the facts. OnClarity’s AI Agent QA scores recorded conversations against existing evaluation rubrics and produces audit-trail exports for compliance review.
Call transcription
Call transcription converts recorded or live call audio into searchable text using automatic speech recognition (ASR). It can run in real time, powering live agent guidance, or in batch after the call ends. Batch processing generally yields higher accuracy. Quality transcripts include speaker diarization, timestamps, and redaction of sensitive data like card numbers. Accuracy is measured by word error rate. OnClarity’s AI Agent QA uses transcripts to score 100% of conversations for QA and compliance. Example: a team searches six months of transcripts for every mention of a failed payment flow to find a root cause.
Caller ID spoofing
Caller ID spoofing happens when a caller fakes the phone number or name shown to the person receiving the call. The call looks like it comes from a different line than its real source. In the United States, the Truth in Caller ID Act bans spoofing meant to defraud or harm someone. The FCC also mandates the STIR/SHAKEN framework, which verifies calls across carrier networks. Spoofing hurts contact centers two ways. Fraudsters copy a brand’s real support number to scam customers. Meanwhile, the brand’s own outbound calls, including calls placed by an AI voice agent, can get flagged as spam. That lowers answer rates and damages customer trust.
Code switching
Code switching happens when a speaker alternates between two or more languages or dialects in one conversation. This can happen between sentences (inter-sentential) or inside a single sentence (intra-sentential). It includes Arabizi, Arabic commonly written using the Latin alphabet in digital messaging. In contact centers, this is routine on WhatsApp and chat across the GCC. A message may open in Gulf Arabic and close with an English product or brand name. Models trained on only one language often misread this mixing. The result is misclassified sentiment and a swollen “unknown topic” bucket. OnClarity’s Arabic-native capability and Agent Assist’s multilingual response drafting are built to handle this blending directly, rather than treating mixed-language messages as noise.
Concurrent calls
Concurrent calls are the number of voice sessions active at the same instant, not the total calls handled in a day. This figure, not average volume, determines how many SIP trunking channels and licensed voice seats a contact center needs. Capacity has to cover peak moments, not typical ones. When active sessions reach the provisioned limit, new callers hit busy signals or route to queue overflow until a line frees up. Example: a utility’s power outage triples concurrent calls for twenty minutes. Capacity has to be sized well above daily average volume to handle that spike.
Contact center
A contact centre is the team and tooling that handle inbound customer contacts across every channel, including voice, chat, email, and social. The term replaced call centre as support expanded beyond telephony, and it covers workforce management, quality assurance, and routing as well as the agents themselves.
Contact center as a service
CCaaS
CCaaS stands for Contact Center as a Service. It is cloud-delivered software for managing customer interactions, and it covers call routing, IVR, omnichannel queues, recording, and reporting. A company buys CCaaS by subscription instead of building and running its own telephony hardware. CCaaS differs from UCaaS, which handles internal employee collaboration like chat and video meetings. It also differs from on-premise platforms, where a company owns and maintains its own infrastructure. Example: a bank migrates its voice and chat queues to a CCaaS platform, then connects AI agents through the vendor’s APIs to automate routine inquiries like balance checks and card replacements. AI vendors typically integrate on top of or alongside CCaaS rather than replacing it. This is one reason CCaaS sits near the center of most contact center AI terms: almost every AI deployment in contact centers has to plug into one.
Cost of inaction
Cost of inaction is the cost of keeping a process unchanged over a set period, often the same 12 months used in a business case. It adds up carried labor cost, overtime, a growing backlog, customer churn, and compliance risk that build while a decision sits. Most business cases show only the cost of a new system. They leave out the cost of doing nothing. That gap makes the status quo look free when it is not. For example, a contact center that delays automation for 12 months while ticket volume keeps growing will carry higher overtime pay, a larger backlog, and measurable churn from slower replies, all before any new spend gets approved. Tools like Voice of Customer from OnClarity can surface the backlog and churn signals that belong in this calculation.
Cost per contact
Cost per contact is total fully loaded contact center operating expense divided by the number of contacts handled in the same period. The figure conventionally includes agent wages and benefits, supervision and QA staffing, telecom, technology and software licensing, and facilities overhead. Contact centers are labor-intensive, so personnel costs make up the bulk of the total and wage rates by geography drive much of the variance between centers. Example: a center spending $420,000 a month to handle 60,000 contacts has a cost per contact of $7.00. MetricNet benchmarking data puts average cost per inbound contact around $4.83, with a median near $3.73.
Cost per resolution
Cost per resolution is total support cost (staff, software, infrastructure) divided by the number of issues fully resolved in a period. It does not count every interaction logged, only the ones that reach a real fix. That sets it apart from cost per contact, which counts every touch, including repeats and transfers, no matter the outcome. Because it rewards first-contact fixes over raw conversation volume, buyers need to agree what counts as “resolved” versus merely contained before they use the metric in a contract. A team using OnClarity’s AI agents to close a billing query in one exchange usually shows a lower cost per resolution than the same query needing two human handoffs and a callback.
Credit-based pricing
Credit-based pricing is a model in which a buyer prepays for a pool of credits, then draws it down as different actions consume different credit amounts. The credit acts as a conversion layer that abstracts away varied unit costs across features. Customers manage one balance instead of several metered line items. Contracts typically define expiry windows, whether unused credits roll over, and terms for topping up before the pool runs out. This differs from usage-based pricing, which bills for consumption after the fact rather than drawing down a prepaid balance. Example: a support team's credits may deplete at different rates across channels such as voice and chat, since each action, like a voice minute handled by an AI voice agent versus a chat reply, can carry a different credit cost. Finance teams tracking burn rate usually want a monthly consumption report broken out by channel.
Data processing agreement
DPA
A data processing agreement (DPA) is the contract between a data controller and a data processor that sets out how personal data will be handled on the controller's behalf. It is required under GDPR Article 28 whenever processing is outsourced. Standard clauses cover subprocessor approval, security measures, breach notification timelines, deletion or return of data at contract end, and audit rights. Example: a bank signs a DPA before routing customer chat transcripts to a CX vendor for analysis. OnClarity is SOC 2 Type II certified, GDPR and HIPAA Ready, and aligned with Saudi PDPL, which are the facts a DPA review typically asks a vendor to confirm.
Data residency
Data residency is the requirement that customer data be stored and processed inside a specific country or region. Regulated industries and public-sector buyers frequently mandate it, which makes deployment location a procurement question rather than a technical detail for any support platform handling personal data.
Data retention policy
A data retention policy is the documented set of rules governing how long each category of data is kept, where it is stored, and how it is deleted or anonymised once that period ends. It rests on purpose limitation: data should be retained only as long as the original business or legal purpose requires, not indefinitely. Legal holds can pause scheduled deletion during litigation or investigation. Retention is distinct from backup cycles, which preserve copies for disaster recovery rather than active use. In customer service, a contact centre might delete raw call recordings after a set period while retaining anonymised QA scores for long-term trend reporting. See data residency for where that retained data is stored.
Data sovereignty
Data sovereignty is the principle that data is subject to the laws of the country where it is stored or processed. A foreign government may be able to compel access to that data regardless of who owns it. Data sovereignty differs from data residency, which only addresses where data physically sits. It also differs from data localization, which is a legal mandate requiring data to stay within a country’s borders. Example: a Saudi bank may require in-country processing to meet PDPL expectations. Storage location alone would not resolve which jurisdiction’s laws actually govern that data, so residency and sovereignty have to be considered together. OnClarity operates under SOC 2 Type II controls. OnClarity is also GDPR and HIPAA Ready, and it aligns with Saudi PDPL. OnClarity offers in-country data residency options for enterprises that need processing to stay within a specific legal jurisdiction.
Deflection
Deflection is steering a contact toward a self-service or automated resolution before it reaches an agent queue. Effective deflection resolves the underlying question; unsuccessful deflection merely delays the contact, so teams measure it by whether the customer returns rather than by how many contacts were diverted.
Disposition code
A disposition code is the label an agent or AI applies to a closed contact to describe what actually happened. Disposition data drives volume reporting and root-cause analysis, so inconsistent or overly broad codes quietly destroy a support team’s ability to explain why contacts arrive at all.
Enterprise license agreement
ELA
An enterprise license agreement (ELA) is a negotiated, usually multi-year contract covering an organization's use of a vendor's software across the whole company, rather than separate purchases by individual teams. It typically sets a term length, an entitlement or volume commitment (users, devices, or locations), the business entities covered, and support terms. Most ELAs include an annual review comparing actual use against the committed entitlement. Growth within that review is handled through a true-up, and usage above contracted limits is billed as overage charges. Example: a telecom signs a three-year ELA covering voice and chat automation for every regional support team under one contract instead of separate regional deals.
Escalation
Escalation is moving a contact to a more senior agent, a specialist team, or a human when automation stalls. Escalation paths are defined by business rules, and the rate at which contacts escalate is a direct measure of whether the first line is equipped to resolve them.
Escalation rate
Escalation rate is the share of contacts transferred to a higher support tier, a supervisor, or from an AI agent to a human. Reporting should separate planned handoffs, where an AI agent routes a complex or high-risk case by design, from failure escalations, where the agent could not resolve the issue; blending the two obscures true automation performance. Escalation reason codes point to specific knowledge base gaps, and the metric moves inversely with containment and first contact resolution. Example: 120 escalations from 3,000 contacts gives a 4% rate.
Failover
Failover is the automatic switch from a primary system, carrier, or data center to a standby one when the primary fails. Calls keep connecting without manual intervention. Active-active setups run multiple systems simultaneously, so traffic shifts instantly. Active-passive keeps a standby idle until the primary goes down, which takes longer to engage. Planning relies on two metrics: Recovery Time Objective (RTO), how fast service must resume, and Recovery Point Objective (RPO), how much data loss is tolerable. At the carrier level, failover reroutes inbound calls to a secondary SIP trunk or region. Example: a data center outage hits, and calls automatically reroute to a second region. Customers already in queue stay on the line instead of waiting for an engineer to trigger a manual disaster-recovery process.
Fair usage policy
A fair usage policy is the contractual clause that caps consumption under an otherwise "unlimited" or generously bundled plan. It defines what counts as excess and what the vendor may do once a customer crosses it: throttle performance, apply overage charges, or trigger a renegotiation of the contract. Vague language such as "reasonable use" leaves enforcement to the vendor's discretion. Buyers should insist the threshold be written as a specific number, not a general principle. Example: an "unlimited seats" support plan that caps each seat at a fixed number of conversations per month, with defined pricing or escalation once that ceiling is reached. Asking for the exact cap in writing before signing avoids a dispute later over what "fair" actually meant.
First contact resolution
FCR
First contact resolution is the share of issues fully resolved during a customer’s first interaction, with no follow-up contact about the same problem. It correlates strongly with satisfaction and cost, but only when measured over a defined reopen window rather than at ticket close.
Full resolution time
Full resolution time is the total elapsed time from a customer’s first message to a confirmed resolution, including waiting, escalation, and overnight gaps. Unlike response time, it reflects the experience of waiting for an answer rather than the speed of the first reply alone.
Hold time
Hold time is the duration a customer spends on hold after an agent has answered the call, typically while the agent researches an account, consults a colleague, or prepares a transfer. It is distinct from queue wait time, which happens before the call connects to an agent. Hold time is one part of average handle time, alongside talk time and after-call work. Teams usually report it as average hold time per call or total hold time across a contact. Frequent or lengthy holds are associated with lower satisfaction scores, since repeated waiting adds perceived effort even when the issue gets resolved, and repeated holds can drag down a whole customer satisfaction index.
Hybrid support model
A hybrid support model has AI handling routine, high-volume contacts while human agents own complex, sensitive, or high-value interactions. The design question is not what the technology can handle but where the cost of an error is high enough to justify keeping a person in the conversation.
Interactive voice response
IVR
IVR is an automated telephony system that plays recorded or synthesized prompts and routes callers based on their input. Touch-tone (DTMF) menus require keypad presses. Directed dialogue lets callers speak from a limited list of options. Natural language or conversational IVR interprets open-ended speech to identify intent. Success is typically measured by containment rate: the share of calls resolved without a human agent. Deep menu trees are a common source of customer friction, causing repeat prompts and abandoned calls. OnClarity’s AI agents work across chat and voice, handling voice interactions conversationally.
Knowledge base
A knowledge base is the maintained source of truth that AI agents and human agents both answer from. Its accuracy sets a ceiling on the quality of every automated answer, which makes knowledge maintenance an operational requirement rather than a documentation project owned by nobody in particular.
Knowledge gap
A knowledge gap is a recurring customer question the knowledge base cannot answer, usually visible as repeat escalations or low-confidence fallbacks on the same intent. Systematically closing gaps is the highest-return maintenance activity available to any team running automated support at scale.
Live chat
Live chat is real-time text support delivered in-product or on-site, fronted by a human agent, an AI agent, or both in sequence. Its defining constraint is synchrony: the customer is waiting, so response latency and handoff quality matter more than in asynchronous channels.
Macro
A macro is a saved reply or action set that agents apply to a common case, inserting standard wording and performing routine updates in one step. Macros reduce handle time and variation, but stale macros are a frequent source of incorrect policy reaching customers at scale.
Maker-checker
Maker-checker, also known as the four-eyes principle, is a control requiring that one person create or change a record (the maker) and a different person review and approve it (the checker) before it takes effect. The principle comes from banking operations. It enforces segregation of duties so no single individual can both initiate and authorize an action. This reduces error and fraud risk without slowing down routine, low-value transactions. In customer service, a common application is refund approval: an agent issues a goodwill credit, but any amount above a set threshold requires a supervisor's sign-off before it is processed. The same pattern applies to policy changes, bulk data exports, and configuration updates in a support platform.
Multi-tenancy
Multi-tenancy is a software architecture where one application instance serves multiple customer organizations, called tenants. Logical controls keep each tenant’s data separate even though the underlying infrastructure is shared. Isolation models vary. Some platforms use a shared database with tenant ID columns distinguishing each customer’s records. Others use separate schemas per tenant. The strongest option is a fully dedicated instance per customer. Shared infrastructure is what keeps cloud contact center pricing low. Dedicated or on-premise deployment is the usual alternative for regulated buyers who need stronger separation between their data and everyone else’s. A procurement team evaluating an AI vendor should ask directly whether conversation data shares storage with other customers, and how encryption keys are separated between tenants. Both answers affect data sovereignty and audit requirements, so they are worth writing into a contract, not just a sales conversation.
Multilingual support
Multilingual support means serving customers in their own language, including handling Arabic and English side by side within a single operation. Beyond translation it requires language-aware routing, quality scoring in each language, and knowledge content that is maintained rather than machine-translated once and forgotten.
Occupancy rate
Occupancy rate is the portion of an agent’s logged-in time spent actively handling contacts rather than waiting for them. Sustained high occupancy predicts burnout and attrition, so workforce planners treat it as a health measure rather than a productivity target to be maximised.
Omnichannel
Omnichannel describes one continuous conversation and history across chat, email, voice, and social, so a customer who switches channel does not have to restart. The distinction from multichannel is continuity: offering many channels is not omnichannel unless context follows the customer between them.
On-premise
On premise means software runs on servers the customer owns or controls, inside their own data center or private cloud, instead of the vendor’s environment. In an AI contact center, on-premise deployment gives regulated operators direct control over where conversation data is processed and stored. This matters when telephony investments, internal audit rules, or sector regulation make external hosting difficult to justify. Example: a utility keeps call recordings inside its own network, while the AI model itself runs in an isolated environment the utility controls directly. The trade-off is real. The customer takes on hardware cost, patching and upgrade cycles, and the engineering staff needed to run the stack. The vendor no longer carries that work. Many enterprises land on a hybrid model instead. They pair on-premise components with private cloud for everything that does not require strict data isolation, which keeps costs lower than a fully on-premise build.
Operational reporting
Operational reporting is the daily or intraday reporting that supervisors and team leads use to run contact center operations, covering queue volumes, staffing levels, handle time, and individual or team performance at a granular level. It differs from executive reporting in cadence, audience, and detail. Executive reporting rolls up trends for leadership on a weekly or monthly cycle, while operational reporting refreshes continuously for frontline managers making same-shift decisions. For example, a supervisor might check hourly queue depth and agent adherence to decide whether to pull staff off email to cover a chat backlog. OnClarity's AI Agent QA adds granular quality data to this layer, scoring conversations shortly after they end so supervisors can act on coaching and compliance issues the same day rather than waiting for a periodic review.
Outcome-based pricing
Outcome-based pricing charges a customer only when a defined business result happens, not for seats provisioned or volume consumed. Common outcome units in support operations include a resolved ticket, a contained contact, or an avoided escalation. Because payment depends on the result, contracts need clear rules for measurement, attribution, and audit set in advance. Vendor and customer can define “resolved” differently, which creates dispute risk without agreed evidence. For an AI support agent handling full resolutions on its own, a company might pay per ticket resolved end-to-end, with AI QA scoring giving the audit trail that backs each outcome. This differs from usage-based pricing, which scales with activity no matter the result, and from per-seat pricing, which charges a fixed fee per licensed user no matter what gets delivered.
Overage charges
Overage charges are fees billed when actual usage exceeds the volume included in a software contract, typically at a per-unit rate set in the agreement and applied in the billing period the excess occurs. In contact center and CX platforms, common metered units include conversations, voice minutes, agent seats, and API calls. Overage charges differ from a true-up: an overage bills the excess directly, while a true-up adjusts entitlements going forward instead of charging per unit after the fact. Buyers often negotiate a usage buffer or a capped overage rate to avoid list-price surprises at renewal time. Example: a retailer's conversation volume exceeds its contracted tier during a holiday sales peak, triggering overage fees for that month. See true-up and usage-based pricing for related billing mechanics.
Payback period
Payback period is the time, usually stated in months, needed for cumulative savings or benefits from an investment to equal its cumulative cost. The basic calculation divides total investment by average monthly benefit. Uneven savings need a month-by-month add-up until benefits offset the outlay. This simple version ignores the time value of money, unlike net present value or internal rate of return, which discount future cash flows. CX business cases should state whether the AI payback period clock starts at contract signature, at go-live, or once adoption targets are met, since each start point gives a different result. For an AI support agent deployment, payback period arrives when the value of deflected contact volume (fewer agent hours, lower cost per resolution) equals the combined license and implementation cost.
Peak volume
Peak volume is the highest-contact period a staffing plan has to absorb, whether a daily rush hour, a seasonal spike, or an incident-driven surge. Because peaks drive headcount decisions, automation is usually justified on peak absorption rather than on average daily contact volume.
Per-seat pricing
Per-seat pricing charges a fixed fee per named or concurrent user over a billing period, no matter how much that user does. Named-seat licensing assigns access to one specific person. Concurrent licensing caps how many people can log in at once, a limit teams sometimes share across shifts. Its main appeal is budget predictability: finance can forecast cost from headcount alone, which keeps procurement simple. The friction shows up with AI software like Agent Assist or an omnichannel inbox, where agents resolve conversations without ever occupying a seat. Per-seat pricing can undercharge for AI-driven work, or push teams to ration logins during a seasonal peak, only to true up seat counts after volume drops. See usage-based pricing and outcome-based pricing for models built around actual work performed.
Perpetual license
A perpetual license is a one-time software purchase that grants indefinite rights to use a specific version. Updates and support are typically sold separately, under an annual maintenance contract. It differs from subscription or term licensing, where access stops once payments stop. CX buyers weigh a higher upfront cost against predictable long-run spend. They should also check who hosts the platform, and whether newer AI model versions are included or billed separately. Example: a bank with strict KSA/GCC data residency requirements chooses a perpetual, self-hosted deployment to keep customer data within approved borders.
PII redaction
PII redaction is the automatic removal of personally identifiable information from transcripts, logs, and training samples. It lets support conversations be analysed, stored, and used to improve models without carrying customer identifiers into systems that were never scoped to hold them.
Platform fee
A platform fee is the fixed, recurring charge a vendor bills for access to the core software environment, separate from usage-based charges and per-seat licences. It typically covers the hosting environment, core modules, standard support, and standard integrations. It usually excludes overage charges, premium support tiers, and professional services such as implementation or custom configuration. Buyers should ask vendors exactly which modules, support levels, and integrations sit inside the platform fee versus which are billed separately, since the label varies by vendor and bundling differs widely across contracts. A contact centre might pay a flat monthly platform fee for its ticketing and routing environment, then pay variable charges on top based on conversation volume or resolved cases. Reading the fee schedule line by line before signing avoids surprise invoices later.
QA calibration
QA calibration is a recurring exercise in which multiple evaluators independently score the same customer interaction against the same agent scorecard, then compare results and reconcile any gaps. Sessions typically run on a regular cadence to catch rubric ambiguity before it spreads and to keep evaluators aligned as scorecards evolve. Success gets measured by inter-rater reliability: how closely scores converge across reviewers. Calibration is necessary because manual QA relies on small, sampled reviews, where individual judgment drifts over time and across reviewers. Applying one rubric automatically across every conversation, as OnClarity’s AI Agent QA does, removes evaluator-to-evaluator drift by design.
QA coverage
QA
QA coverage is the percentage of customer service conversations reviewed and scored against a quality rubric. It measures how much of an operation’s actual customer interaction volume actually gets evaluated. Manual QA programs typically sample only a small slice of contacts. Industry data puts the standard at 2 to 5 calls per agent per month, often a low single-digit percentage of total volume. Everything outside that sample is a blind spot, where compliance breaches, coaching opportunities, and recurring issues go undetected. OnClarity’s AI Quality Agent scores 100% of conversations within about five minutes of call end, roughly 20 times typical manual coverage. That shift turns QA from a sampling problem into a question of rubric consistency and audit-trail completeness.
Quality assurance
QA
Quality assurance is the structured review of conversations against a scorecard, applied to human agents and AI agents alike. Traditional QA samples a handful of conversations per agent each month; automated QA scores every conversation, which changes the exercise from spot-checking into actual measurement.
Quality assurance score
QA
A quality assurance score is the rating a customer service conversation receives after evaluation against a defined rubric, typically covering accuracy of information, process and compliance adherence, and communication quality such as tone, empathy and clarity. A simple rubric might weight ten criteria at 10 points each, with a call losing points for a missed disclosure or an inaccurate answer to land at 82/100. The score is only as reliable as the rubric’s clarity and the sample size behind it: manual QA programs conventionally review roughly 5 to 10% of conversations, so most interactions never get scored. OnClarity’s Agent QA scores 100% of conversations within five minutes, cutting QA operations cost by roughly 70%, and keeps scoring criteria visible so teams can calibrate evaluators against each other.
Queue
A queue is the ordered set of contacts waiting to be handled, usually segmented by channel, language, skill, or customer tier. Queue design determines who waits and for how long, making it one of the most consequential and least visible decisions in a support operation.
Resolution rate
Resolution rate is the share of contacts closed with the customer’s issue actually solved, as distinct from contacts merely closed. The gap between the two is where reopened tickets and repeat contacts live, so the measure is only trustworthy when reopens are tracked against it.
Response time
Response time is how long a customer waits for a reply once they have made contact. Teams report it as a first-response figure and as an average across subsequent replies, because a fast opening reply followed by long silences produces a poor experience despite good headline numbers.
Role-based access control
RBAC
Role-based access control (RBAC) is an access model where permissions attach to defined roles rather than to individual users. Users inherit access by being assigned to a role. This keeps permissions aligned with job function and supports the principle of least privilege: each role grants only what it needs, no more. Poorly maintained RBAC systems often accumulate overlapping or redundant roles faster than anyone prunes them, a pattern sometimes called role explosion. Role definitions need regular review alongside joiner-mover-leaver changes as staff join, switch teams, or exit. In customer service, RBAC lets a QA reviewer read every conversation transcript for evaluation while a frontline agent sees only the tickets in their own queue. A well-scoped RBAC setup also limits the blast radius if one account is compromised, since that account only ever had access to its own role's data.
Round robin routing
Round robin routing assigns each incoming ticket, chat, or call to the next agent in a fixed, repeating sequence, cycling back to the first agent once everyone has received one. It guarantees an even count of assignments but ignores ticket complexity, agent availability, and language or product skill. Workload can still land unevenly even when the numbers look balanced on paper. In a 12-agent queue, one agent might receive three multi-part complaints in a row purely by rotation order, while a colleague handles three quick password resets in the same stretch. Teams often layer smarter logic on top of this baseline, balancing by current workload or skill rather than relying on rotation alone. That approach sits closer to skills-based routing or load-balanced assignment than to pure round robin.
Routing
Routing is deciding which agent, team, or AI agent receives a contact, based on intent, language, skill, customer tier, and availability. Accurate routing is the cheapest available reduction in handle time, because a misrouted contact pays the cost of being read and reassigned twice.
Schedule adherence
Schedule adherence is the percentage of scheduled time an agent is available and performing the specific activity planned for that interval, such as taking calls when calls are scheduled or being on break when a break is scheduled. Most contact centers target 85 to 95% adherence, per industry benchmarks, with schedules built to allow for shrinkage from training, meetings, and absences. Example: an agent scheduled for 480 minutes who logs 456 minutes matching the schedule scores 95% adherence.
Script adherence
Script adherence measures how closely an agent follows the required dialogue and process steps for a given contact type, scored against a quality assurance rubric. Typical components include identity verification, mandatory disclosures, and required closing language that a compliance team has signed off on. Some steps are compliance-critical, where a miss creates regulatory exposure, such as a call where an agent skips a required recording or consent disclosure. Others are soft guidance intended to support consistency rather than legal requirements. OnClarity's AI Agent QA scores conversations against a company's existing rubric, checking adherence across every contact rather than a small manual sample, which makes script adherence one of the more common contact centre QA terms teams ask about during evaluation. See also call monitoring.
Self-service
Self-service is help a customer can complete without contacting support at all, such as a help centre article, an account action, or a guided flow. Its success is measured by task completion rather than page views, since a read article that fails to resolve still generates a contact.
Service level
Service level is the percentage of contacts answered within a set time threshold, written as two numbers such as 80/20: 80% of calls answered within 20 seconds. The threshold is a business decision rather than a fixed standard, and while 80/20 is the most commonly cited target, its origin is debated and it lacks rigorous research backing. Staffing to hit a target service level typically relies on the Erlang C queuing formula, and service level moves together with abandonment rate, since more callers hang up as wait times grow. Example: if 850 of 1,000 calls are answered within 20 seconds, service level is 85%.
Service level agreement
SLA
A service level agreement sets the committed response and resolution targets for a customer, tier, or contract, often with financial penalties attached. Support operations design queues, routing, and escalation around SLA thresholds, which makes the agreement a structural constraint rather than a reporting line.
Session border controller
SBC
A session border controller (SBC) sits at the edge of a VoIP network, between a contact center’s call infrastructure and its carriers’ SIP trunking connections. It secures, normalizes, and polices SIP signaling and media as calls cross that boundary. Core jobs include SIP interworking, which resolves header and dialect mismatches between carrier and PBX implementations, media transcoding between incompatible codecs, NAT traversal, topology hiding, which masks internal network details from outside parties, and blocking denial-of-service attacks and toll fraud. Example: a contact center adds a second carrier that only supports a different codec than its existing voice platform. The SBC transcodes between the two in real time, so calls connect without requiring either side to change its setup.
Shrinkage
Shrinkage is the share of paid agent time unavailable for handling contacts, covering breaks, training, meetings, absence, and system downtime. Workforce plans that ignore shrinkage systematically understaff, because scheduled headcount and available headcount differ by a predictable and often substantial margin.
SIP trunking
SIP trunking, short for Session Initiation Protocol trunking, carries voice calls over an IP network between a contact center platform and a telephony provider. It replaces physical PRI or analog phone lines with a virtual connection, sized by concurrent call capacity and codec choice. For an AI voice agent, the trunk is where audio enters and leaves the system. Codec quality, jitter, and capacity limits all directly affect how natural the agent sounds and how quickly it responds. Trunk health ties directly to latency, since a congested trunk adds delay before the agent even starts processing audio. Example: provisioning a dedicated test trunk and phone number lets a team run a proof of concept with OnClarity’s AI agents answering live calls, before wider rollout across the rest of the queue.
Skills-based routing
Skills-based routing assigns each contact to the agent best matched to it, by language, product line, account tier, certification, or proficiency score, rather than the next available agent. It applies across voice, chat, email, and WhatsApp. It typically runs on top of standard routing logic inside a unified queue such as OnClarity’s omnichannel inbox. Tighter matching improves resolution quality, but it can lengthen wait times if few agents hold the required skill. Example: an Arabic-language mortgage question is routed to a licensed mortgage specialist instead of a generalist support agent.
Status quo bias
Status quo bias, defined by Samuelson and Zeckhauser in their 1988 study of decision-making, is the tendency to prefer the current state of affairs and to weigh potential losses from changing it more heavily than equivalent potential gains. The mechanism behind it is loss aversion: a possible downside from switching feels bigger than a matching upside from staying put. In AI buying decisions, this shows up as a stalled evaluation defended with “the current process works,” even when support backlogs or missed tickets say otherwise. Quantifying the cost of inaction counters this bias by making the price of delay as visible as the price of change.
Ticket
A ticket is the record of a single customer issue and everything done about it, including messages, internal notes, actions taken, and final disposition. The ticket is the unit most support reporting counts, which is why inconsistent ticket creation quietly distorts every downstream volume metric.
Ticket routing
Ticket routing is the set of rules and models that decide which queue, team, or agent should receive an incoming request, and where it lands in the priority order. Decisions typically draw on channel, classified intent, language, account tier, and the applicable SLA clock. OnClarity's omnichannel inbox applies automated routing across channels, and its AI agents hand conversations they can't resolve to a human with full context. For example, a payment failure reported by an enterprise account can route directly to a specialist queue with a tightened SLA, rather than sitting in the general inbox behind simpler requests. Routing quality is only as good as the classification feeding it: misread intent sends tickets to the wrong place regardless of how well the rules themselves are built. See also routing and skills-based routing.
Time to first response
Time to first response is how long a customer waits before any human or AI reply arrives. It is the most visible service measure to the customer and the easiest to improve with automation, which is why it should always be read alongside resolution quality.
Total cost of ownership
TCO
Total cost of ownership (TCO) is the full cost of acquiring, running, and eventually replacing a system over a set multi-year period, not just its subscription or usage fee. For an AI deployment, TCO includes license or usage fees, implementation, integration with existing systems, data preparation, staff training, ongoing admin time, change management, and exit or migration costs. Buyers routinely leave out several of these lines when they compare vendors, which makes license price alone a misleading basis for a decision. Consolidation is a practical TCO lever. Replacing separate ticketing, chat, chatbot, and voice tools with one platform, such as an AI support agent running across an omnichannel inbox, removes duplicate integration work, duplicate admin overhead, and duplicate training cycles. A contact center comparing five point tools against one consolidated platform over a multi-year period should weigh total cost of ownership across all these categories, not just each tool’s sticker price. The cheaper-looking option on paper can cost more once implementation, integration, and admin time get added in.
Transfer rate
Transfer rate is the percentage of contacts moved from the first agent or queue to another agent, team, or queue before resolution. A warm transfer includes context passed directly between agents; a cold transfer drops the customer into a new queue with no handoff, often forcing them to repeat information. Elevated transfer rates usually signal routing misconfiguration, gaps in skill-based mapping, or missing knowledge access rather than individual agent fault. Each transfer represents an unresolved first contact, so transfer rate moves inversely with first contact resolution and inflates average handle time across the interaction chain. Example: 80 transfers out of 1,000 calls yields an 8% transfer rate.
Triage
Triage is sorting incoming contacts by intent, urgency, and value before they are worked, so the most consequential conversations reach the right place first. Automated triage now performs the classification step, leaving prioritisation rules and exception handling as the main human contribution.
True-up
A true-up is a scheduled reconciliation, built into most enterprise license agreements, in which the buyer reports actual usage against contracted entitlements and pays for any growth since the last check-in, typically on an annual cycle within a multi-year term. The customer initiates it, not the vendor, which is what separates a true-up from an audit. Rather than simply billing an excess, a true-up raises the entitlement count going forward, at rates set when the contract was signed. A contact center licensed for 400 seats that ends the year at 520 would true up the additional 120 seats, adding them to the contracted baseline rather than paying an open-ended overage charge indefinitely.
Unified inbox
A unified inbox is one workspace where conversations from every channel land, so agents work a single prioritised list instead of switching between tools. It reduces context-switching cost and makes cross-channel history visible at the moment an agent is drafting a reply.
Usage-based pricing
Usage-based pricing charges customers for measured consumption of a value metric, such as conversations, minutes, messages, or tokens, rather than a flat per-seat fee. Contracts for tools like an AI support agent or AI voice agent usually combine a committed minimum volume with an overage rate for consumption above that threshold. Some agreements let unused volume roll over. Because support volume can spike sharply (a product recall driving a sudden surge in chat volume, for example), usage-based pricing shifts budget volatility onto the buyer. It differs from outcome-based pricing, which charges only for successfully resolved contacts. Buyers should check overage rates, rollover terms, and true-up timing before they sign.
Warm transfer
A warm transfer connects a customer to another agent or team only after the receiving party has been briefed on who the customer is and what they need. The customer never has to repeat themselves. This contrasts with a cold or blind transfer, where the call is passed along with no introduction, and the next agent has to start from zero. Example: in an AI voice deployment, a warm transfer means a mortgage query is handed to a human specialist along with the customer’s verified identity, an intent summary, and the full transcript so far. The trade-off is brief. Two agents are occupied during the handoff instead of one, but that small cost is offset by fewer repeat-explanation complaints from customers. See also routing and triage, two related terms already defined on the OnClarity glossary.
White label
White label describes a product built by one vendor and sold or deployed under another company’s brand. The originating vendor stays unnamed to end users. In CX, this shows up three ways: a BPO presents analytics as its own service, a platform embeds an analytics layer into its product, or a partner resells software under its own name. Buyers should confirm branding scope (UI, emails, domains), tenant data separation, support ownership, and who carries contractual liability. Example: an outsourcer issues auto-QA scorecards and audit-trail exports to a client under its own brand, with the underlying provider unnamed.
Workforce management
WFM
Workforce Management, or WFM, is the discipline of forecasting contact volume, calculating staffing requirements, building schedules, and tracking adherence and shrinkage. The goal is simple: have the right number of agents available for predicted demand. WFM is narrower than workforce engagement management, which also covers quality scoring, coaching, and performance management. When an AI agent resolves routine contacts on its own, forecasts must split deflected volume from escalated volume, since escalations tend to run longer and more complex than average. Example: once automation clears most password resets, the remaining queue holds fewer calls, but harder ones. Planners raise their average handle time assumptions, even as overall ticket volume drops, and reset staffing levels instead of reusing last quarter’s model unchanged.
Wrap-up time
Wrap-up time is the after-contact work an agent performs before taking the next conversation, including notes, disposition coding, and system updates. It is frequently excluded from handle time reporting, which is the most common reason two teams’ average handle time figures cannot be compared.
Browse other categories
Customer experience
How teams measure, diagnose, and improve what it feels like to be a customer.
Marketing
How growth and demand teams describe audiences, attribution, and pipeline.
Product management
The language product teams use to prioritise, scope, and measure what they build.
Brand
How marketing, brand and communications teams define, position, and measure a brand over time.
AI and automation
The terms behind AI agents, automation, and the metrics that prove they work.

Support teams are no longer a cost centre.
See how AI Support Agent, Agent Assist, and VoC Analyst work on your own ticket volume.