A customer contacts a company because something is not working as expected. At the same time, a sales representative may be preparing a renewal, a service agent may be handling an open case, a manager may be waiting for an approval, and a customer may be searching the knowledge base for an answer.
All of these activities are connected to the customer relationship, but they do not always use the same terminology.
This is where understanding ServiceNow CRM terminology becomes useful. Terms such as Account, Contact, Case, Opportunity, SLA, Knowledge Article, Flow Designer, ACL, API, and Now Assist describe different parts of the customer and service experience. Understanding what each term means, and how the terms relate to one another, makes it easier to work with ServiceNow and communicate across business and technical teams.
This glossary explains 65 commonly used CRM, customer service, workflow, platform, and AI terms in straightforward language, with ServiceNow context and practical examples.
Customer and CRM fundamentals
Account
An Account represents an organisation or business that has a relationship with your company.
In a ServiceNow CRM environment, an account can represent a customer organisation, partner, or another business entity. The account record can provide context for contacts, opportunities, cases, products, and other customer-related activities.
Example: A software company has ABC Manufacturing as a customer. ABC Manufacturing is represented as an account, while its employees who interact with the software company are stored as contacts.
Contact
A Contact is a person associated with an account or customer relationship.
Contacts may include decision-makers, users, buyers, administrators, or other people who communicate with the organisation.
Example: Priya Sharma works for ABC Manufacturing and contacts the service team about a product issue. Priya can be represented as a contact associated with the ABC Manufacturing account.
Customer
A Customer is a person or organisation receiving products, services, or support from a company.
In ServiceNow, customer information can be connected across sales, service, support, and engagement processes.
Example: ABC Manufacturing purchases software and receives technical support. ABC Manufacturing is therefore a customer, while its employees may appear as individual contacts.
Customer Relationship Management (CRM)
Customer Relationship Management (CRM) refers to the processes, data, and technology used to manage interactions with customers and prospects.
CRM brings together information about customers, accounts, contacts, sales activities, service interactions, and relationships.
ServiceNow can connect CRM-related activities with customer service and other enterprise workflows so that teams can work from shared customer information.
Example: A sales representative reviewing an account can see relevant customer information, while a service agent handling a case can work with the same underlying customer context.
Customer Experience (CX)
Customer Experience (CX) describes the overall experience a customer has when interacting with an organisation.
It includes activities such as purchasing a product, requesting support, finding information, communicating with agents, and resolving problems.
Example: If a customer can quickly find an answer through self-service, submit a request easily, receive timely updates, and get an issue resolved without repeating information, those interactions contribute to the overall customer experience.
Customer Service Management (CSM)
Customer Service Management (CSM) is ServiceNow's approach to managing customer service operations and workflows.
CSM helps organisations manage customer cases, requests, interactions, knowledge, self-service, customer communication, and related processes.
Example: A customer reports a product issue through a portal. The issue becomes a case, is assigned to the appropriate team, follows the relevant SLA, and can be supported by knowledge and automation.
Customer Service
Customer Service refers to the processes and activities used to help customers before, during, and after they use a product or service.
In ServiceNow, customer service can include case management, service requests, knowledge, self-service, communication, and escalation.
Example: A customer contacts support because a business application is unavailable. The service team records the issue, investigates it, communicates with the customer, and works toward resolution.
Interaction
An Interaction represents an engagement or communication between a customer and an organisation.
Interactions can provide context for customer conversations across channels.
Example: A customer starts a conversation through chat and later contacts the support team by phone. Capturing the interaction history helps the agent understand what has already been discussed.
Relationship
A Relationship describes how people, organisations, products, cases, or other business records are connected.
Understanding relationships is important because customer information rarely exists in isolation.
Example: A contact belongs to an account, an account has opportunities, a customer has cases, and a case may be related to a product.
Persona
A Persona represents a particular type of user or customer based on characteristics, needs, responsibilities, or behaviour.
Personas can help organisations design experiences around different user needs.
Example: A purchasing manager may need contract and pricing information, while a technical administrator may primarily need troubleshooting and product information.
Sales and opportunity management
Lead
A Lead represents a potential customer or business opportunity that has not yet become a qualified opportunity.
Leads may come from campaigns, website forms, events, referrals, or other sources.
Example: A company downloads a product guide and provides its contact information. The resulting prospect can initially be treated as a lead for sales follow-up.
Opportunity
An Opportunity represents a potential sales transaction that has progressed beyond the initial lead stage.
An opportunity typically includes information such as the customer, expected value, products, sales stage, and expected close date.
Example: ABC Manufacturing is considering purchasing additional software licences. The potential deal is tracked as an opportunity.
Sales Pipeline
The Sales Pipeline represents the collection of active sales opportunities and their stages.
It helps sales teams understand where opportunities are in the sales process.
| Sales term | What it represents |
|---|---|
| Lead | Potential customer or initial prospect |
| Opportunity | Qualified potential business transaction |
| Sales Pipeline | Collection of active opportunities |
| Quote | Proposed commercial offer |
| Forecast | Expected sales outcome |
Example: A sales manager reviews the pipeline to see how many opportunities are in qualification, proposal, negotiation, and closing stages.
Quote
A Quote is a commercial proposal provided to a customer that describes products or services, quantities, pricing, and other relevant terms.
Example: A customer requests 500 additional software licences. The sales team prepares a quote showing the requested products, quantities, and pricing.
Forecast
A Forecast represents an estimate of expected future sales or revenue.
Sales teams use forecasts to plan business activity and understand potential future outcomes.
Example: A sales manager reviews current opportunities and their stages to estimate the expected revenue for the quarter.
Sales Engagement
Sales Engagement refers to the structured activities used to interact with prospects and customers during the sales process.
This can include outreach, follow-ups, communications, and other activities designed to move a relationship forward.
Example: A sales representative follows up with a prospect after a product demonstration and schedules a meeting to discuss requirements.
Account Management
Account Management involves managing an ongoing relationship with a customer organisation.
Account managers may work with customer stakeholders, monitor opportunities, coordinate service issues, and identify expansion or renewal opportunities.
Example: An account manager reviews a customer's open cases, upcoming renewal, current products, and business requirements before a quarterly customer meeting.
Opportunity Management
Opportunity Management is the process of managing sales opportunities throughout their lifecycle.
It includes tracking stages, activities, expected value, products, stakeholders, and potential close dates.
Example: A sales team moves an opportunity from qualification to proposal after confirming the customer's requirements and budget.
Product
A Product represents something an organisation sells, provides, or supports.
Products can be connected to sales opportunities, quotes, cases, requests, and entitlements.
Example: A customer has a support case related to a specific software product. Associating the product with the case gives the service team additional context.
Entitlement
An Entitlement defines what support or service a customer is entitled to receive.
It can be based on factors such as a contract, subscription, product, service level, or customer agreement.
Example: A premium customer may be entitled to 24/7 support with a faster response time than a standard customer.
Customer service and case management
Case
A Case represents a customer issue, question, or service-related request that requires attention.
Cases are central to customer service because they give agents a structured way to track the customer's issue from creation through resolution.
Example: A customer reports that users cannot access an application. A case is created so the service team can investigate, communicate with the customer, and document the resolution.
Case Management
Case Management is the process of creating, assigning, working, updating, escalating, and resolving customer cases.
A well-designed case management process helps agents follow consistent procedures while maintaining customer context.
Example: A case is created through the customer portal, routed to the correct team, investigated by an agent, updated with customer communication, and closed after resolution.
Case Assignment
Case Assignment determines which agent or team should work on a case.
Assignment can be based on factors such as product, location, issue type, skill, priority, or workload.
Example: A case related to a billing problem can be routed to the billing support team rather than a technical support team.
Case Escalation
Case Escalation occurs when a case needs additional attention because of complexity, urgency, priority, or service-level requirements.
Escalation may involve moving the case to another team, increasing its priority, or involving management.
Example: A critical customer issue remains unresolved and approaches its SLA deadline. The case is escalated to a specialist team.
Service Request
A Service Request is a customer's request for a service, item, access, or standard fulfilment activity.
A service request is generally different from a case involving an unexpected issue or problem.
| Term | Typical purpose | Example |
|---|---|---|
| Case | Customer issue or support matter | Application is not working |
| Service Request | Request for a standard service | Request additional user access |
| SLA | Time commitment for service | Respond within four hours |
SLA
An SLA (Service Level Agreement) defines service commitments such as response or resolution targets.
In ServiceNow, SLA management can track whether cases or other records are meeting defined service-level commitments.
Example: A priority customer case may require a response within one hour and resolution within eight hours.
Major Issue
A Major Issue is a significant customer-impacting problem that requires coordinated attention and potentially accelerated handling.
The exact definition and process can vary between organisations.
Example: A critical product failure affects many customers. The organisation treats the issue with increased coordination, communication, and escalation.
Case Task
A Case Task is a smaller piece of work associated with a larger customer case.
Tasks allow different teams or individuals to complete specific activities required to resolve the overall case.
Example: A customer case requires both a technical investigation and an account verification. Separate tasks can be created for the teams responsible for each activity.
Customer Communication
Customer Communication includes messages and updates exchanged between an organisation and its customers.
Clear communication is important throughout the case lifecycle, especially when customers are waiting for resolution.
Example: An agent sends a customer an update explaining that the issue has been identified and that the engineering team is working on a fix.
Service Catalog
The Service Catalog provides a structured way for users or customers to request predefined services or items.
Catalog items can be connected to workflows, approvals, fulfilment activities, and automation.
Example: A customer selects a predefined service package from a catalog and submits a request without needing to contact an agent manually.
Knowledge and self-service
Knowledge Management
Knowledge Management is the process of creating, organising, maintaining, publishing, and using information to help users and agents solve problems.
In ServiceNow, knowledge management can support both customer self-service and internal agent workflows.
Example: A support team publishes troubleshooting instructions that customers can use before opening a case.
Knowledge Base
A Knowledge Base is a structured collection of knowledge articles.
Organisations may maintain different knowledge bases for different audiences, products, departments, or purposes.
Example: A company may have separate knowledge bases for customer troubleshooting, internal support procedures, and product documentation.
Knowledge Article
A Knowledge Article is an individual piece of documented information stored in a knowledge base.
Articles can explain procedures, answer common questions, or provide troubleshooting guidance.
Example: "How to reset your account password" can be published as a knowledge article that customers can access through self-service.
Self-Service
Self-Service allows customers or users to find information, submit requests, check status, or perform other activities without directly contacting an agent.
Example: A customer searches for a solution, reads a knowledge article, and resolves the issue without creating a case.
Customer Portal
A Customer Portal provides customers with a digital interface for interacting with services and support.
Depending on the implementation, customers may use the portal to search knowledge, create cases, submit requests, track activity, and communicate with service teams.
Example: A customer signs in to the portal, searches for an answer, and then creates a case if the available information does not solve the problem.
Virtual Agent
Virtual Agent provides conversational assistance through a chatbot-style experience.
In ServiceNow, Virtual Agent can help users find information, complete tasks, and interact with service processes through conversation.
Example: A customer asks, "How can I reset my password?" Virtual Agent can provide the appropriate information or guide the customer through the relevant process.
Employee/Agent Workspace
Employee/Agent Workspace provides a focused interface where employees or service agents can work with records, tasks, cases, and related information.
For customer service agents, the workspace can bring relevant customer information and work activities into a single working environment.
Example: An agent opens a case and can review customer information, previous interactions, related knowledge, tasks, and case details without navigating through unrelated parts of the platform.
Omnichannel
Omnichannel refers to providing connected customer interactions across multiple communication channels.
The goal is to provide continuity when customers move between channels.
Example: A customer begins a conversation through chat and later contacts the service centre by phone. The agent can use available interaction history to understand the previous conversation.
Search
Search allows users and agents to find relevant information across available data and content.
Search is especially important in self-service and knowledge-driven support because finding the right answer quickly can prevent unnecessary case creation.
Example: A customer searches for "VPN connection problem" and finds a relevant troubleshooting article.
Service Experience
Service Experience describes how users interact with services throughout their journey.
It includes the channels, processes, information, communication, and outcomes involved in receiving a service.
Example: A customer can search for an answer, submit a request, receive status updates, and track progress through one connected experience.
Workflow and automation
Workflow
A Workflow defines a sequence of activities used to move work from one step to another.
In ServiceNow, workflows can coordinate tasks, approvals, notifications, and other activities.
Example: A service request is submitted, approved by a manager, assigned to a fulfilment team, completed, and then communicated back to the requester.
Flow Designer
Flow Designer is ServiceNow's low-code capability for creating automated flows.
It allows organisations to define triggers, actions, conditions, approvals, and other steps without requiring every process to be implemented through custom scripting.
Example: When a customer submits a specific type of request, Flow Designer can automatically create tasks, request approval, and notify the relevant team.
Business Rule
A Business Rule is server-side logic that runs when specific database operations or conditions occur.
Business Rules can be used to validate data, update records, trigger actions, or enforce business logic.
Example: When a record is updated, a Business Rule can check whether required information is present before allowing the transaction to continue.
Automation
Automation uses technology to perform activities with limited or no manual intervention.
ServiceNow automation can include workflows, flows, business rules, integrations, notifications, and other platform capabilities.
Example: Instead of manually assigning every new case, an automated process can route cases based on category and customer information.
Approval
An Approval is a decision step where an authorised person or group must approve an action before a process can continue.
Example: A customer requests a service that requires commercial approval. The request is routed to the appropriate manager before fulfilment begins.
Notification
A Notification communicates information to users or teams when a defined event occurs.
Notifications may be delivered through email or other supported channels.
Example: When a case is assigned to an agent, the system can send a notification informing the agent about the new work.
Assignment Rule
An Assignment Rule determines how work is automatically assigned to users or groups.
Assignment rules can use conditions such as category, priority, product, location, or other record information.
Example: Cases categorised as "Billing" can automatically be assigned to the billing support group.
Flow
A Flow is an automated sequence of actions created to respond to a trigger or event.
A flow can perform actions such as updating records, creating tasks, sending notifications, or requesting approvals.
Example: When a new high-priority case is created, a flow can notify the responsible team and create a follow-up task.
Playbook
A Playbook provides a structured set of activities that guides users through a particular process.
It is useful when work requires multiple coordinated steps rather than a single automated action.
Example: A complex customer issue may require the agent to verify customer information, perform troubleshooting, involve another team, communicate an update, and confirm resolution.
Integration
An Integration connects ServiceNow with another system so information or actions can move between them.
Integrations can support processes such as customer data synchronisation, order processing, payment information, or external service updates.
Example: A ServiceNow process can exchange information with an external customer or billing system so agents do not have to manually copy information between applications.
Data and platform
Table
A Table is a structured collection of records in the ServiceNow platform.
Tables define where a particular type of data is stored and can contain fields that describe that data.
Example: A case table stores case records, while each case record contains information such as number, customer, priority, status, and description.
Record
A Record is an individual entry in a ServiceNow table.
Each record represents one specific business object or transaction.
Example: A particular customer case with a unique case number is a record in the relevant ServiceNow table.
Field
A Field stores a specific piece of information on a record.
Fields can contain values such as text, numbers, dates, references, choices, or other types of data.
Example: A case can contain fields for customer, priority, status, assignment group, description, and resolution notes.
Data Model
A Data Model defines how information is structured and related across tables, records, fields, and relationships.
A well-designed data model helps different processes work with consistent information.
Example: Customer information can be connected to contacts, cases, products, requests, and other related records.
Role
A Role defines a set of permissions or capabilities assigned to a user or group.
Roles help determine what users can access or perform within the platform.
Example: A service agent may have permissions needed to view and update customer cases, while another user may have access only to customer-facing information.
Access Control List (ACL)
An Access Control List (ACL) controls access to data or functionality based on defined security rules.
ACLs can determine whether a user can read, create, update, or delete particular records or fields.
Example: A sensitive customer field may be restricted so that only users with the appropriate role can view or modify it.
API
An API (Application Programming Interface) provides a structured way for applications to communicate with one another.
ServiceNow provides APIs that allow external systems and applications to interact with platform data and functionality.
Example: An external application can use an API to create a ServiceNow case when a customer reports a problem through another system.
IntegrationHub
IntegrationHub provides ServiceNow capabilities for connecting the platform with external systems and services.
It can be used to create integrations and automate actions across applications.
Example: A ServiceNow flow can use IntegrationHub to interact with an external application as part of a customer service process.
AI and intelligent CRM
Generative AI
Generative AI refers to AI systems that generate new content such as text, summaries, responses, or other outputs based on provided information and instructions.
In customer service, generative AI can assist with activities such as summarisation, drafting responses, and generating knowledge content.
Example: An agent reviewing a long customer case can use generative AI capabilities to create a concise summary of the issue and previous actions.
AI Search
AI Search uses AI-driven capabilities to improve how users find relevant information.
Instead of relying only on exact keyword matching, AI-powered search can use context and meaning to help surface useful results.
Example: A customer searches for "I cannot log in after changing my phone" and receives relevant authentication or account recovery information even if the exact words do not appear in the article title.
Predictive Intelligence
Predictive Intelligence uses machine learning capabilities to identify patterns and make predictions or recommendations based on available data.
In ServiceNow, it can support activities such as categorisation, assignment, and prediction.
Example: A new case can be analysed based on historical data to predict its category or suggest the appropriate assignment group.
Agent Assist
Agent Assist refers to capabilities that help service agents while they are working on customer interactions or cases.
These capabilities can surface relevant information, recommendations, summaries, or knowledge so agents can work more efficiently.
Example: While handling a customer case, an agent may receive relevant knowledge suggestions based on the case details.
Now Assist
Now Assist is ServiceNow's family of generative AI capabilities designed to assist users across ServiceNow workflows and experiences.
Depending on the ServiceNow product and configuration, Now Assist capabilities can support tasks such as summarisation, content generation, conversational assistance, and productivity improvements.
Example: An agent can use Now Assist to summarise a customer case before taking over the interaction.
Machine Learning
Machine Learning is a form of AI in which systems learn patterns from data to make predictions, classifications, or recommendations.
In ServiceNow, machine learning can support capabilities such as predictive categorisation and intelligent recommendations.
Example: Historical case data can be used to identify patterns that help predict the likely category of a new case.
Intelligent Automation
Intelligent Automation combines automation with data-driven or AI-based capabilities to make processes more adaptive and efficient.
Instead of simply following fixed steps, intelligent automation can use available information to determine what action should happen next.
Example: A new customer case can be automatically categorised, routed to an appropriate team, matched with relevant knowledge, and followed by automated communication.
How these 65 terms connect in a real customer journey
The value of a CRM glossary becomes clearer when the terms are viewed as connected parts of a customer journey rather than isolated definitions.
Consider a customer purchasing an enterprise software product.
The organisation first exists as an Account, with individual stakeholders represented as Contacts. A potential sales engagement may begin as a Lead and eventually become an Opportunity.
As the opportunity progresses through the Sales Pipeline, the sales team may prepare a Quote, update the Forecast, and manage the relationship through Account Management and Opportunity Management.
Once the customer purchases the Product, the customer's support rights may be defined through an Entitlement.
Later, the customer may encounter a problem and create a Case. The case enters Case Management, is handled through Case Assignment, and may involve Case Tasks or Case Escalation depending on its complexity.
If the customer is simply requesting a standard service, the activity may instead be handled as a Service Request through the Service Catalog.
The service team works against the applicable SLA, communicates with the customer, and can use Knowledge Articles, Knowledge Management, and Self-Service to accelerate resolution.
Customers may interact through a Customer Portal, Virtual Agent, or other Omnichannel experiences. Agents can work from Employee/Agent Workspace and use Search to find relevant information.
Behind these experiences, Workflow, Flow Designer, Business Rules, Automation, Approvals, Notifications, Assignment Rules, Flows, and Playbooks can coordinate the work.
The underlying information is stored in Tables, Records, and Fields, structured through the organisation's Data Model, and protected through Roles and Access Control Lists (ACLs).
External systems can communicate with ServiceNow through APIs and IntegrationHub.
AI capabilities can then add another layer of assistance. AI Search, Predictive Intelligence, Agent Assist, Generative AI, Now Assist, Machine Learning, and Intelligent Automation can support users and agents with finding information, predicting outcomes, summarising work, and automating decisions or activities.
This is why CRM terminology matters. The terms describe different parts of the same connected customer journey.
Why the relationships between terms matter
Knowing the definition of a term is useful, but understanding how it relates to other terms is more valuable when working with ServiceNow.
For example, Case, Case Management, SLA, Case Assignment, and Case Escalation are closely related.
A case represents the work. Case management describes the overall process. The SLA defines the service commitment. Assignment determines who works on the case, while escalation provides a path for cases that require additional attention.
The same principle applies to sales.
A Lead may become an Opportunity. Opportunities form the Sales Pipeline. A quote can be created for an opportunity, and the collection of opportunities contributes to the sales Forecast.
The platform terms work together in a similar way.
A Table stores records. A Record contains fields. The Data Model defines how the information is structured and related. Roles and ACLs control access, while APIs and IntegrationHub can connect the information to external systems.
AI terms also become easier to understand when viewed together.
Machine Learning provides a foundation for learning patterns from data. Predictive Intelligence can use those capabilities for predictions and recommendations. AI Search helps users find relevant information. Agent Assist supports agents during their work, while Generative AI can create or summarise content. Now Assist brings ServiceNow's generative AI capabilities into supported workflows and experiences. Intelligent Automation combines automation with intelligence to support more adaptive processes.
Making ServiceNow CRM terminology easier to work with
A glossary becomes much more useful when teams use the terminology consistently.
For business teams, this means understanding what each term represents in the customer journey.
For ServiceNow administrators and developers, it means understanding how the business concept maps to platform capabilities, records, tables, fields, workflows, security, and integrations.
For service agents, it means knowing which process applies to the customer's situation.
For technical teams, it means designing the platform so that customer information flows consistently between the relevant processes.
A shared vocabulary can reduce confusion during requirements discussions, implementation projects, process design, testing, training, and ongoing platform improvements.
For example, saying "create a case and route it according to the customer's entitlement and priority" is much clearer than simply saying "send this issue to support."
The terminology gives the requirement structure.
If you are exploring how ServiceNow CRM and customer service capabilities can be aligned with your organisation's processes, Impactron can help you understand the available options and implementation approach.
A glossary should support the customer journey, not replace it
ServiceNow CRM terminology can look complicated when each term is considered separately.
Once the terms are connected, the picture becomes much easier to understand.
A customer relationship starts with people and organisations. Sales processes manage potential business. Customer service handles questions, issues, and requests. Knowledge and self-service help customers find answers. Workflows and automation coordinate activities. The ServiceNow data model provides the underlying structure. Integrations connect other systems. AI capabilities add intelligence and assistance to many of these processes.
The important point is not simply memorising 65 definitions.
It is understanding where each term fits and how the terms work together.
Final thought
CRM terminology is not just a list of technical definitions.
Each term represents a piece of a larger customer journey, from the first sales interaction to ongoing service, from a customer question to its resolution, and from manual work to automated and intelligent processes.
Understanding that connection is what makes the terminology useful.