The difference between a CRM that grows valuable over time and a CRM that becomes a chaotic dumpster is one discipline: knowing when to tag and when to field. Most owners treat tags and custom fields as interchangeable. The result is a CRM with 200 tags by month six where nobody remembers what half of them mean, and no structured data to power reports or quotes.
The fix is the discipline. This is exactly when to use each, with the default segmentation that ships with HonorElevate per industry.
The conceptual difference
Tags are behavioral and boolean
A tag is either applied to a contact or not. The state is binary. The tag answers "is this contact currently in this category?" Examples: VIP, Storm Chaser, Maintenance Plan Active, After Hours Caller, Returning Customer, Bilingual Spanish, Mobility Issues.
Custom fields are structured and typed
A custom field stores a specific data point with a defined type (text, number, date, currency, dropdown, multi-select). The field answers "what is this specific fact about this contact?" Examples: System Brand (text), System Age (number), Last Service Date (date), Annual Spend YTD (currency), Service Area (dropdown).
The simple test
If you can ask "is the contact tagged with X?", it is a tag.
If you need to ask "what is the contact's X value?", it is a custom field.
"Is the contact a VIP?" → tag.
"What brand is their HVAC system?" → custom field.
The 12 default tags every service business needs
HonorElevate ships with these pre-configured per industry. Start here. Add tags only when a clear operational use case demands it.
1. VIP
Manually applied to your top-tier customers. Triggers priority dispatch, owner direct-line access, premium response SLAs.
2. Returning Customer
Auto-applied when a contact has 2+ completed jobs. Triggers personalized SMS templates that reference history.
3. Maintenance Plan Active
Auto-applied on plan signup. Triggers the maintenance plan workflow (scheduled visits, plan-perk reminders, renewal alerts).
4. Storm Chaser / Emergency
Auto-applied when the AI voice agent or web chat detects an emergency. Triggers priority dispatch and surcharge logic.
5. After Hours Caller
Auto-applied when the inbound call lands outside business hours. Used for after-hours conversion reporting.
6. Bilingual Spanish (or other language)
Applied when the AI detects Spanish-speaking preference. Triggers Spanish-language SMS templates and routes calls to bilingual techs when available.
7. Referral Source
Applied to customers who have referred someone. Triggers gratitude workflow (gift card, thank-you SMS, ongoing recognition).
8. High-Value Prospect
Auto-applied when lead score crosses 80. Triggers owner direct notification.
9. Stuck Quote
Auto-applied when a Quote Sent stage exceeds 72 hours. Triggers owner alert and re-engagement workflow.
10. Lost - Price Sensitive
Applied at Closed Lost when reason is pricing. Triggers a quarterly winback with a different offer angle.
11. Reviewer / Public Advocate
Auto-applied when customer leaves a public review. Used for retention nurture.
12. Do Not Contact
Applied on customer request. Blocks all outbound from the platform. Compliance-critical.
The 15 default custom fields per HVAC business
These are the structured data points that power quotes, reports, and segmentation queries.
| Field name | Type | Used for |
|---|---|---|
| Service Area | Dropdown | Routing, eligibility, reporting |
| System Brand | Dropdown | Parts ordering, expertise matching |
| System Model | Text | Specific parts lookup |
| System Age | Number | Repair vs replace logic |
| Install Date | Date | Warranty status |
| Last Service Date | Date | Maintenance scheduling |
| Maintenance Plan Tier | Dropdown | Plan benefits, renewal |
| Maintenance Plan Renewal Date | Date | Auto-renewal workflows |
| YTD Spend | Currency | LTV tracking |
| Total Spend | Currency | LTV tracking |
| Number of Jobs Completed | Number | Loyalty tier eligibility |
| Last Tech Assigned | Text | Preferred tech routing |
| Preferred Contact Method | Dropdown | SMS vs email vs call |
| Property Type | Dropdown | Residential vs commercial routing |
| Notes | Long text | Free-form context from techs and owner |
How tags trigger workflows
The real power of tags is automation. Every tag can be a trigger for a workflow.
Example 1: Storm Chaser tag fires emergency workflow
Tag applied → SMS to customer: "We are dispatching a tech now, emergency surcharge $X applies." Owner notification fires. Priority dispatch queue updated. Next available tech is rerouted to the emergency.
Example 2: Maintenance Plan Active tag fires recurring workflow
Tag applied → recurring maintenance visit scheduled (typically 6 or 12 months out). Reminder SMS at 30 days, 7 days, and day-of. Tech-rotation logic applied.
Example 3: Lost - Price Sensitive tag fires quarterly winback
Tag applied → 90-day delayed SMS with a different offer angle (financing options, off-peak pricing, value-tier service). Owner sees the response in the unified inbox.
Example 4: VIP tag changes every customer interaction
Tag applied → all future calls route directly to the owner. All SMS uses VIP-tier templates ("Connor here, what do you need today?"). Pricing logic may apply VIP discount.
How custom fields power reports
Tags answer "who fits this category right now." Custom fields answer "what are the patterns across all customers."
- Average ticket by service area: Group by Service Area custom field. Sum YTD Spend. Reveals which neighborhoods are highest-value.
- System brand distribution: Group by System Brand. Count contacts. Reveals which manufacturers dominate your service base.
- Maintenance plan renewals coming up: Filter Maintenance Plan Renewal Date for next 30 days. Surfaces upcoming renewal opportunities.
- Aging customer base: Filter System Age > 15 years. These customers are replacement-system candidates.
- Top 20% by LTV: Sort by Total Spend descending. Apply VIP outreach to top quintile.
None of these queries are possible if "Brand-Trane" and "Brand-Lennox" are tags instead of one custom field. The discipline pays off the first time you want to run a report.
Want your segmentation tuned for your industry?
Free 30-minute AI audit. We configure the default tags and custom fields for your specific industry, your specific operations, and your specific reporting needs.
Book My Free AI AuditThe four rules that keep segmentation clean
Rule 1: One concept, one place
If you are tagging it, do not also field it. If you are fielding it, do not also tag it. Pick one. The "Service Area" example: it is a custom field with dropdown values (Saugus, Valencia, Newhall, etc.) NOT also a set of tags ("Area-Saugus", "Area-Valencia", etc.). Pick a side.
Rule 2: Auto-apply when possible
Manual tag application erodes. Owners forget. Office staff disagree on what counts. The best tags are auto-applied by the system based on events (job completed → Returning Customer tag) or by AI parsing (call mentions emergency → Storm Chaser tag). Manual tags should be reserved for true judgment calls (VIP designation, Do Not Contact).
Rule 3: Use definitions, not gut
Every tag should have a one-sentence definition documented in the platform. "VIP: 3+ completed jobs at $5,000+ total spend OR personally designated by owner." Without the definition, applications drift. With it, the tag stays meaningful.
Rule 4: Prune quarterly
Every quarter, review the tag list. Tags with under 5 applications in 90 days probably either need to be auto-applied (raise the bar) or deleted (not actually useful). Tag fatigue kills CRM hygiene. 30 well-defined tags beats 200 vague ones.
What this looks like in practice
Maria Hernandez from Saugus, after her AC repair, looks like this in the CRM:
Tags applied: Returning Customer, After Hours Caller, HVAC, Reviewer
Custom fields populated:
- Service Area: Saugus
- System Brand: Carrier
- System Age: 12 years
- Install Date: 2014-08-15
- Last Service Date: 2026-05-16
- YTD Spend: $4,189
- Total Spend: $4,189
- Number of Jobs Completed: 1
- Last Tech Assigned: Mike Sanchez
- Preferred Contact Method: SMS
- Property Type: Residential
- Notes: "Capacitor + showing compressor strain, recommend replacement quote in 6 months"
This data structure enables: routing future calls to Mike, sending Maria a maintenance plan offer in 30 days (auto-fired), surfacing her in the "approaching replacement system age" report next year, and personalizing the next SMS thread ("Hi Maria, hope your Carrier is still running good after Mike's visit").
The bottom line
Tags and custom fields are not interchangeable. Tags are behavioral on/off markers that trigger automation. Custom fields are structured data points that power reports and quotes. Using them correctly is the discipline that separates a CRM that compounds in value from a CRM that becomes a graveyard.
HonorElevate ships with industry-tuned defaults so you do not have to design from scratch. 12 default tags. 15 default custom fields per industry. All auto-applied where possible. All documented with clear definitions. The discipline is built into the deploy.
For the pillar context, read The Complete Guide to CRM and Pipeline. For the pipeline stages that work alongside tags and fields, read The HonorElevate Pipeline Stages Built for Service Businesses.