Solution · Law firms

Keep enquiries and consultations visible while acceptance remains a professional decision.

A CRM can organise first contact, ownership, consultation booking and appropriate follow-up. It must not treat an enquiry as a client, perform conflict clearance or automate legal judgement.

Subscribe to 121 CRM Seller, billing and cancellationExplore conversations

Customer Thread

From enquiry to an acceptance decision

Illustrative example

Enquiry
Owner
Conflict route
Acceptance
Consultation

Enquiry
Basic matter context
Owner
Intake responsibility
Conflict route
Approved process invoked
Acceptance
Authorised person decides
Human decision
Consultation
Next step recorded

Illustrative intake workflow. It does not create a solicitor-client relationship or perform conflict checks.

Enquiry and consultation context

Keep the first contact owned without implying acceptance.

The conversation view supports intake coordination while conflict checking, scope and engagement remain professional decisions.

121

Northstar Joinery

Fictional

Keep customer messages together

OverviewContactsInboxPipelineAutomation

Keep customer messages together

See the message, customer context and responsible owner in the same working view.

Search inbox

Bramble Studio

Jamie Clarke · Email

Contact confirmed

Could Thursday morning work for a short discovery call?

09:54

Yes — 11:30 is available. I can send the appointment details once the scope is confirmed.

10:02

Thursday morning would work well. Thank you.

10:24

Write a reply…

Illustrative 121 interfaceAll people, organisations, dates and activity are fictional. Any figures are illustrative. Controls demonstrate interaction patterns, not enabled account features.

The working building blocks

Use the CRM where it improves the working day.

The same core capabilities can support different sectors, but the data, permissions, professional boundaries and handovers need to reflect the business using them.

Capability 01

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 use it: Gives a team one place to understand who a customer is and what has happened.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 02

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 use it: Helps a team see the customer history and coordinate replies from one working view.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 03

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 use it: Makes booked work visible alongside the customer conversation and follow-up.
Plan for: Sync, meeting-link and resource behaviour varies by calendar type and external provider.
Your team owns: Staff must handle exceptions, incorrect availability and bookings that need judgement.

Capability 04

Tasks

Creates assigned, dated and optionally recurring actions against contacts or opportunities.

How it works: Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it: Turns the next step into owned work instead of leaving it inside notes or inboxes.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Capability 05

Users, roles and permissions

Controls whether a user acts at agency or sub-account level and which supported areas they can access.

How it works: Controls agency or sub-account configuration that determines access, packaging, governance or billing.
Why use it: Limits day-to-day access to the work a person actually needs to perform.
Plan for: Availability and control depth depend on agency plan, role and current account configuration.
Your team owns: An authorised administrator must review, approve and audit material changes.

Intake journey

Make the first contact organised without overstating what it means.

The reference focuses on after-hours response and consultation booking. 121 makes status and professional boundaries explicit.

Capture the enquiry

Record appropriate contact details, broad matter type, source and responsible intake owner.

Coordinate the consultation

Where approved, connect availability, confirmation and reminders without implying the matter has been accepted.

Follow up appropriately

Keep an agreed next action visible while avoiding automated legal advice or pressure.

Professional boundary

Conflicts, scope and client acceptance stay outside routine automation.

The CRM may show that a decision is required; it should not make or conceal that decision.

Human professional decision

Conflict process

Use the firm’s approved conflict-checking procedure and authoritative systems before acceptance.

No relationship by implication

Acknowledgements and booking messages should not imply advice, confidentiality terms or formal engagement beyond approved wording.

Sensitive information

Limit early intake fields and route confidential or high-risk information to the firm’s approved process.

Acceptance gate

Stop routine movement at the professional decision.

The CRM may expose that a decision is due; it does not perform conflict clearance or accept a client.

121 CRM · Workflow sequence

Enquiry received

Capture source and customer

Acknowledgement

Set a clear response expectation

Human review

Check fit, consent and exceptions

Owner assigned

Name the person responsible

Follow-up due

Remind the owner, not the customer blindly

Illustrative exampleA conceptual workflow. Triggers, messages, delays and exceptions need configuration and testing.

Operating control

Define hand-offs between CRM, practice systems and people.

Account ownership, data transfer and post-acceptance responsibilities need a documented boundary.

System of record

Name where matter, client, conflict and legal-work information becomes authoritative.

Permissions

Restrict enquiry and client information according to role, matter sensitivity and firm policy.

Separate tool

Optional diagnostic

The separate Law Firms Toolkit can help review governance or operating questions; using it does not provision or assess this CRM.

Questions about this page

Useful answers, without the sales fog.

1. Does the CRM perform conflict checks?

No such capability is claimed. It may record that an approved conflict process is required, but authorised people and firm systems remain responsible.

2. Can it book consultations?

A consultation journey may be configured after availability, wording, status, reminders and exceptions are agreed. A booking does not imply client acceptance.

3. Is the Law Firms Toolkit part of the CRM?

No. It is a separate 121 diagnostic and governance surface. A link is provided only as an optional resource and does not purchase, provision or validate the CRM.

Read all CRM questions

Continue the journey

Customer conversations Security and data responsibilities Open the separate Law Firms Toolkit

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing