# CRM Solutions by Business Type | 121 CRM

> Explore CRM journeys for small businesses, dental practices, law firms, accountants and trades, grounded in real operational needs.

A dental practice, law firm, accountancy practice and trade business may all use contacts and pipelines. The useful differences are in the enquiry, booking, acceptance, sensitivity and follow-up decisions around them.

## One platform, different responsibility points

Sector examples describe operating patterns, not preconfigured packages or guaranteed outcomes.

## 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.

### 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.

### 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.

## Look for the work pattern that resembles your business.

The pages below focus on recognisable operating moments rather than dressing the same feature list in different sector language.

### Growing small businesses

Create shared ownership across enquiries, customer conversations, appointments and follow-up.

### Professional practices

Organise intake and relationship work while keeping acceptance, conflicts, advice and professional judgement outside routine automation.

### Appointment and field services

Connect booking or site work to clear customer communication and the next operational action.

## Every useful setup still needs the same basic disciplines.

Sector language does not remove the need for clear data, ownership, permissions and acceptance.

### Relevant records

Collect only useful customer and enquiry context, with additional care for sensitive or regulated information.

### Named owners

Give each active enquiry, conversation or appointment an appropriate person and next action.

### Bounded workflows

Automate routine movement only after exceptions and professional or clinical decisions are clearly excluded.

## A sector page is a starting point, not an implementation specification.

The final design depends on the business model, existing systems, team roles, service risk and commercial scope.

### Map the real journey

Use representative enquiries and customer cases to define stages, hand-offs and useful evidence.

### Check connections

Review calendars, practice systems, accounting tools, forms and communication routes separately.

### Agree acceptance

The customer approves the configured workflow, limitations and responsibilities before operational use.

## Frequently asked questions

### Is there a different CRM product for each sector?

These pages describe sector-specific operating journeys within 121 CRM. They do not claim a separate preconfigured product or included package for every sector.

### Can 121 copy our current process exactly?

Not automatically. Existing steps should be reviewed for purpose, data, ownership and risk before deciding what to retain, simplify or configure.

### What if our sector is not listed?

Start with the CRM overview and map the enquiry-to-next-action journey. A new sector page is not required to assess whether the core operating model fits.

## Related CRM pages

- [/crm](https://121.direct/crm)
- [/crm/solutions/small-business](https://121.direct/crm/solutions/small-business)

This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.