CRM tags for wholesalers: what belongs in a tag, a field or a campaign
Tags are the easiest thing to add to a CRM and the hardest to keep clean. Within a year you have "hot", "Hot", "hot lead", "HOT!!", three versions of "probate" and a list of 400 tags nobody can search. The cause isn't sloppy people. It's that tags get used for jobs that need a field, a campaign or a flag, so each person invents their own. This guide sorts what a wholesaling or home-buying team actually needs to label, tells you which container fits each, and gives naming rules and a Salesforce setup. Use it whether you're on an investor CRM with tags built in or on Salesforce, which is built around structured fields rather than free-form tags.
Use a field (a picklist) for anything you'll report on or filter by every week: lead source, motivation, property type, dead reason. Use a campaign for a marketing wave or a list, because it carries cost and dates. Use a checkbox or status for consent and do-not-contact, which must never be a tag. Keep free tags, if your tool has them, for short-lived working labels, with a fixed list, one owner and a quarterly clean-up.
Why do tag systems turn into a mess?
- Anyone can create one. Free-text tags have no spell check and no owner.
- One tag tries to do four jobs. "Probate-hot-Franklin-Nov" is a source, a motivation, a market and a date squeezed into one word you can't count.
- Nobody retires them. Tags from a campaign two years ago still sit on thousands of records.
- Automation keys off them. Once a text sequence starts from a tag, deleting or renaming it breaks something quietly. See automations that fail quietly.
- The people who label are not the people who report. Reps tag what helps them today, and the owner later can't answer "which source works?"
What are you really trying to label?
Almost everything teams tag falls into one of six groups. The group tells you the right container.
- Where it came from (source, list, mailer wave, ad).
- Who the seller is and why they sell (motivation, situation: probate, divorce, tax delinquent, tired landlord).
- What the property is (type, condition, county).
- Where the lead is (stage, status, nurture).
- What you're allowed to do (consent to text, do not call, opted out).
- Temporary working notes ("send to dispo team", "call after the 15th").
Which container fits each?
| You are labeling | Use | Why |
|---|---|---|
| Lead source and channel | A picklist field with a fixed list, set when the record is created | You'll report on it every week; free text can't be counted |
| A mailer wave, list or ad campaign | A campaign (and campaign members) | Carries cost, dates and result, so cost per contract works |
| Seller situation (probate, divorce, tax delinquent) | A picklist, or a small set of checkboxes if a lead can be several | Needed for scoring and for the right message |
| Property type and county | Fields on the property or deal | Filters, buy-box matching and reporting |
| Stage and status | The stage or status field, with rules | This drives your pipeline; see pipeline stages |
| Consent, do not call, opt-out | A checkbox plus date and source, never a tag | A compliance fact needs a record of when and how |
| Short-lived working labels | A tag if you have them, from a fixed list | The one place free tags are fine, because nothing important depends on them |
The test: will I want to count it? If yes, it's a field, and probably a picklist. If it only helps someone find a record this week, a tag is fine.
What naming rules keep it clean?
- One list, one owner. One person (ops or an admin) approves new values. Reps can ask, but they can't create.
- Lowercase or one consistent style. Pick it once and never mix.
- One meaning per value. "Probate" means probate, not "probate and maybe divorce".
- No dates, names or markets inside a value. Those belong in their own fields or on the campaign.
- Keep the lists short. Ten to fifteen sources and eight to twelve situations is enough for most teams. If a list reaches fifty, you're mixing jobs.
- Write the definitions down. One line per value, in a place reps can read it. It prevents most arguments.
How do you build this in Salesforce?
Salesforce is built around structured fields rather than the free-form tags many investor CRMs use, which is a feature here: structure is what keeps data usable.
- Picklists for sources and situations. Use one shared list of values (a global value set) across Lead, Opportunity and Campaign, so a source can't mean different things on different objects. Make the field restricted, so a rep or an import can't add a new value by accident.
- Campaigns for waves and lists. Create a campaign per mailer wave or list and add records as campaign members with a status (sent, responded, appointment, contract). Cost goes on the campaign, which is what makes cost per contract a normal report. The step-by-step is in lead sources in Salesforce.
- Checkboxes for situations a lead can have more than one of. Several short checkboxes report more easily than one long multi-select list.
- Consent as its own set of fields. A checkbox, the date, and the source of the consent, plus an opt-out checkbox that Flow copies to every duplicate record. See texting and consent.
- Record types and page layouts to show reps only the values that apply to their type of lead.
- A data dictionary. A small custom object or a shared sheet listing each field, its values and its owner. It sounds boring and it's the thing future admins thank you for.
The CRM field kit has a starting set of lead, deal and buyer fields you can adapt.
Why are tags that trigger automation risky?
If adding a tag starts a text sequence, anyone who adds it starts messages. Two problems follow: a typo means nothing happens, and a bulk edit can start messages to thousands of sellers, including some who opted out. Safer pattern: automation starts from a stage, a status or a consent-checked field, never from a free tag. Where you can't avoid it, make the tag controlled (only ops can apply it) and have the automation check the consent field before it sends.
What does a 30-minute quarterly clean-up look like?
- List every tag or picklist value with its record count.
- Merge near-duplicates ("hot" and "Hot lead") and retire the unused.
- Check anything that triggers automation, and test it on one record.
- Archive campaigns that finished, and keep the results.
- Update the one-line definitions and tell the team what changed.
It's the same weekly-and-quarterly rhythm that keeps duplicates from piling up. If your tags are already out of hand, the CRM audit checklist shows where to start.
Questions
How should I tag leads in a wholesaling CRM?
Don't use one tag for everything. Put lead source, seller situation and property type in picklist fields you can report on, record marketing waves as campaigns with cost, and keep consent as a checkbox with a date. Use free tags only for short-lived working labels from a fixed list.
What is the difference between a tag and a field in a CRM?
A field holds one defined piece of data you can filter, count and report on, such as lead source. A tag is a free label that is quick to add but easy to misspell and hard to report on. Use fields for anything you'll count and tags for temporary notes.
Does Salesforce have tags?
Salesforce is built around structured fields rather than free-form tags like many investor CRMs. You use picklist fields, checkboxes, campaigns and record types, which keep the data structured and reportable. It takes more setup but is easier to report on.
How many lead sources should a CRM have?
Ten to fifteen is enough for most home-buying teams. If a source list grows past about fifty values, you're probably mixing the source with the campaign, the market or the date, which belong in their own fields.
Should consent and do-not-call be tags?
No. Consent is a compliance fact that needs a record of when and how it was given, so use a checkbox plus a date and a source, and make sure every duplicate record and every tool reads the same field.
How do I clean up a messy tag list?
Export every tag with its count, merge near-duplicates, retire unused ones, test anything that triggers automation, and write a one-line definition for each remaining value. Do it quarterly and give one person ownership of the list.
Related guides
Want your tags and fields sorted once?
Data structure is part of the fixed-price CRM Revenue Audit (USD 1,500): your fields, sources and tags reviewed against how you report, with a clean-up plan. It's for teams already on Salesforce.
Book a free callSee the Revenue AuditOr just ask one question about your setup: email · WhatsApp · LinkedIn
