Salesforce Service Cloud Consultant key terms

A record that tracks a customer's question, problem, or request from creation to resolution. It stores contact, description, status, priority, owner, and related communication so support teams can manage the work in one place.

A holding area that groups unassigned cases for a team or function, such as Tier 1 Support, so members can pick up work. Queue membership determines who can view and take the records.

A Salesforce feature that pushes incoming work items such as cases, chats, and messaging sessions to the most available agent based on capacity, skills, and priority instead of leaving them to be claimed manually.

Time-based rules that automatically reassign a case or notify a manager when the case has not been closed within set intervals, helping enforce service levels for aging work.

Rules that run when a case is created or edited to set the case owner automatically, typically routing to a queue or user based on field values such as product, region, or priority.

Rules that send an automatic email to a case contact when the case is created, confirming receipt and setting expectations, with the template chosen by matching criteria.

A record defining the support a customer is contractually owed, such as response times or channel access. It determines whether a case is covered and drives milestone tracking.

A step on an entitlement process that captures a target time for an action, such as first response or resolution, and shows whether the case is meeting its service level.

A record that ties a customer to purchased support terms and links to entitlements, so agents and automation can see which coverage applies to a given case.

A group of users given defined roles, such as support agent or product expert, who collaborate on a single case and can receive case-related notifications and access.

A console feature that surfaces existing cases matching a new case's subject or description so agents can reuse prior resolutions rather than investigating from scratch.

A set of saved instructions, such as field updates and email templates, that an agent runs with one click to complete repetitive case actions consistently and quickly.

Prewritten message snippets with merge fields that agents insert into emails, chats, and case comments to answer common questions quickly and consistently.

A Lightning app layout designed for high-volume support work, showing a case record alongside related lists, knowledge, and customer details on a single screen.

A fixed footer in a console app that gives agents always-available tools such as record history, notes, or telephony controls without leaving the current record.

A console layout option that displays a list of records next to the selected record's detail, letting agents move between cases without losing context.

The Salesforce object that stores help articles, with fields for title, summary, body, and validation status, and which can be surfaced in the console and self-service sites.

A template that defines which fields and layouts a knowledge article uses, so different content such as FAQs versus troubleshooting steps can capture different information.

A label assigned to knowledge articles to control visibility and filtering. Categories are grouped into hierarchies so articles can be targeted to specific audiences or channels.

The set of validation states, such as draft, review, published, and archived, that an article moves through, controlling who can see it and when it appears to customers.

A methodology in which solving a case also means capturing and improving the article, so knowledge creation becomes part of everyday support work rather than a separate task.

Keywords added to an article so it ranks higher in Salesforce Knowledge search results for the phrases customers and agents most commonly type.

A Knowledge feature that automatically proposes relevant articles to an agent working a case, based on the case text, so accurate answers reach customers faster.

A channel that converts inbound email into cases, either through Salesforce's email service or an on-premise agent, and threads later replies into the original case.

A channel that generates cases from a form on a website, capturing the submitter's details and question without requiring the customer to log in to a portal.

A digital channel supporting persistent, asynchronous conversations with customers inside a website or mobile app, keeping context across sessions rather than a single live chat.

A configuration that places a support component such as chat, messaging, or knowledge search directly on a customer website without building custom integration code.

A telephony integration that brings calls into the console with transcription and AI assistance, aligning voice work with the same case, routing, and reporting tools used for digital channels.

A branded, login-based website where customers can log cases, read knowledge articles, and track their requests through self-service.

An AI agent built on the Salesforce platform that handles service conversations and tasks, such as answering from knowledge or creating cases, with guardrails and escalation to human agents.

A reusable, versioned instruction stored in Salesforce that gives a generative AI model context, tone, and constraints so outputs stay consistent across a use case.

Platform controls that keep customer data out of model training, mask sensitive fields, and log AI interactions so generative features can be used with governance and auditability.

Automatically applied topic or field predictions generated from case text, which support routing decisions, trend reporting, and suggested agent responses.

A definition of which objects and relationships a report can use, determining the records and fields available when building service reports and dashboards.

A prebuilt analytics application that combines case, channel, and agent data into dashboards for measuring service performance beyond what standard reports provide.

The baseline sharing setting on an object that decides whether records are private or public, with sharing rules and the role hierarchy opening access as needed.

A structure of roles that grants users access to records owned by people below them, commonly used so managers can see and report on their team's cases.

A guided in-app home page in Service Cloud that walks administrators through enabling core features such as case settings, channels, and entitlement configuration.

A separate copy of a Salesforce org used to build and test configuration changes, integrations, and releases before they are deployed to production.

A route through which customers contact support, such as phone, email, web form, chat, messaging, or a self-service portal. The channel mix drives licensing, staffing, and routing design.