Solution · Dental practices

Organise non-clinical enquiries and booking while clinical judgement stays clinical.

A CRM may support new-patient enquiries, appropriate reminders and non-clinical follow-up. It is not the clinical record, does not decide treatment and should not invite unnecessary health information into general channels.

Subscribe to 121 CRM Seller, billing and cancellationExplore appointments

Customer Thread

A bounded new-patient enquiry

Illustrative example

Enquiry
Front desk
Booking
Clinical boundary
Follow-up

Enquiry
Contact and general need
Front desk
Identity and route checked
Booking
Appropriate slot offered
Clinical boundary
Care decisions stay with clinicians
Human decision
Follow-up
Administrative action recorded

Illustrative non-clinical workflow. No clinical-system integration or patient outcome is claimed.

Non-clinical appointment journey

Coordinate the administrative path around a clear clinical boundary.

The example demonstrates availability and reminders while explicitly excluding diagnosis, treatment and clinical 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

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

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 05

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 use it: Turns a repeatable customer process into a visible, reviewable flow.
Plan for: Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns: A process owner must approve, test, monitor and pause or correct faulty automation.

Practice journey

Support the administrative work around care.

Recall, missed-call and post-visit workflows all need to be separated from unverified instant-response, clinical and outcome claims.

New-patient enquiry

Record contact details, general reason for contact, source, owner and next administrative action.

Appointment coordination

Where configured, link appropriate availability, confirmation, reminder and change handling to the enquiry.

Administrative follow-up

Keep agreed non-clinical tasks visible without placing clinical notes or treatment decisions in the CRM.

Sensitive boundary

Do not turn a general CRM into an accidental clinical channel.

Form fields, messages and staff practice should actively discourage unnecessary sensitive information.

Outside CRM

Clinical information

Use the approved clinical system and professional process for symptoms, diagnosis, treatment and clinical history.

Identity and disclosure

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

Human clinical decision

Urgency and exceptions

General automated messages must not triage emergencies or substitute for clinical assessment.

Sensitive-data boundary

Keep information in the appropriate system and role.

General CRM access and communication must not become an accidental clinical channel.

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.

Implementation questions

Confirm systems, permissions and wording before go-live.

Dental workflows often involve practice-management systems, calendars and sensitive communications with distinct responsibilities.

System of record

Name where patient identity, appointments and clinical information are authoritative.

Integration and sync

Do not imply practice-system or calendar connectivity until objects, direction, duplicates and failures are tested.

Messages and reviews

Approve reminder and feedback wording, consent basis, timing, platform rules and human response ownership.

Questions about this page

Useful answers, without the sales fog.

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

No. This page concerns non-clinical enquiry, booking and relationship workflows. Clinical records and treatment decisions stay in appropriate systems and professional processes.

2. Can it send appointment reminders?

Reminder workflows may be configured where the calendar, channel, identity, consent, wording and usage terms are approved and tested.

3. Can it manage recalls?

No recall programme is promised here. The data source, clinical or administrative responsibility, eligibility, messaging and integration would require specific review.

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