Solution · Health and wellness businesses

Organise non-clinical customer work without turning the CRM into a care record.

Studios, salons, wellbeing services and regulated providers may need enquiry, booking and relationship follow-up. The appropriate boundary depends on the service: clinical information, assessment, treatment and urgent needs belong in approved professional systems and processes.

Subscribe to 121 CRM Seller, billing and cancellationReview security and data

Customer Thread

A bounded enquiry and booking journey

Illustrative example

Enquiry
Identity
Booking
Boundary
Follow-up

Enquiry
General service question
Identity
Appropriate details checked
Booking
Suitable slot offered
Boundary
Professional decision retained
Human decision
Follow-up
Administrative action

Illustrative non-clinical workflow. No clinical-system integration, care decision or outcome is claimed.

Non-clinical appointment journey

Coordinate the booking while professional judgement stays outside the CRM.

The view demonstrates administrative availability and reminders without representing clinical suitability, treatment or care records.

121

Northstar Joinery

Fictional

Make appointments easier to organise

OverviewContactsCalendarAppointmentsAutomation

Make appointments easier to organise

Coordinate availability, appointment status and the follow-up owner.

Mon

10:00

Discovery call

Rowan & Co

Tue

09:30

Site survey

Oakfield Homes

15:00

Drawing review

Marlow Works

Wed

Thu

11:30

Discovery call

Bramble Studio

Fri

13:00

Installation check

Field & Form

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

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 03

Appointment reminders

Uses configured notifications or workflows around booking, rescheduling, cancellation and attendance events.

How it works: Applies configured availability, booking rules and connected-calendar settings to eligible appointments.
Why use it: Keeps customers and staff informed without relying on a person to send each reminder manually.
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

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

Non-clinical journey

Coordinate the administrative work around a clear service boundary.

A CRM may support general enquiries, availability, reminders and appropriate relationship communication without becoming the authoritative clinical or treatment system.

Enquiry and ownership

Capture contact details, general service interest, source, owner and the next administrative action.

Booking coordination

Where configured, offer appropriate availability, confirmation, changes and reminders with a visible exception route.

Relationship follow-up

Use approved non-clinical messages for relevant updates or rebooking, subject to customer preference and professional policy.

Sensitive-information boundary

Collect less, route carefully and keep care information in the right place.

Generic forms, messages and automations should not invite symptoms, diagnoses, treatment history or other sensitive detail without an approved need and system.

System of record

Name the approved system for clinical, treatment, assessment, consent and other regulated records.

Identity and disclosure

Verify identity and communication preference before sharing appointment or personal information.

Human professional decision

Clinical and professional judgement

Diagnosis, suitability, urgency, treatment and safeguarding remain with qualified people and approved procedures.

Sensitive-information boundary

Keep care information in the approved professional system.

The responsibility chain makes data minimisation, access and escalation visible around the general customer workflow.

121 CRM · Data responsibility chain

Customer

Lawful inputs, users, instructions and acceptance

121

Agreed configuration, access handling and documented boundaries

Connected supplier

Service operation, account terms and supplier controls

Access follows named roles

Changes retain evidence

Assurances need approval

Illustrative exampleConceptual responsibility view, not a published certification or exhaustive data-flow diagram.

Safety and consent

Routine communication needs a clear stop and escalation path.

An administrative workflow must not imply emergency coverage or interpret a health-related reply.

Urgent language

State the appropriate emergency or urgent route for the service; do not let automated messaging triage or reassure.

Channel choice

Use only approved channels and wording for the type of information, with opt-out and preference handling.

Failed or unusual replies

Stop the routine sequence and route ambiguity, distress, complaint or sensitive content to an authorised person.

Implementation questions

Confirm the service model, connections and evidence before go-live.

The risk profile varies significantly between a fitness studio, salon, wellness provider and regulated clinical service.

Sector and data review

Document the service, professional duties, lawful basis, data classes, retention and prohibited CRM content.

Calendar or practice system

Verify the objects, direction, authority, duplicates, failure path and supplier responsibilities for each proposed connection.

Reviews and marketing

Approve testimonial, before-and-after, sensitive targeting and review-request practice against professional and platform rules.

Questions about this page

Useful answers, without the sales fog.

1. Is 121 CRM a clinical or practice-management system?

No such claim is made. It is presented here for non-clinical enquiry, booking and relationship work; clinical and regulated records belong in the approved professional system.

2. Can health and wellness customers receive appointment reminders?

Potentially, where the calendar, channel, timing, wording, consent and exception handling are configured and tested. Keep the reminder administrative and route sensitive replies to the right person.

3. Can customers describe symptoms in a form or message?

General CRM channels should discourage unnecessary sensitive information. The service should provide an approved route for clinical or urgent matters and ensure staff know how to handle accidental disclosure.

4. Can it automate treatment or suitability decisions?

No. Clinical, professional, safeguarding and treatment decisions stay with appropriately qualified people and approved systems.

Read all CRM questions

Continue the journey

Appointment workflows Security and data responsibilities Customer conversations

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