CRM
Client Status Examples for Service Businesses
Use practical client status examples for service businesses, with simple lifecycle models for new, active, repeat, inactive and archived clients.
Overview
A client status should answer one operational question:
What kind of relationship do we currently have with this person, and what should the team understand at a glance?
It should not try to summarize every appointment, payment, note and marketing preference in one label.
For most service businesses, five to seven clear statuses are more useful than a giant CRM taxonomy nobody uses consistently.
This guide shows practical client-status models for appointment businesses, project services and small teams, plus the important difference between a client status, booking status, note and tag.
Client status vs booking status vs note vs tag
These fields solve different problems.
Client status
Describes the relationship with the person or account over time.
Examples:
- New
- Prospect
- Active
- Returning
- Inactive
- Archived
Booking status
Describes one appointment.
Examples:
A client can be Active while one specific appointment is Cancelled. Do not change the entire client relationship to “Cancelled.”
- Pending
- Confirmed
- Completed
- Cancelled
- No-show
Payment status
Describes money attached to an appointment or order.
Examples:
A client is not a “Paid client” forever just because one invoice was settled.
- Awaiting payment
- Partially paid
- Paid
- Refunded
Note
Stores useful context that does not belong in a lifecycle label.
Example:
Prefers weekday mornings. Asked to keep the next appointment under 60 minutes.
Tag
Groups clients by a useful property, segment or operational attribute when the CRM supports tags.
Examples:
A tag should not replace the main lifecycle status.
- Bridal
- Corporate
- Piano
- Monthly
- Referred by partner
First decide whether one client can have more than one lifecycle label
Some CRMs allow one lifecycle status at a time. Others can combine a main status with tags, attributes, segments or calculated repeat-client flags.
If your system allows only one lifecycle status, keep those statuses mutually exclusive. A clean model is usually:
New / Prospect → Active → Inactive → Archived
In that model, Returning is often better treated as a repeat-client tag, attribute or reporting concept while the relationship can still remain Active. Use Returning as a single-valued status only if your team deliberately defines it as a mutually exclusive lifecycle stage.
This matters because “Active” and “Returning” can both be true at the same time in ordinary language. Do not force overlapping meanings into a field that accepts only one value.
A simple six-label model for service businesses
If your system can represent a main lifecycle state plus repeat-client context, this is a practical baseline. If it accepts only one status, use the mutually exclusive lifecycle states above and keep Returning separate.
1. New
Use for a person who has just entered the system and has not yet developed a clear client history.
Typical triggers:
Possible next statuses:
- first enquiry;
- first record created;
- first booking created but not yet completed.
- Prospect;
- Active;
- Archived, if the record was created by mistake or is no longer relevant.
2. Prospect
Use for someone who is considering a service but has not yet become a completed-service client.
Examples:
Do not leave someone as “Prospect” forever after they complete a service.
- requested information;
- submitted an enquiry;
- had a consultation;
- asked for availability;
- requested a quote.
3. Active
Use for someone with an ongoing current relationship.
Examples:
“Active” should mean something operational. Define it for your business.
- has an upcoming appointment;
- is in an active project;
- is receiving a multi-session service;
- is currently in a working engagement.
4. Returning
Use when the customer has completed more than one meaningful service or has returned after the first engagement.
This is useful for businesses where repeat behavior matters, such as:
Do not use Returning as a compliment. Make the definition objective.
Example definition:
Returning = at least two completed appointments or a new completed engagement after the first.
- salons;
- tutors;
- photographers with repeat families or brands;
- consultants;
- coaches;
- pet groomers;
- detailers;
- wellness businesses.
5. Inactive
Use when the client has had a real relationship with the business but is no longer active.
The threshold should match the service cycle.
A haircut business, annual photographer and project consultant should not share the same 60-day inactivity rule.
Define inactivity based on expected return behavior, for example:
- no future booking and past expected return window;
- project completed and no current engagement;
- account dormant after an agreed period.
6. Archived
Use for records you no longer want in the active working view but still need to retain according to the business’s operational or legal requirements.
Examples:
Archive is usually better than deleting useful history.
Do not use Archived as a punishment label.
- old inactive relationship;
- duplicate resolved into another record;
- record no longer relevant to day-to-day work;
- customer relationship ended.
A five-status model for appointment businesses
For a salon, barber, beauty professional, tutor, groomer or other repeat appointment service:
If your CRM accepts only one status, keep Active as the lifecycle state and represent Returning separately as a tag, attribute or reporting flag. The table is a vocabulary model, not a requirement to make overlapping labels mutually exclusive.
This model is small enough that staff can actually use it.
| Status | Meaning | Example rule |
|---|---|---|
| New | First relationship beginning | No completed appointment yet |
| Active | Current/upcoming relationship | Future appointment or recently active |
| Returning | Repeat customer | 2+ completed appointments |
| Inactive | Past customer outside expected return window | No future booking and return interval passed |
| Archived | Removed from normal active workflow | Old/duplicate/closed record |
A six-status model for consultants and project services
Project work needs a slightly different lifecycle.
Be careful with Qualified if your CRM does not support a true sales pipeline. For a small service business, New → Active → Past may be enough.
| Status | Meaning |
|---|---|
| Lead / Prospect | Considering the service |
| Qualified | Good fit and actively discussing work |
| Active | Project or engagement is underway |
| Past client | Project completed, relationship still valuable |
| Returning | New engagement after previous completed work |
| Archived | No longer in the working pipeline |
A status model for a solo service business
Solo operators often need less structure, not more.
Use:
New → Active → Returning → Inactive → Archived
That covers most of the client lifecycle without turning the CRM into a second job.
If enquiries are important, add Prospect before Active.
How to define each status so the team uses it consistently
A status name is not enough. Give each one a trigger.
Bad definition:
Active = good client.
Better definition:
Active = client with an upcoming appointment or a service completed within the current normal return window.
Bad definition:
VIP = best customers.
Better approach:
If VIP treatment is genuinely part of the operation, define the criteria as a tag or program rule rather than a subjective status.
Use observable criteria
Good criteria include:
Avoid status rules based on staff feelings.
- number of completed appointments;
- future booking exists;
- project is open;
- expected return interval;
- last completed service date;
- engagement closed;
- record archived.
Status examples by business type
Salon or beauty studio
A practical setup:
Example:
A customer books a first color appointment → New. They complete the appointment and book maintenance → Active. They return for another completed visit → Returning. They stop booking beyond the expected return interval → Inactive.
- New
- Active
- Returning
- Inactive
- Archived
Photographer
Possible statuses:
But remember: Booked may be better stored as a booking/project state rather than a client status if the system already models bookings separately.
A cleaner client model may be:
- Enquiry
- Booked / Active
- Past client
- Returning
- Archived
- Prospect
- Active
- Past
- Returning
- Archived
Tutor or music teacher
Possible statuses:
If the student has weekly lessons, “Active” can mean an ongoing current teaching relationship.
Do not overload the client status with lesson attendance. Attendance belongs to individual sessions.
- Prospect
- Active
- Returning/continuing
- Inactive
- Archived
Consultant or coach
Possible statuses:
If you need to track proposal stages such as discovery, proposal sent and negotiation, use a dedicated sales pipeline when available rather than turning every proposal stage into a client status.
- Prospect
- Active
- Past client
- Returning
- Archived
Pet groomer
Possible statuses:
Pet-specific attributes such as breed, coat, behavior or vaccination information should not be crammed into the client status. Specialized pet records are a separate data model.
- New
- Active
- Returning
- Inactive
- Archived
Auto detailing
Possible statuses:
Vehicle details belong in the appropriate service record, asset record or note structure, not the relationship status.
- New
- Active
- Returning
- Inactive
- Archived
When should a client become “Returning”?
Define it once.
Good options include:
Rule A: Returning after the second completed appointment.
Rule B: Returning after a new engagement begins following a completed first engagement.
Rule C: Returning when a customer books again after the expected service cycle.
Pick one rule and use it consistently.
Do not manually label favorite clients as Returning before they actually return.
When should a client become “Inactive”?
This is where many CRMs become misleading.
A universal “inactive after 30 days” rule makes no sense across services.
Instead, use the normal service rhythm.
Examples:
The status should reflect the business model rather than an arbitrary software default.
If you later create reactivation messages, use the same logic. Do not send “We miss you!” to someone whose normal return interval has not passed.
- a monthly treatment business may care after several expected cycles are missed;
- a quarterly service has a longer window;
- a wedding photographer may not expect another booking for years;
- a consultant may be a valuable past client even with no current engagement.
Do you need a “Do Not Contact” status?
Sometimes, but often this is better handled as a separate communication preference or suppression flag.
“Do not contact” is not necessarily the lifecycle relationship. A customer can be an active client and still opt out of marketing messages.
Keep consent, marketing preferences and required transactional communication separate from general client status where your tools support that separation.
Never use sensitive personal traits as lifecycle statuses.
Do you need a “VIP” status?
Usually not as the main lifecycle state.
VIP often means one of several different things:
Those should not be silently mixed together.
If the business has a real membership or priority program, represent it with a defined field or tag. Keep the lifecycle status focused on the relationship stage.
- high lifetime value;
- membership;
- frequent visits;
- priority service;
- personal preference;
- staff favorite.
How to clean up an existing status mess
If your CRM already has 25 inconsistent labels, do not keep adding more.
Step 1: Export or review the current list
Collect every status actually in use.
Step 2: Group synonyms
Examples:
- Current, Open, Working → Active
- Repeat, Regular, Loyal → Returning
- Dormant, Cold customer, Old → Inactive
- Closed, Finished, Historical → Past/Archived depending on the model
Step 3: Separate non-status information
Move these out of lifecycle status when possible:
- booking state;
- payment state;
- source;
- service type;
- staff assignment;
- location;
- membership;
- marketing consent.
Step 4: Define the new taxonomy
Write one sentence for each allowed status.
Step 5: Map old statuses to new ones
Do not delete history blindly. Keep a migration record if the data matters operationally.
Step 6: Train the team with examples
Give staff five real examples and ask which status each client should have. If answers differ, the definitions are still too vague.
A compact status policy you can copy
New: client record created, no completed service yet. Prospect: actively considering or discussing a service, no completed service yet. Active: current relationship with an upcoming appointment or open engagement. Returning: client has completed more than one engagement according to our repeat-client rule. Inactive: previous client with no current engagement and outside the normal expected return window. Archived: record removed from the normal active workflow but retained as appropriate.
Delete Prospect if your business does not need a pre-client stage.
How statuses connect to reporting
A clean client-status model can support useful operational questions:
Do not treat the status field as a perfect analytics model by itself. Completed bookings, actual revenue, booking source and service history are usually stronger measures for performance.
- How many active clients do we have?
- How many clients return?
- How many past clients are currently inactive?
- Are we growing through new clients or repeat clients?
- Which clients have upcoming activity?
- Which records should be archived from the daily working view?
How OneStudio fits into the workflow
OneStudio’s public website states that contacts, history, notes and client statuses stay together in the CRM area. The current public experience also shows example statuses such as Active and Returning, and the Features page lists client records, notes/tags, booking history and client archive capabilities.
That supports a simple service-business lifecycle model.
However, OneStudio should not be described as allowing arbitrary custom status creation, automatic lifecycle transitions, lead scoring, enterprise deal pipelines or status-triggered campaigns unless those capabilities are separately verified.
For publication, frame the guide as a practical taxonomy businesses can adapt to the status options their system actually supports.
CTA
Keep client context, bookings and day-to-day history easier to understand. Explore how OneStudio connects client records with appointments, notes and the wider business workflow.
Questions businesses ask
What are common client statuses in a CRM?
For service businesses, a simple set can include New, Prospect, Active, Returning, Inactive and Archived. Not every business needs all six.
What is the difference between Active and Returning?
Active describes a current relationship. Returning describes repeat behavior. Because both can be true at once, a single-status CRM should usually keep Active as the lifecycle state and represent Returning as a tag, attribute or reporting concept.
Is Cancelled a client status?
Usually not. Cancelled describes an appointment, not the entire client relationship.
Is Paid a client status?
Usually not. Paid describes the payment state of a transaction, booking or order.
When should I mark a client inactive?
When they no longer have a current engagement and have moved beyond the normal expected return interval for the service. Define the rule based on your business rather than an arbitrary universal number of days.
Should I delete inactive clients?
Not automatically. Archive may be more appropriate when you need to retain legitimate business history. Follow the data-retention and privacy requirements that apply to your business.