CRM Tags
Tags are simple labels attached to customers. They are useful for quick filtering and flexible organization without creating too many segments.
Recommended Tags
- Hot lead.
- Needs follow-up.
- Coupon user.
- Booking customer.
- Negative feedback.
- Referral source.
- VIP.
CRM Tags - Main Features Overview
Reusable labels for classifying customers and campaign interactions. This page explains how customers should use the CRM Tags module in day-to-day LocalBoost AI operations, from setup to review and troubleshooting.
Main Features
- CRM customers.
- Segments.
- Tags.
- Tasks.
- CRM automations.
- CRM reports and CSV export.
Recommended Workflow
- Review incoming customers.
- Clean and tag records.
- Create useful segments.
- Assign tasks for manual follow-up.
- Create automations for repeated actions.
- Use reports to measure CRM health.
Views, Filters, and Review Options
- Filter by business.
- Filter by segment.
- Filter by tag.
- Filter by source campaign.
- Filter tasks by status and due date.
Available Actions
- Open customer detail.
- Create segments and tags.
- Create tasks.
- Build CRM automations.
- Export customers CSV.
- Review CRM reports.
Benefits
- Turns campaign submissions into follow-up workflow.
- Helps sales and service teams prioritize.
- Prevents leads from being forgotten.
- Supports targeted automation.
Before Publishing or Activating
- Customer consent rules are respected.
- Segments are named clearly.
- Tags are not duplicated.
- Tasks have owners and due dates.
- Automations are tested on a small segment first.
Troubleshooting
- If customers are missing, check source campaign submission.
- If segments look wrong, review segment rules.
- If tasks are overdue, check assignment workflow.
- If export fails, check permissions.
- If automation or AI does not run, check credits, provider settings, logs, and feature access.
Operational Notes
Use consistent naming for businesses, campaigns, templates, QR codes, automations, and CRM segments. Consistent naming makes reports easier to read and helps support teams diagnose issues quickly. When a feature depends on an addon, confirm the addon is installed, active, available in the current plan, and visible to the current workspace.