Tags vs fields vs pipelines: which one to use for what

Use a field for something every customer has and that changes what you do (phone, branch, consent, insurance plan). Use a tag for a group you want to find later (maintenance plan, VIP, referred by a dentist). Use a pipeline only for something that moves through stages over time and needs a next action at each one (a lead becoming a customer; a large project). The mistake is using the wrong one: a tag for a fact, a field for a group, a pipeline for everything.

Fields

A field has one value per customer and the value means something. Mobile number. Home branch. Insurance plan. Preferred provider. Consent status. If the value would change how the AI replies or how the front desk books, it is a field. If it is empty on most records, it is not a field; delete it.

Fields are for filtering exactly ("everyone at the Northgate branch with marketing consent") and for the AI and the front desk to read at a glance.

Tags

A tag is a label you put on some customers and not others, to find them as a group. "Maintenance plan." "Referred by Dr Patel." "Prefers text." "Do not book with Sam." A customer can have several. Tags are cheap to create, which is their strength and their problem: a tag list nobody prunes becomes forty labels with overlapping meanings.

Rules: one person owns the tag list. Every tag has a sentence saying what it means. Tags with fewer than ten customers after a year get reviewed. And a tag that is really a fact ("Delta insurance") becomes a field.

Pipelines

A pipeline is a sequence of stages with a next action at each. For most service businesses, one pipeline is enough: the lead pipeline (new, contacted, booked, converted, lost). A kitchen remodeller or a law firm may want a project pipeline (consult, estimate, signed, in progress, done). A dental office does not need a pipeline for cleanings.

Pipelines are expensive: every stage needs someone to move things, and stale pipelines are worse than none. If a stage has items that have not moved in a month, the pipeline is not being used and the report is lying.

The rule for choosing

Ask: does every customer have this? Field. Do I want to find a group with this? Tag. Does this move through stages and need a next action? Pipeline. If none of the three, it is a note on the timeline.

Examples

"Has a dog named Biscuit": a pet record (a structured field group), or a note if the system has no pet fields.

"Interested in whitening": a tag, or an interest the AI records, for a campaign later (with marketing consent).

"Prefers mornings": a note, or a tag if you will filter by it.

"Deposit on file": a field, because it changes the booking flow.

"Enquired about a full-mouth restoration, estimate sent, deciding": a lead in the pipeline with a next action.

Where automation helps

Fields can be filled from what customers type (a new number, a branch they mention). Tags can be suggested when a customer says something that matches a tag's meaning. Pipelines can move a lead on its first reply or its first booking. Check which of these your CRM actually does before relying on any of them, and have a person confirm anything the software inferred.

Frequently asked questions

Can a tag have a value?

If it needs one ("plan: gold"), it is a field. Tags are on or off.

How many tags is too many?

More than the front desk can remember the meaning of. Twenty is a lot for a single-location business.

Should leads and customers be separate pipelines?

Leads move through the lead pipeline and become customers. Customers do not need a pipeline unless you sell multi-stage projects.

What Frontiva does here

Frontiva's CRM has tags, custom fields you define once, and a lifecycle stage on every contact, and lead management has configurable pipelines that ship with New, Contacted, Qualified, Appointment Booked, Proposal, Won and Lost. Moving a lead to Won marks the contact a customer. See the fields a service business needs for the field list.