Every qualification step in your sales flow saves its answer to a field. Think of a field as the labeled box where the agent stores what it just learned: the prospect's budget, their goal, their timeline, their experience level, whatever that step asked about. Everything captured lands on the contact's profile, so your pipeline fills itself in as conversations happen.
Most commonly, your fields are your qualification criteria. A fitness coach might capture "goal", "training experience", and "budget". You can collect whatever you want, but the pattern to aim for is simple: each step asks one qualifying question, and its field is where the answer lives.
What you never need to capture
Before you plan your fields, know what Cloziq already handles for you, because the answer changes what your steps should ask:
- Booking calls in the DMs: if your agent books through your connected calendar, Cloziq automatically collects the prospect's name and email at booking time. They are required to book the call, so the agent takes care of it on its own. You do not need to configure any step for them.
- Selling in the DMs: Stripe checkout requires the buyer's email as part of paying, and that is the email Cloziq uses for delivery and receipts. Again, nothing to configure.
So contact details take care of themselves exactly where they matter. Capture an email or phone field yourself only when you want it for your own purposes, like follow-up outside Cloziq or lead forwarding to Zapier. Otherwise, spend your steps on qualification, which is what makes the conversation smarter.
Pick a field on each step
Field management lives right on the Sales Flow tab. Under each step's message you will find Field Selection:
- Open the field dropdown. You can search your workspace's existing fields or choose Create new field.
- Pick the field this step's answer should be saved to. It attaches immediately, as a chip under the step, marked Required. There is no separate Add button.
- Untick Required on the chip if the answer is nice to have rather than essential. Required means the agent must collect the answer before moving on; when it is unchecked, the agent asks up to two times and then continues without it.
Each step captures exactly one field, so the picker disappears once a field is attached. To change it, remove the chip and pick another. A field can also only be captured once anywhere in the flow: any field already used on another step, or inside a sub-step, is hidden from the picker, so you cannot create a duplicate by accident.
Sub-steps work exactly the same way, with the full field library available to them too.
Field types
When you create a field, you give it a name and a type: Text, Email, Number, Phone, or Select (a fixed set of options). The type decides how strict the agent is about what it saves.
Text fields are generous. If the prospect makes a genuine attempt at your question, it gets saved, even when the answer is loose. Ask when they want to start and "whenever I have the time really" is a real answer, so the agent takes it and moves on rather than asking again.
Email, Phone, Number and Select are strict. If the answer is not a usable value, nothing is saved and the agent asks again. Number fields also respect the units in your field description: if you called the field "monthly budget" and someone answers "about $60k for the year", the agent will not record 60000 as a monthly figure. It asks for the monthly number instead.
The practical takeaway: put the unit or period in the field's description whenever it matters. That description is what stops a yearly figure landing in a monthly field.
How Select fields read an answer
Select fields do not need the prospect to repeat your options word for word. The agent maps what they actually say onto your list, so for options like Salmon, Chicken and Tofu, "the fish" picks Salmon and "the first one" picks Salmon too.
One behavior is worth designing around: if the prospect is genuinely indifferent, the agent picks your first option. "You pick", "whatever", "up to you", "doesn't matter" all resolve to the top of your list and the conversation moves on rather than stalling on a question they do not care about.
So order your options deliberately. Whatever sits first is the answer you get from everyone who has no preference, which makes it worth putting your safest or most common choice there rather than your most expensive one.
Manage your field library
Manage Fields on the Sales Flow tab opens your workspace's field library, where you can add new fields or remove ones this agent should not use. Fields are shared across your workspace, so a field like "Budget" means the same thing on every agent, and every agent's answers land in the same place on the contact.
Deleting a field from the library cleans up after itself: it is removed from every step that captured it and every if/then rule that referenced it, so you are never left with a rule pointing at something that no longer exists.
Every step needs a field to publish
You can save a draft at any point, but publishing requires every qualification step to capture a field. If a step is missing one, publish stops with "Step N: choose a field to capture before publishing." This is deliberate: a question whose answer is not saved anywhere is a question you cannot act on later.
If a step references a field that was removed from the agent, publish flags that too and points you to Manage Fields to fix it.
Tips
- Design fields around decisions. If "budget under $100" means disqualify, capture budget as a field and let a Flow Action act on it.
- Only ask for what you will actually use. Every extra ask adds friction; the smoothest flows capture two or three things.
- Phrase the step's question so the answer is the field. "What's your monthly budget for coaching?" maps cleanly; "tell me about yourself" does not.
- Skip the email step unless you want the email for yourself. Booking and checkout collect it automatically when it is actually needed.