AI and automation glossary

Understand the words behind the workflow.

Plain-language definitions for the terms used across business AI, integration and implementation planning. Follow the related resource to see how each concept applies to real work.


26 terms.

AI agent

An assistant designed to use approved knowledge or tools toward a bounded task. Its authority to suggest, prepare or execute actions should be explicit.

Explore in context →
API

An application programming interface: a defined way for one system to request information or actions from another, subject to its authentication and rules.

Explore in context →
Baseline

A measurement of the current process used to compare a later pilot or implementation. Record quality and exceptions as well as time or volume.

Explore in context →
Chatbot

A message-based interface. It may use fixed rules, retrieved information or a model; the interface alone does not establish permission to act in business systems.

Explore in context →
CRM

Customer relationship management software and processes for organizing customer records, enquiries, opportunities, activities and ownership.

Explore in context →
Data retention

The agreed approach to how long information is kept, for what purpose and how it is removed. The actual period and process depend on the service and applicable requirements.

Explore in context →
Duplicate handling

Rules for recognizing repeated requests or matching existing records, so retrying an event does not silently create unrelated copies.

Explore in context →
ERP

Enterprise resource planning: software and connected processes used to organize core operational records and business activities.

Explore in context →
Escalation

Passing a request to an authorized person or team when its uncertainty, sensitivity or required action is outside the current workflow.

Explore in context →
Human-in-the-loop

A workflow in which a person reviews or authorizes defined steps. The review needs context, authority and a clear action—not only a notification.

Explore in context →
Idempotency

Designing a repeated operation so that retries do not create an unintended additional effect. A stable request identifier and target-system behavior are part of the contract.

Explore in context →
Integration

A connection between systems with agreed access, field mapping, actions and failure handling. A provider name in a directory is not evidence that an account is connected.

Explore in context →
Knowledge base

A maintained collection of approved information. Its audience, content owner and update process affect whether it is useful for an assistant.

Explore in context →
Latency

The delay between an input and an observable response. Measure the complete task and provider handoffs rather than only one model request.

Explore in context →
Least privilege

Granting only the access needed for an agreed task, rather than broad permissions by default. Credentials and allowed actions still need operational review.

Explore in context →
OAuth

A framework for delegated access to protected resources. The relevant provider, permission scopes, account consent and token lifecycle need to be reviewed for a connection.

Explore in context →
Pilot

A limited implementation used to test a defined workflow against agreed examples and acceptance criteria before deciding whether to expand.

Explore in context →
Prompt

Instructions or context supplied to a model. A prompt does not replace application-level validation, identity checks or tool permissions.

Explore in context →
Rate limit

A restriction on how frequently requests may be made. The implementation needs appropriate queueing, backoff or user feedback when a provider limit is reached.

Explore in context →
Retrieval-augmented generation

Preparing model responses using retrieved source material as context. Relevant, current sources and a defined fallback are still needed; retrieval does not guarantee correctness.

Explore in context →
ROI estimate

A business-case model based on explicit assumptions about costs and benefits. The website calculator models theoretical labor capacity, not guaranteed cash savings.

Explore in context →
Scope

The agreed tasks, features, permissions, responsibilities and exclusions for a project or service. An illustrative workflow is not itself a delivery commitment.

Explore in context →
Service-level agreement

An agreement defining specific service commitments and how they are measured. Targets must be confirmed in the applicable contract rather than inferred from a support page.

Explore in context →
Source of truth

The authoritative system or record for a particular field or state. Bidirectional connections need rules for conflicting updates.

Explore in context →
Tool calling

An assistant requesting a defined application function. The server must validate the request and check authorization before executing an action.

Explore in context →
Webhook

An event notification sent to a configured endpoint. Verify its source and distinguish event receipt from completed downstream processing.

Explore in context →