Use four role tags in GoHighLevel, Buyer, Seller, Investor, and Renter, that can stack on one contact, plus a few status tags, and keep every protected trait out of tag names. The bottom line: tags start workflows and filter lists, so each tag should mean one clear thing, and a tag like Family or Senior is both unnecessary and a Fair Housing risk.
Why roles must stack
A summary table of NAR's Profile of Home Buyers and Sellers lists the share of repeat buyers at 79 percent in 2025, and NAR reports that 51 percent of sellers used the same agent to buy their next home. So many contacts are both: a seller who is also a buyer. A single role field would force a choice. Tags can stack, so one person can be Seller and Buyer, and each tag can start its own workflow.
The tag set
| Tag | Meaning | Starts |
|---|---|---|
| Buyer | Looking to buy | Buyer lead and criteria workflows |
| Seller | Looking to sell | Listing and pricing workflows |
| Investor | Buying or selling for investment | Investor criteria and deal alerts |
| Renter | Looking to rent, or a rental client | Rental inquiry workflow, if the team handles rentals |
| Lead, Client, Under contract, Closed, Past client | Lifecycle status | Sequences, as in our lead to client guide |
| Opted out | Asked to stop messages | Removes from messaging |
| Updates consent, Marketing consent | What the person agreed to receive | Which lists they can join |
Status tags move over time and should change with the pipeline stage. Role tags are stable facts about what the person wants. Do not use tags to track things that change daily, such as the last property viewed. Use fields for that.
What tags must never say
The Fair Housing Act, 42 U.S.C. 3604, makes it unlawful to discriminate in the sale or rental of housing based on race, color, national origin, religion, sex, familial status, or disability, and steering does not require bad intent. HUD issued two guidance documents on AI on May 2, 2024, one on tenant screening and one on ad targeting and delivery, and one source reports that HUD withdrew the advertising guidance effective September 17, 2025. The statute applies either way, private parties can still sue, and several summaries stress that a brokerage cannot hand its fair housing responsibility to a software vendor. In practice that means a chat or voice assistant should answer facts about the property and the process, treat every lead the same way, and never describe a neighborhood by who lives there.
- Protected characteristics. Avoid tags like Family, Has kids, Senior, Christian community, or Disabled.
- Source of income. Many states protect it, so avoid tags such as Section 8 or Voucher on rental contacts, and record only what a lawful screening process requires, separately from marketing.
- Neighborhood labels about people. Use the area the person named, not a tag about who lives there.
- Slurs or opinions. Tags are visible in lists and exports.
Naming rules
- One meaning per tag, written the same way every time.
- Singular nouns, with the first letter capitalized.
- A one line note on each tag in a shared document.
- A quarterly review that merges duplicates, such as Buyer and Buyers.
Build it in GoHighLevel
GoHighLevel's help pages describe tags as labels that start workflows and filter lists, and workflow actions that add and remove them.
- Create the tags in the table, and write the one line meaning of each.
- Build a form that sets role tags from the buyer or seller's own answer, and allows more than one.
- Build workflows that start when a role tag is added, such as the buyer lead sequence on Buyer.
- Move status tags with the pipeline stage, removing the old one when the new one is added.
- Restrict who can create new tags, to prevent duplicates.
- Audit tags each quarter, and delete any that reference a protected trait.
Worked example
For example, a team with 800 buyer contacts, half of whom also own a home they may sell, has about 400 contacts who hold both tags (800 times 0.5). Stacking tags lets each contact get the right workflow for each role. The one half is an assumption to replace with your own count.
Mistakes to avoid
- One role per contact. Allow stacking.
- Tags about protected traits. Do not create them.
- Duplicate tags. Standardize and audit.
- Using tags for fast changing facts. Use fields.
How this was handled before
CRMs offered one contact type field, so a seller who was also a buyer had to be entered twice. Stackable tags fix that, and a naming rule keeps protected traits out of the labels.
What to measure after launch
Track contacts with a role tag, contacts with two roles, duplicate tags, and tags removed in audit. Audit the tag list each quarter.
Check before you switch it on
US text messages sent from a standard 10 digit number need A2P 10DLC registration. The HighLevel support portal says registration is required for texts to US recipients from 10 digit long code numbers and that toll free numbers do not require it. HighLevel's opt in guidelines also say a person cannot be forced to agree to text messages in order to submit a form, so keep the consent box optional. One compliance guide separates informational texts, which need documented consent, from marketing texts, which need prior express written consent. Ask your attorney which category your reminders fall into. Have your broker review the tag list for Fair Housing issues, including state protected classes such as source of income. This is general information, not legal advice.
Questions people ask
Why can a contact have two role tags?
Many people are both buyers and sellers. NAR's Profile shows repeat buyers are a large share of buyers, so roles must stack.
What should a tag never say?
Anything about a protected characteristic, such as family status, age, religion, disability, or source of income.
What starts a workflow in GoHighLevel?
Tags can start workflows and filter lists, according to its help pages.
Ready to try it yourself? Start a GoHighLevel account here.
You can also see this in action in our GoHighLevel capabilities demo.