Contacts
Gives a team one place to understand who a customer is and what has happened.
In practice
Amina can see who Jamie is, which organisation the enquiry belongs to and which service was requested before replying.
Feature · Customer management
Bring the details, conversations, open work and next action around each customer into one practical view. Your team still decides what matters, what is appropriate to record and what should happen next.
Contact workspace
A working record should make recent activity, ownership, permission context and next action visible without asking the team to hunt.
Northstar Joinery
FictionalSee every customer relationship in context
Move from a searchable contact list into a useful relationship record.
Jamie Clarke · jamie@example.test
Owner
Amina Rahman
Source
Website form
Stage
Discovery
Commercial state
Not recorded
Preferred contact
Email preferred
Next action
Confirm site-visit scope
Human decision
Amina Rahman confirms fit and records the outcome before the opportunity moves stage.
The relationship, joined up
The contact is the anchor. Conversations explain what was said; an opportunity represents the active piece of commercial work; tasks and appointments make responsibility and timing visible. None of them, alone, is “the customer”.
Gives a team one place to understand who a customer is and what has happened.
In practice
Amina can see who Jamie is, which organisation the enquiry belongs to and which service was requested before replying.
Helps a team see the customer history and coordinate replies from one working view.
In practice
Jamie’s reply about access constraints is visible beside the customer record instead of sitting only in a colleague’s inbox.
Shows which customer conversations are active commercial work rather than general contacts.
In practice
The Bramble Studio reception project sits at Discovery with Amina as owner; the contact record itself is not treated as the deal.
Makes booked work visible alongside the customer conversation and follow-up.
In practice
Once scope is agreed, the proposed site visit can sit with the customer rather than in an unlabelled diary entry.
Turns a repeatable customer process into a visible, reviewable flow.
In practice
A routine acknowledgement may be sent and a task created, but the workflow pauses when a reply changes the context or a person needs to assess fit.
One ordinary enquiry
Bramble Studio asks about a reception desk. The software can keep the records connected. Amina still decides whether the request fits, what should be promised and when a site visit is appropriate.
The human decision is part of the journey
It is not an awkward exception hidden after the automation has run.
Source and useful details are captured.
Contacts
New context appears in the conversation.
Conversations inbox
A relevant opportunity is created and owned.
Opportunities
A person confirms scope and suitability.
Contacts
The appointment is linked to the customer.
Appointments
A task or bounded workflow keeps the next action visible.
Workflow builder
Useful building blocks
Custom fields, saved views and labels can make a customer list easier to use. They also create maintenance work. The useful test is whether the structure supports a real decision, handover or follow-up.
Object-specific custom fields capture structured information that the team can search and reuse.
Example: Service interest and preferred contact method are useful; a vague free-text field for everything is not.
Smart Lists use saved filters and update as contact data changes, subject to permissions and the quality of those fields.
Example: The team can review enquiries with an overdue next action without maintaining a second list.
Duplicate-handling tools can support a controlled clean-up, but matching, merging and deletion rules still need a named owner and a checked process.
Example: If two records appear to belong to Jamie, a data owner checks the details before choosing what to merge or retain.
Decide who needs to view, edit, export and delete records. Then test those roles with representative users and non-sensitive sample data before real customer information is added.
Review data responsibilitiesBoundaries worth planning for
Imports, free-text notes, duplicate records and out-of-date fields still need rules and review.
Email, telephone, SMS and social messaging depend on connections, permissions, consent, provider behaviour and possible usage charges.
A workflow cannot repair an unclear process, recognise every exception or decide what is appropriate for a relationship.
Roles and permissions should be checked with representative users and sensitive records before the system becomes operational.
From record to action
The CRM can support routine routing while keeping qualification and sensitive decisions with a named person.
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
Questions about this page
It is the working record for a person or lead, with configured contact details, ownership and related activity. Depending on the verified setup, it may also link to conversations, tasks, opportunities and appointments.
Only messages from supported channels that have been connected and configured correctly. Channel access, sender identity, consent, delivery behaviour and usage costs must be checked before the inbox is relied on.
No. Contact tools can help the team find and manage records, but matching rules, imports and merges still need a responsible person. Review the records before combining or deleting anything.
HighLevel documents opportunities as potential deals associated with contacts, and tasks can be managed from contact and opportunity views. Your team still needs agreed stages, named owners and a clear rule for closing stale work.
Appointments can be linked to contacts, and configured workflows can respond to selected events. The calendar connection, triggers, actions, messages and stopping rules still need to be agreed and tested for your setup.
Agree which records are in scope, the lawful and useful fields to retain, how duplicates will be handled, who may access the data, how a sample will be checked and what evidence counts as an accepted migration.
The checkout confirms 121 CRM at £250/month (no VAT charged) with unlimited users. It does not list module access, connected services, usage charges or configuration work, so confirm anything material to your decision before subscribing.
Continue the journey
Delegate the work. Keep the human.
Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.
121 CRM
Your customers. Your conversations. Your business. Organised around clear ownership and human decisions.