How to Use Labels in ZazzyAgent to Organize Customers
Labels are one of the easiest ways to organize customer conversations.
A label is a simple marker you can attach to a customer to describe something important about them or their interaction with your business.
Examples:
New Lead
VIP
Interested
Existing Customer
High Intent
Support Required
Interested in Shoes
Follow-up Required
What is a label?
A label is a tag attached to a customer record.
For example:
Customer: Rahul
Labels:
New Lead
Interested in Shoes
High Intent
Labels help your team understand customer status without reading the entire conversation history.
Create a label
Open the Labels area in ZazzyAgent.
Create a new label.
Use names that clearly describe what the label means.
Good:
High Intent
Bad:
Label 17
Apply labels manually
You can apply a label to a customer when appropriate.
For example:
Customer needs a callback.
Add:
Callback Required
Apply labels automatically
Automation can apply labels when specific events occur.
Example:
Customer asks for pricing.
↓
Add:
Pricing Interested
Another:
Customer confirms purchase interest.
↓
Add:
High Intent
Remove labels
Labels should also reflect changes.
Example:
Customer starts as:
New Lead
After purchasing:
Remove:
New Lead
Add:
Customer
Keeping labels updated prevents your customer database from becoming confusing.
Use labels with broadcasts
Labels can help you create targeted broadcast audiences.
Example:
Send a new-product message only to:
VIP
Instead of sending the same message to everyone.
Use labels with sequences
Labels can also be part of follow-up logic.
Example:
High Intent
↓
Subscribe to:
Sales Follow-up
Labels and AI Agents
An AI Agent can apply or remove labels through supported actions.
Example:
When the customer clearly expresses strong buying intent,
add the High Intent label.
##add_label## : 12
Or:
When the customer completes their purchase,
remove the High Intent label.
##remove_label## : 12
Always select the appropriate label through the ## autocomplete rather than guessing the numeric ID.
Labels vs custom fields
A label is best for a simple state or category.
VIP
A custom field is best for a specific value.
Budget = ₹30,000
Another example:
Label:
Interested in Cars
Custom Field:
Preferred Car = SUV
Labels vs segments
A label is information stored against a customer.
A segment is a group created using filtering rules.
Example:
Label
VIP
Segment
VIP customers in Mumbai who haven't purchased in the last 90 days.
Don't create duplicate labels
Avoid having several labels that mean the same thing.
For example:
Interested
Interested Lead
Lead Interested
Customer Interest
Choose a naming system and keep it consistent.
Create labels around useful events
Useful label categories include:
Customer stage
New Lead
Qualified
Customer
Repeat Customer
Sales status
High Intent
Demo Requested
Quote Requested
Support status
Support Required
Callback Required
Escalated
Product interest
Interested in Shoes
Interested in Shirts
Interested in Accessories
Example: Lead lifecycle
A simple automation could use:
New Lead
↓
Customer answers qualification questions.
↓
Qualified Lead
↓
Customer expresses strong buying interest.
↓
High Intent
↓
Customer purchases.
↓
Customer
This creates a clear customer lifecycle using simple labels.
Label troubleshooting
If a customer is not showing under the expected label, check:
The label was actually applied.
The correct label was selected.
Automation conditions were met.
The workflow ran successfully.
The customer record is the expected one.
Best practice
Every label should answer a useful question.
For example:
Is this customer a VIP?
Is this customer interested in Product A?
Does this customer need a callback?
If a label doesn't help your team make a decision or organize customers, you probably don't need it.