CRM glossary: terms teams actually use

Why a CRM glossary helps

CRM projects stall when sellers, founders, and admins use the same words for different ideas. A shared glossary speeds requirements and demos.

SchemaDesk uses precise terms like object, field, record, relation, and view because the product is schema-driven rather than hardcoded to one industry.

Core terms

Start with these definitions. They cover most buying and implementation conversations.

• Object: a record type in the workspace, such as contacts or a custom job type
• Field: a typed attribute on an object, such as email, currency, or select
• Record: one row of data for an object
• Relation: a link between records across objects
• View: a saved list layout with filters, sorts, and columns
• Pipeline: stages that track progress for deals or similar work
• Workspace: the tenant boundary for members and business data
• Template: a seed of objects and fields you can install, not a special engine
• Import: bringing CSV rows into an object with mapping and validation
• Automation: async rules that react to changes without manual busywork
• Permission: server-enforced role checks on workspace actions
• Duplicate: a likely match inside a file or against existing records

Buying and pricing terms

Seat, plan, entitlement, and add-on show up in every quote. Translate them into what your team can do on Monday, not just what the SKU is named.

Implementation terms

Mapping, preview, coercion, and batch limits matter during migration. Knowing them prevents surprise failures when a CSV is larger or dirtier than expected.

SchemaDesk language

In SchemaDesk, CRM nouns like contacts are configuration. Engines speak in objects and fields. That is why the glossary emphasizes reusable concepts over industry jargon.