Tag Component
❓ What is the Tag component in Flowbuilder used for?
The Tag component allows you to assign tags to a conversation within the flow, facilitating the organization, analysis, and future marketing, sales, or customer service actions in Atom.
❓ What is the main function of the Tag component?
The main function of the Tag component is to mark relevant information mentioned during a conversation.
Tags can be understood as:
A simple information field, associated with a single criterion.
A resource to give greater visibility to a key piece of data.
A practical way to filter conversations and reports.
Unlike other more structured fields, tags are ideal when you need to quickly identify a specific attribute of the contact.
❓ How does the Tag component work within the flow?
The component allows you to:
Select previously created tags.
Create a new tag directly from the flow if it does not already exist.
When the flow reaches this component, the tag is automatically assigned to the conversation.
❓ How to use the Tag component step by step?
Drag the Tag component to the flow.
Drag the Tag component to the flow.
Select an existing tag or write a new one.
Select an existing tag or write a new one.
If the tag does not exist, choose the option "Create new tag".
If the tag does not exist, choose the option "Create new tag".
The tag will be automatically assigned when the flow passes through that point.
The tag will be automatically assigned when the flow passes through that point.
❓ In what cases should you use tags? (Examples)
📌 Example 1: Level of interest in a purchase
You can use tags to classify customer interest, for example:
High interest
Medium interest
Low interest
This later facilitates the segmentation of conversations and the analysis of results.
📌 Example 2: Topics or preferences mentioned
You can also use tags to identify relevant information mentioned in the conversation, such as:
Payment preferences.
Type of financing.
Urgency of contact.
❓ What is the difference between using tags and information fields?
Tags and information fields do not compete, but rather complement each other.
📌 Practical example
A university wants to:
Know if the contact is interested in enrolling.
Know the product of interest.
The client defines that the level of interest in enrolling is the most important thing to filter conversations and reports.
Recommended configuration:
TagsHotWarmCold
Hot
Warm
Cold
Information fieldProduct of interest: Bachelor's Degree / Master's Degree / Courses
Product of interest: Bachelor's Degree / Master's Degree / Courses
👉 In this case, the tag is used to segment quickly, and the information field to save structured data.
❓ What are the best practices when using tags?
📢 Recommended best practices:
Use tags with specific and related values.
Avoid combining multiple criteria in a single tag.
Define tags thinking about how you are going to filter or analyze them later.
❌ Example to avoid:
"interest, product and purchase time"
✅ Recommended example:
Separate tags for interest (Hot / Warm / Cold).
Information fields for product, date or type of service.