In this article we'll explain how to save information within a conversational flow, what options exist to do so, and when it's best to use the Save Field component or a field-saving Smarton.
Correctly saving customer data is key for:
Personalizing responses.
Making decisions within the flow.
Improving reporting and analysis.
Avoiding errors or inconsistent data.
📌 What is the Save Field component?
The Save Field component allows you to store information within a field based on:
What the user says (Input).
A fixed value defined by the flow.
📍 Examples of information you can save: Document or ID, city, payment method, consultation status, or internal identifiers.
How is it configured?
Select the field where the information will be stored.
Choose whether you'll save the user's response or assign a specific value for all customers.
✍️ How can information be saved?
There are two main ways to save a field within a flow:
1️⃣ Save the user's input
The field takes the customer's actual response.
Example: The bot asks: "What city are you in?". The user responds: "Panama City". The flow saves that exact value in the City field.
👉 Ideal for: Capturing explicit user information.
2️⃣ Assign a specific value (Fixed/hardcoded value)
The field always saves the same value, regardless of the response.
Example: Field: City | Specific value: Panama City.
👉 Ideal for: Data that is defined by context, that is fixed for the entire flow, or that doesn't need to be asked.
🔀 Save Field vs. Field-saving Smarton
Both options serve to store information, but they aren't used in the same scenarios:
🧩 Save Field Component | 🤖 Field-saving Smarton |
Saves a specific piece of data at a specific point. | AI interprets the context and decides what and when to save. |
Ideal for direct inputs, fixed values, and simple logic. | Ideal for open conversations and data that doesn't come in a single response. |
Works with strict rules. | Works automatically without explicit questions. |
💡 Tip: If the data is clear and structured, use Save Field. If the data comes from a more open conversation, use the Smarton.
🗂️ Information fields vs. Flow variables
It's key to understand this difference to avoid overloading the bot:
🟦 Information fields: Persist over time and are used for reporting and analysis. (Note: They impact performance if overused).
🟨 Flow variables: Live only during the conversation and are not stored long-term. They're ideal for temporary logic or intermediate states.
📌 Practical rule: If the data only serves "in the moment", use a variable. If you need history or reports, use a field.
📝 The importance of field descriptions
The field description functions as a prompt (instruction) for the AI. It tells it: what to save, when to do it, and what values are valid.
A poor description can generate incorrect data, poorly populated fields, and errors in automatic decisions.
📢 Best practices for Save Field
1️⃣ Define clear and specific descriptions
Avoid generic or ambiguous texts.
✅ Correct: Field: Payment method | Description: "Payment method chosen by the user. Possible values: 'cash' or 'credit'."
❌ Incorrect: "User's form of payment."
2️⃣ Include clear storage conditions
Specify when the value should and shouldn't be saved.
✅ Correct: Save only if the user mentions "cash". Don't save if they mention "installments".
❌ Incorrect: "Save when the user mentions a payment method."
3️⃣ Adapt the field to the conversation context
Not all fields depend on a direct response.
✅ Correct: Field: Consultation made | Description: "Save 'True' if the user made a consultation and received a successful response."
4️⃣ Use structured and standardized values
Avoid long texts or free interpretations.
✅ Correct: Allowed values: "Resolved" / "Pending" / "Escalated".
❌ Incorrect: "The user asked something and was answered correctly."
5️⃣ Avoid saving unnecessary information
Not everything should be a persistent field. Temporary data should go into flow variables.
📉 Real case: A bot had more than 600 information fields, of which 30% could have been variables. This negatively impacted reporting, bot performance, and generated unnecessary data load.
You're now in control of your data! 🚀
By saving strategic fields, you give context to your team and can personalize the rest of the flow. Start capturing valuable information automatically and improve your customers' experience. ✅