🏷️ What is the Tag component for?
The Tag component allows you to assign tags or labels to a conversation automatically within the flow. Its main function is to mark relevant information mentioned by the user to facilitate organization, analysis, and future actions on the platform.
Tags can be understood as:
A simple information field associated with a single criterion.
A visual resource to give greater visibility to key data.
A very practical way to filter conversations and segment reports.
Unlike other more structured fields, tags are ideal when you need to quickly identify a specific attribute of the contact.
⚙️ Step by step: How does it work in the flow?
Implementing this component is very simple. When the conversation passes through this point in the flow, the tag is automatically assigned to the contact:
Drag the component: Locate the Tag component and drag it to your Flowbuilder canvas.
Configure the tag: In the right panel, select an existing tag from your account or type the name of a new one.
Create on the fly: If the tag you need doesn't exist, simply click on the "Create new tag" option that will appear in the dropdown menu.
💡 Use cases and Examples
📌 Example 1: Level of interest in a purchase You can use tags to classify lead temperature or interest level. This makes it easier to segment for remarketing campaigns:
High interest (Hot)
Medium interest (Warm)
Low interest (Cold)
📌 Example 2: Topics or preferences mentioned They are also perfect for highlighting quick information about customer intent:
Payment preference (Ex. Cash payment, Card).
Type of financing.
Contact urgency (Ex. Urgent support).
⚖️ Difference between Tags and Information Fields
Tags and information fields don't compete, they complement each other.
📌 Practical example: A university wants to know if the contact is interested in enrolling and, at the same time, what career interests them. The team defines that the level of interest is most important for quickly filtering conversations.
Recommended configuration:
Tags (To segment quickly): Hot, Warm, Cold.
Information field (To store structured data): Product of interest: Bachelor's degree / Master's degree / Courses.
👉 In summary: The tag gives you a quick view and serves to filter, while the information field stores the detailed data in the customer's profile.
✅ Best practices
To keep your database clean and useful, we recommend following these rules:
🎯 Use specific values: Each tag should represent a clear criterion that is related.
🚫 Don't mix concepts: Avoid combining multiple criteria in a single tag.
❌ Example to avoid: Creating a tag called
"interest, product and purchase time".✅ Recommended example: Use a tag for the level of interest (
"Hot") and separate information fields for the product and date.
📊 Think about analysis: Define your tags thinking about how you'll want to filter or search those conversations in the future.
Organize your chats like a professional! 🚀
The Tag component is your best ally for segmenting and analyzing conversations. Combine it intelligently with information fields and give your team the exact context they need to sell more. ✅