# 121 CRM Features | Customers, Conversations and Follow-Up > Explore 121 CRM for customer records, pipelines, conversations, booking, follow-up, reporting and optional AI-assisted workflows. 121 CRM brings useful customer work into a clearer operating view. Capabilities still depend on configuration, permissions, connected providers and the scope you agree. ## Five views of one customer journey Illustrative grouping — not a statement that every optional capability is enabled. ## 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. ### Workflow builder Combines a start event with an ordered sequence of configurable actions. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Turns a repeatable customer process into a visible, reviewable flow. **Limitations:** Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service. **Human responsibility:** A process owner must approve, test, monitor and pause or correct faulty automation. ### Dashboards Combines supported widgets and filters into an operational view for ongoing monitoring. **How it works:** Aggregates eligible source data into configured dashboards, reports or exports. **Why a business would use it:** Helps a team review the few measures needed for the next decision. **Limitations:** A report reflects available source data and configuration; it does not prove causation or data completeness. **Human responsibility:** A person must interpret results, investigate gaps and decide what action is justified. ## Start with a usable customer and opportunity record. The record and pipeline should answer practical questions for the team without implying that software owns the relationship. ### Customer management Details, activity, tasks and relevant opportunities can be kept together. ### Sales pipelines Stages, owners and next actions make current work visible. ### Data quality Field choices, duplicates and source ownership remain operating responsibilities. ## Bring supported communication into an owned workflow. Where channels are configured, conversations can be assigned and followed up alongside the customer context. ### Conversations See messages that belong to supported, connected channels. ### Tasks and reminders Give routine follow-up an owner and a due point. ### Exceptions Route sensitive, uncertain or failed automation to a person. ## Optional capability needs evidence and a reason. Booking, workflows, reporting, reviews, AI and other connected tools should be tested and scoped before being described as part of your account. ### Configuration Confirm the intended workflow, plan availability and permissions. ### Cost Confirm usage and connected-provider charges before enabling them. ### Control Define approval, escalation, monitoring and change responsibility. ## Frequently asked questions ### Which CRM features should we start with? Start with the smallest set that fixes a visible customer or team problem: often a useful contact record, clear ownership and one agreed follow-up journey. Add more only when the first journey works. ### Can different features share the same customer context? They can where the records, permissions and connections are configured to work together. Keep each capability’s purpose clear so the team knows which view is authoritative. ### Will every feature be available immediately? Feature access and behaviour can depend on the selected plan, account settings, connected services and usage costs. Confirm the parts your business needs before relying on them. ## Related CRM pages - [/crm](https://121.direct/crm) - [/crm/demo](https://121.direct/crm/demo) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.