CRM and contacts

Tags and Segments for Contact Lists: A Practical Guide

How to use tags and rule-based segments to build call lists that make sense: naming rules, when to tag, how segments differ and how to keep both tidy.

Call editorial team · Published · 5 min read

Every phone team ends up needing to answer a question like "who should we call this week?" The answer is a list, and the quality of the list depends on how well the contacts are described. Tags and segments are the two main tools for that. They sound similar and are often confused, which leads to messy tagging and lists that nobody trusts. This guide explains the difference, when to use each and how to keep both under control.

A team lead filtering a contact list by rules on a screen
Illustrative image

It is part of the CRM series; for the base data, read Keeping CRM Data Clean. For the outbound side, see Keeping Outbound Call Lists Healthy and Managing Opt-Outs.

Tags and segments: what is the difference?

Tags versus segments

TagsSegments
What it isA label attached to a contactA saved list defined by rules
Who creates itAnyone, by hand, during or after a callA manager or planner, from rules
UpdatesOnly when someone changes itUpdates itself as contacts change
SuitsFacts learned in conversationRepeatable lists for campaigns
RiskInconsistent namesRules that catch the wrong people

A simple way to remember: a tag is something you know, a segment is something you ask. A tag says "asked for a callback after the holiday". A segment says "all contacts in the Qualified stage, in this country, with no call in two weeks". Tags can feed segments, but the segment is the thing you call from.

Designing tags that stay useful

Tags are easy to create and easy to ruin. Within a few months a free-for-all produces "vip", "VIP", "very important" and "v.i.p." as four different tags. Prevent it from the start.

Building segments from rules

A segment is a saved question. Each rule has a field, a condition and a value, such as country is a given country, stage is a given stage, deal value is more than a figure, or attempts so far is at most three. All rules must match. The skill is in choosing rules that describe the people you actually want, and no more.

Building a segment safely

  1. Define the goalWho do you want to reach, and why now?
  2. Choose rulesField, condition and value, one at a time.
  3. PreviewCheck the count and a handful of example names.
  4. AdjustTighten or loosen rules until the list makes sense.
  5. Save and nameUse a name that says what it is and who owns it.
  6. Use and reviewCheck results after the campaign.

Always look at the count and the examples before using a segment. A rule with a typo, a field that is blank for half your contacts or a condition that is too loose can put thousands of the wrong people on a list. Seeing the count as you build means you notice at once.

Segments phone teams commonly need

A hypothetical example

Imagine a regional training provider that calls past enquirers about new courses. Agents tag contacts during calls with interest-based tags such as "interest-evening-classes" or "asked-for-brochure". A planner then builds a segment: stage is Contacted or Qualified, tag-based interest recorded, country is the home country, attempts so far at most two. The preview shows several hundred contacts and a list of example names; the planner spots that a few belong to a company that has asked not to be called, fixes the exclusion and saves the segment as "Evening classes follow-up, spring".

The tags came from conversations; the segment came from a question. Neither could do the other's job. And because the planner looked at the preview, the mistake was caught before a single call was made.

Exclusions and compliance

Every segment used for outbound calling must exclude people who must not be called. That means do-not-call lists, people who have opted out, and anyone who has not given the consent your rules require. Build the exclusion into the process, not into each segment by hand, so that it cannot be forgotten. Check calling-hours rules for the countries on your list.

One more habit worth building is retiring segments after a campaign. A segment named for a spring promotion that is still in the list in autumn invites someone to use it by accident. Archive or delete finished segments, and keep the results of the campaign somewhere you can find them. The aim is a small collection of lists that each have a clear job.

Document the rules in one shared place so a new team member can see what each tag means and how each segment is built. A one-page guide with examples saves hours of questions and keeps the habit consistent as the team grows.

Keeping tags and segments tidy

Like any shared tool, these need an owner. Give one person the job of reviewing tags and segments each quarter. They should merge duplicate tags, delete unused segments, rename vague ones and note which are tied to active campaigns. Write a one-line purpose for each segment; if nobody can say what it is for, it should go.

Quarterly tag and segment review

  • Tag list reviewed and duplicates merged
  • Naming convention followed
  • Unused tags and segments removed
  • Each segment has an owner and a purpose
  • Exclusions confirmed for do-not-call and opt-outs
  • Segment counts checked against expectations
  • Results of recent campaigns compared with their segments

Tags and segments in Call

In Call, a contact page lets you add a tag with an Add a tag box that suggests the tags already used in your organisation; a small cross removes one. The Prospects list can be searched by name, company, phone or email and narrowed by stage, and exported to CSV for the current search and stage.

For rule-based lists, the Segments tab under Outbound ops lets you build a segment from rules. Choose a field (country, city, industry, stage, tier, source, deal value, company, job title or attempts so far), a condition (is, is not, contains, more than, less than, at least, at most) and a value, add more rules, and optionally limit the segment to one campaign. The count of matching contacts and example names update as you type, so a list is not saved without someone having seen who it catches. Saving and removing segments needs the admin or manager role. In Dialling hygiene, managers can rest contacts for a number of days instead of discarding them, and they return when the rest is over.

Frequently asked questions

Should I use tags or segments?

Use tags for facts learned by hand and segments for repeatable lists defined by rules. Many teams use tags as one of the inputs to a segment.

How many tags are too many?

If agents cannot remember them or you cannot say what each is for, there are too many. A short approved list works better than a long free-for-all.

Why should I preview a segment?

Because a small mistake in a rule can add many wrong contacts. The count and example names let you catch it before anyone is called.

Do segments update themselves?

Rule-based segments are defined by rules, so the people who match can change as contact details change. Check a segment before each campaign.

How do I keep do-not-call contacts out?

Exclude them as a standing step in your process, not just in each segment, and check the list before every campaign.

Who should manage tags and segments?

One named owner who reviews them regularly, supported by agents who follow the naming rules.

Build a segment from rules and preview the count in Call

In the demo console you can try incoming calls in a simulation.

Related guides