Contact Segmentation & Tagging Scheme

Use this when your CRM is getting messy: duplicate tags, inconsistent names, and automations that fire on the wrong people. Copy the core tag list and naming rules below, swap the example products, channels, and deal-size bands for your own, then build a few example segments to power your follow-up and routing. A consistent scheme pays off the moment you start filtering, reporting, or triggering automations.

Format
Editable doc
Length
6 sections · ~2 pages
Price
100% free
Setup
Copy or deploy

Copy the whole template, or grab a single block below.

Get started free
4.9·Free · No signup · Copy-paste ready
Connects toWebsiteWhatsAppTelegramInstagram
CRM

Contact Segmentation & Tagging Scheme

Tag naming rules

Format: prefix:value, all lowercase, words joined by hyphens.

Use a fixed prefix per category: stage:, source:, interest:, value:, status:.

Examples: stage:lead, source:whatsapp, interest:onboarding, value:high.

One concept per tag. Never combine two, so avoid tags like hot-whatsapp-lead.

No spaces, no emojis, and no personal names inside tags.

Pick singular over plural and stick to it: use interest:demo, not interest:demos.

When in doubt, extend an existing prefix instead of inventing a new one.

Lifecycle stage tags

stage:subscriber (opted in, not yet qualified)

stage:lead (showed interest, basic info captured)

stage:qualified (fits your ideal-customer criteria)

stage:opportunity (active deal or quote in progress)

stage:customer (has purchased or booked)

stage:churned (lapsed or canceled, kept for win-back)

Rule: a new stage replaces the old stage tag, it never stacks.

6 ready-to-use sections

1

Tag naming rules

When to use: Set these conventions first so every tag stays consistent and machine-readable, no matter who adds it.

Format: prefix:value, all lowercase, words joined by hyphens.

Use a fixed prefix per category: stage:, source:, interest:, value:, status:.

Examples: stage:lead, source:whatsapp, interest:onboarding, value:high.

One concept per tag. Never combine two, so avoid tags like hot-whatsapp-lead.

No spaces, no emojis, and no personal names inside tags.

Pick singular over plural and stick to it: use interest:demo, not interest:demos.

When in doubt, extend an existing prefix instead of inventing a new one.

2

Lifecycle stage tags

When to use: Apply exactly one stage tag per contact to track where they are in your funnel and keep automations from overlapping.

stage:subscriber (opted in, not yet qualified)

stage:lead (showed interest, basic info captured)

stage:qualified (fits your ideal-customer criteria)

stage:opportunity (active deal or quote in progress)

stage:customer (has purchased or booked)

stage:churned (lapsed or canceled, kept for win-back)

Rule: a new stage replaces the old stage tag, it never stacks.

3

Source and channel tags

When to use: Tag where each contact first reached you so you can measure which channels produce real customers.

source:website

source:whatsapp

source:telegram

source:instagram

source:referral

source:paid-ads (or name the specific campaign, like source:spring-launch)

Set source once on creation and never overwrite it, so attribution stays accurate.

4

Interest and value tags

When to use: Layer these descriptive tags on top of stage so you can segment by what someone wants and how much they're worth.

interest:onboarding (name one interest tag per product or service, like interest:analytics)

interest:pricing (asked about cost or plans)

interest:demo (requested a walkthrough or trial)

Pick one: value:low, value:medium, or value:high, based on your own deal-size bands.

Multiple interest tags are fine, but value should always be a single tag.

5

Status tags

When to use: Use these to flag how a contact should be handled, separate from where they sit in the funnel.

status:vip (priority contact, route to a human fast)

status:do-not-contact (suppress from all outreach)

Status tags stack: a contact can carry several at once.

They are independent of stage, so status:vip and status:do-not-contact can technically coexist. Treat that pairing as a flag to reconcile rather than a state to design for.

Suppression always wins: when status:do-not-contact conflicts with an active stage or automation, the send is blocked.

Add a status tag only when it changes how someone is handled, and remove it when it no longer applies.

6

Example segments

When to use: Combine the tags above into saved filters that drive your campaigns, reporting, and routing rules.

Hot inbound this week: stage:qualified AND source:whatsapp

Demo requested, no purchase: interest:demo AND NOT stage:customer

High-value win-back: stage:churned AND value:high

New website leads to nurture: stage:lead AND source:website

VIP fast lane: status:vip (route straight to a human)

Suppression list: status:do-not-contact (exclude from every send)

Replace the [highlighted fields] with your own details. Free to use.

Do it in sem.chat

Let your AI agent tag every contact for you

Building the scheme is half the job. In sem.chat, your 24/7 AI agent answers on your website, WhatsApp, Telegram, and Instagram, then captures every conversation into the built-in CRM and applies these tags automatically as it learns what each person wants.

  • Auto-tag stage, source, and interest from real conversations across every channel
  • Saved segments power your follow-up, reporting, and routing with no manual sorting
  • Smart handoff routes status:vip and complex cases straight to a human

How to use this template

  1. 1

    Copy the naming rules and core tag list into your CRM, replacing every placeholder with your real products, channels, and deal-size bands.

  2. 2

    Audit your existing contacts: merge duplicate or inconsistent tags into the new prefix:value format, and delete anything off-scheme.

  3. 3

    Set the cardinality rule: each contact carries one stage tag, one source tag, and one value tag, plus multiple interest tags and any optional status tags that apply.

  4. 4

    Build the example segments as saved filters and point your automations, reports, and routing rules at them instead of loose tags.

Frequently asked questions

How many tags should one contact have?
Keep it lean: one stage tag, one source tag, one value tag, plus as many interest tags as genuinely apply. Status tags are optional and stack, so status:vip plus status:do-not-contact can technically coexist, but treat that combination as a flag to reconcile, not a target state. If a contact has a dozen tags, you're probably duplicating concepts that should live in a single prefix.
What's the difference between a tag and a segment?
A tag is a fact you attach to one contact, like stage:lead or source:whatsapp. A segment is a saved filter that combines tags to define a group, like qualified leads from WhatsApp. Tags are the inputs, segments are the views you act on.
How often should I clean up the scheme?
Review it whenever you launch a new channel or product, and otherwise on a regular cadence that fits your team. A quick monthly pass is usually enough to catch drift before it spreads across your records.

Power it up with sem.chat

Everything you need to put this template to work.

Put this template to work in sem.chat

Drop this template into sem.chat, put it to work across your channels, and go live the same day. Free to start, no credit card.