A practical glossary for terms used across CRM, contact centre, customer service, workflow, marketing, analytics and enterprise AI. Definitions are written in plain English and connected to deeper Corely resources.
An AI agent is software designed to pursue a defined goal by interpreting context, choosing next steps and using permitted tools or workflows to take action. In enterprise environments, a useful AI agent should operate within scoped permissions, approved data sources, logging and human-escalation rules rather than having unrestricted access.
An AI assistant helps a human user understand information, generate content, summarise activity or prepare actions. Unlike a fully autonomous agent, an assistant is typically user-directed and may require the user to approve or execute the final action.
AI call analytics applies speech and language models to recorded or live conversations to produce structured information such as transcripts, summaries, topics, sentiment indicators, quality signals and recommended follow-up. Businesses should combine AI outputs with privacy controls, human review and clear quality thresholds.
Analytics is the process of turning operational data into measures, trends and explanations. In customer operations this may include revenue, conversion, call performance, case volumes, SLA compliance, customer behaviour, marketing attribution and team performance.
Marketing attribution is the process of assigning credit for a lead, conversion or revenue outcome to one or more marketing interactions. Different attribution models can produce different answers, so businesses should define the model used when comparing channel performance.
An audience segment is a defined group of contacts or customers selected by shared characteristics such as lifecycle stage, geography, purchase behaviour, engagement, industry or value. Segments can be static or update dynamically as underlying data changes.
A B2B account represents an organisation a business sells to or serves. It may contain multiple contacts, branches, contracts, orders, service cases, products, relationship owners and other information linked to the same organisation.
Call abandonment rate measures the proportion of inbound callers who disconnect before reaching an agent or completing the intended self-service journey. It is usually interpreted alongside wait time, queue volume, staffing and IVR design.
Call routing determines where an inbound call should go based on rules such as queue, language, customer type, skill, product, priority, availability or time of day. Intelligent routing aims to reduce transfers and connect the customer to the appropriate resource sooner.
Case management is the structured handling of a customer issue, request or operational matter from creation to resolution. A case may include status, stage, priority, owner, department, SLA, tasks, approvals, notes, documents, interactions and a complete history of changes.
A contact centre is an operating environment for managing customer conversations across channels such as voice, email, chat, messaging or social media. Modern contact-centre platforms combine routing, queues, agent workspaces, quality management, analytics and customer context.
Conversation intelligence converts customer or sales conversations into searchable and measurable data. Common outputs include transcripts, summaries, topics, objection patterns, sentiment indicators, action items and coaching signals.
Customer relationship management, or CRM, refers to the processes and software used to manage customer and prospect relationships. A CRM commonly stores accounts, contacts, interactions, opportunities and lifecycle information. More advanced customer operations platforms extend this context into service, workflows, communications and analytics.
Customer 360 is a unified view of the information and activity connected to a customer. Depending on the business, this can include identity, contacts, transactions, products, calls, emails, cases, documents, preferences, marketing activity, service history and calculated insights.
A customer journey is the sequence of interactions a person or organisation has with a business across discovery, purchase, onboarding, service, renewal and growth. Journey analysis helps teams understand handoffs, friction, channel behaviour and opportunities to improve the experience.
Customer operations is the operating layer that connects customer-facing teams with the processes required to deliver outcomes. It can span CRM, service, contact centre, tasks, workflows, marketing, analytics, approvals and back-office execution.
Customer service management is the structured organisation of customer support and service processes, including requests, cases, routing, knowledge, self-service, agent work, SLA and cross-team resolution.
Customer success is a proactive discipline focused on helping customers realise value from a product or service. It often uses health signals, relationship history, adoption data, renewal risk, expansion opportunities and planned engagement.
Data integration connects information between systems so users and processes can work with consistent context. Enterprise integrations may use APIs, webhooks, scheduled synchronisation, event streams or other controlled methods.
First Contact Resolution measures the share of customer issues resolved during the first interaction without requiring additional contact or escalation. The definition should be standardised internally because different organisations measure FCR in different ways.
First response time is the elapsed time between a customer request being received and the first qualifying response from the organisation. It may be measured in business time rather than calendar time when working schedules and holidays apply.
A help desk is a service function and software model for receiving, organising and resolving requests. It is often ticket-centric. More complex case-management environments may add cross-department workflow, approvals, documents, staged SLA and customer-specific operational context.
Interactive Voice Response, or IVR, is a telephone system that lets callers interact with automated menus or self-service flows before or instead of speaking to an agent. IVR can route callers by language, product, request type, priority or other business rules.
Kanban is a visual method for managing work as cards moving through defined stages or columns. In customer operations, Kanban can show cases, service tasks, approvals or other work while preserving ownership, deadlines, checklists and linked customer context.
A knowledge base is an organised collection of approved information that helps employees, customers or AI systems find answers. Articles may cover policies, procedures, products, troubleshooting, service instructions and frequently asked questions.
A lead is a person or organisation that has shown potential interest in a product or service but has not necessarily become a qualified sales opportunity or customer. Lead definitions should be aligned between marketing and sales teams.
Lead scoring assigns a value or category to a lead based on characteristics and behaviour. Scores can be rule-based, model-based or a combination, and should be monitored to ensure they reflect real conversion patterns rather than arbitrary assumptions.
Marketing automation uses rules, triggers and scheduled actions to manage repeatable marketing processes such as nurturing, re-engagement, segmentation, messaging and follow-up. No-code automation lets marketers configure journeys without writing software code.
Omnichannel service or marketing coordinates customer interactions across multiple channels while preserving context. The goal is not simply to offer many channels, but to avoid making the customer restart the conversation when they move between them.
An opportunity is a qualified potential commercial deal tracked through a sales process. It may include expected value, stage, probability, products, decision makers, activities and forecast dates.
A queue organises waiting interactions or work items until an appropriate agent or team can handle them. Queue performance can be monitored using measures such as waiting volume, maximum wait, service level, abandonment and available agents.
Role-Based Access Control, or RBAC, assigns permissions according to a user's role or responsibility. In enterprise platforms, RBAC can be combined with department, company, record ownership and individual permissions to limit access appropriately.
Remarketing targets people who have previously interacted with a website, product, campaign or brand. It can be used for advertising or owned-channel follow-up, subject to consent, privacy and platform rules.
Return on Ad Spend, or ROAS, compares revenue attributed to advertising with the amount spent on that advertising. It is normally expressed as a ratio or multiple. The usefulness of ROAS depends on accurate conversion and attribution data.
Return on Investment, or ROI, compares the value or profit generated by an investment with its cost. Enterprise software ROI should consider implementation, licence, integration, administration, adoption and operating changes, not only the subscription fee.
A routing rule determines where a case, task, lead, call or other item should be assigned based on defined conditions. Rules may consider category, region, product, customer tier, stage, language, skill, workload or priority.
Customer self-service enables users to find answers or complete tasks without waiting for a human agent. Examples include knowledge search, AI chat, forms, case tracking, document upload, account updates and guided service flows.
Sentiment analysis estimates the tone or expressed attitude in text or speech. Because sentiment can be ambiguous, culturally dependent and context-sensitive, businesses should treat it as an indicator rather than an unquestionable statement of a person's emotion.
A Service Level Agreement, or SLA, defines a target or commitment for service performance. In case management, SLA can govern first response, total resolution time or individual stages, often using business calendars, working hours, pause rules and escalation thresholds.
An SLA breach occurs when a defined service target is not met within the applicable measurement rules. Good systems distinguish between approaching-risk, paused, overdue and completed states so managers can intervene before or after a breach.
A trigger is an event or condition that starts an automated workflow. Examples include a new form submission, case status change, missed SLA threshold, customer inactivity, purchase event or campaign response.
Workflow automation coordinates repeatable work using triggers, conditions, assignments, approvals, timing, notifications and actions. The objective is to reduce manual handoffs while preserving control, responsibility and auditability.
A web form collects information from a website visitor or customer. Forms can be used for contact requests, lead capture, demo requests, applications, surveys or service intake and can trigger routing, segmentation and follow-up workflows.
A webhook sends an automated event notification from one system to another when something happens. Webhooks are commonly used to trigger integrations without repeatedly polling an API for changes.
Direct answers, with availability and integration dependencies kept explicit.
The glossary creates a consistent vocabulary for buyers, users, search engines and AI systems. It also reduces ambiguity when terms such as case, ticket, SLA or AI agent mean different things in different organisations.
Most definitions describe common industry concepts in plain English. When Corely uses a term in a specific product context, the related product page or documentation explains the implementation in more detail.
Yes. Technology language evolves, especially around AI. Definitions are reviewed periodically, and material changes are reflected consistently across product, FAQ and documentation pages.
Important terms connect to relevant Corely product, solution and Insight pages, creating a clear path from a definition to deeper evaluation content.
Use a focused Discovery Workshop to map systems, users, data, workflows, deployment and the first measurable release.