# Customer journey | 121 CRM > A plain-English definition of Customer journey, with a practical CRM example, related terms, common misunderstandings and implementation questions. Customer journey means the sequence of interactions and decisions a person experiences across discovery, enquiry, service and ongoing relationship. The meaning is useful only when the business agrees how the term appears in its own records, decisions and customer journey. ## Customer journey in a customer record Fictional example using Field & Form, a landscaping business. ## Capabilities explained ### Contacts Stores a person or lead with contact details, activity, ownership and related records. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Gives a team one place to understand who a customer is and what has happened. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Conversations inbox Brings supported connected message threads into a shared operational inbox. **How it works:** Handles an eligible customer interaction through a configured inbox, number or connected channel. **Why a business would use it:** Helps a team see the customer history and coordinate replies from one working view. **Limitations:** Delivery, message types, geographic coverage, approval and charges vary by channel and provider. **Human responsibility:** A person must own sensitive conversations, failed delivery and any situation outside the approved script. ### Opportunities Represents a potential sale or deal linked to a contact, value, owner and pipeline position. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Shows which customer conversations are active commercial work rather than general contacts. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Appointments Stores scheduled customer interactions with time, attendee, owner, status and related contact context. **How it works:** Applies configured availability, booking rules and connected-calendar settings to eligible appointments. **Why a business would use it:** Makes booked work visible alongside the customer conversation and follow-up. **Limitations:** Sync, meeting-link and resource behaviour varies by calendar type and external provider. **Human responsibility:** Staff must handle exceptions, incorrect availability and bookings that need judgement. ## What customer journey means In this glossary, customer journey is the sequence of interactions and decisions a person experiences across discovery, enquiry, service and ongoing relationship. Different suppliers may label fields differently, so the team should document its working definition rather than relying on a menu label alone. ### The essential idea Customer journey helps people describe a particular part of customer work consistently. Its value comes from a shared definition and an action or decision that follows from it. ### What it is not Customer journey is not an internal workflow, which describes how the organisation performs its part of that journey. Keeping those ideas separate prevents reports, workflows and handovers from combining records that mean different things. ### Why the definition matters If two people use customer journey differently, counts and automation can appear precise while describing inconsistent situations. Agree the rule before measuring or triggering action. ## Customer journey at Field & Form Field & Form uses the term in one bounded workflow. The example shows the definition in use without asserting a fixed 121 configuration. ### The situation Field & Form receives an enquiry through its website. A record is created with the source, contact details provided and a named owner for the next review. ### The classification The owner applies the written customer journey definition to the facts available. If information is missing or the case is unusual, it is held for a person rather than classified by guesswork. ### The consequence The recorded term changes what appears in the team view, which checks apply and what next action is expected. The team can later inspect the original facts and decision. ## Questions to settle before using customer journey A glossary definition is a starting point. Configuration still needs an owner, boundaries and realistic testing. ### Which record owns it? Decide whether customer journey belongs on a contact, company, opportunity, activity or another record. Avoid copying the same value into several places without a clear source of truth. ### Who may change it? Set the role allowed to create or change the value and the evidence they should use. Restrict consequential or sensitive changes to appropriate people. ### What happens next? Document any view, task, workflow or report that depends on customer journey. Test ordinary, missing, duplicate and exceptional cases before relying on the rule. ## Keep customer journey distinct from neighbouring terms Clear language reduces configuration mistakes and makes management reporting easier to challenge constructively. ### Use examples Keep two or three fictional examples that meet the definition and one that does not. Examples often reveal ambiguity faster than a longer abstract definition. ### Align the reports Check that dashboard labels and filters use the same definition. A report should state its population, period, exclusions and data-quality limits. ### Review after change Revisit the definition when the customer journey, services, data model or responsibilities change. Update dependent workflows and reports together. ## Frequently asked questions ### Is customer journey defined the same way in every CRM? No. The underlying idea may be common, but suppliers and businesses can use different labels and rules. Record the working definition used by your team. ### Can customer journey trigger automation? It may be used in configured rules where supported, but the definition, data quality, entitlement, timing, exceptions and human responsibilities must be checked before reliance. ### How should we introduce customer journey to staff? Explain the definition with examples, show where it is recorded, state who can change it and make clear what action or report depends on it. ### Does the customer journey definition confirm the configuration in a 121 account? No. It explains public concepts using evidenced product building blocks. Live fields, permissions, workflows and plan availability require separate verification. ## Related CRM pages - [/crm/guides](https://121.direct/crm/guides) - [/crm/guides/what-is-a-crm](https://121.direct/crm/guides/what-is-a-crm) - [/crm/features/customer-management](https://121.direct/crm/features/customer-management) - [/crm/glossary/first-party-data](https://121.direct/crm/glossary/first-party-data) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.