Required Attributes for Stage Transitions

Configure which lead attributes must be filled in before a lead can be moved into a given stage — gate stage moves until the data you need is captured.

Overview

Required Attributes let an admin make one or more lead attributes mandatory before a lead can be moved into a particular stage. When someone manually moves a single lead into that stage and a required attribute is still empty, Kraya blocks the move and asks them to fill in the missing information first. This is useful for capturing the reason or context behind a stage change — for example, forcing a "Lost reason" to be recorded whenever a lead is moved to "Lead Lost", or a "Budget" when a lead reaches "Qualified".

What you can do

Turn on a "Require an attribute" rule for any stage in your pipeline (admin only).
Select one or more existing lead attributes that must be filled before a lead can enter that stage.
See at a glance which attributes a stage requires, shown as "Requires:" chips on the stage.
Have Kraya block a manual single-lead move when a required attribute is missing, and collect the missing values in a single popup.
Capture important data (lost reason, budget, and so on) at the exact moment a lead enters a stage.

How it works

Required attributes are configured per stage. Once a stage has a requirement:

Manual single-lead moves are checked. When you move one lead into the stage — from the lead's details, the lead list, or the Chrome extension — Kraya checks whether every required attribute already has a value.
- If all required attributes are filled, the move happens normally with no interruption.
- If any required attribute is empty, a popup appears listing the missing attributes. The lead only moves after you fill them in. If you cancel, the lead stays in its original stage.
A value counts as "filled" if it has real content. A number of 0 and a value of false count as filled. A completely empty field, or a value that is only spaces, counts as empty and will block the move.
Automated and bulk moves are never blocked. Bulk stage updates, Smart Triggers, AI qualification / AI stage shifting, and integration or lead-sync moves (Zoho, GoHighLevel, and others) all skip the requirement check. The rule only applies to manual, one-at-a-time moves made by a person.
Existing leads are left in place. If you add a requirement to a stage that already contains leads missing that attribute, those leads are not moved out. The rule only applies to new leads entering the stage from that point on.

Step-by-step guide

Requiring an attribute on a stage (admin)

Open your pipeline and go to Edit & Shuffle (the stage management view).
Edit the stage you want to add a requirement to, or use Add New Stage to set the requirement while creating a stage.
Turn on the Require an attribute toggle. An attribute selector appears, labelled Attributes required to enter this stage.
Select one or more attributes from the checkbox list. You must select at least one — if none are selected, you will see "Select at least one attribute".
Save the stage. The stage now shows a Requires: row with a chip for each required attribute.

Moving a lead into a stage with required attributes

You can move a single lead from two places on the dashboard — the Lead Details stage dropdown, and the lead list's Shift to dropdown. Both behave the same way.

Change the lead's stage to a stage that has required attributes.
If all required attributes are already filled on the lead, the move completes immediately.
If any are missing, a popup opens:
- When one attribute is missing, the title reads "[Attribute] Required".
- When more than one is missing, the title reads "Required attributes missing" and every missing attribute is listed.
Fill in each field. Each attribute shows the correct input for its type — text, number, date picker, date-and-time picker, or a dropdown listing its configured options.
Click Fill & Move. The button stays disabled until every required field has a value. Once you click it, the lead moves and the values are saved on the lead.
To abandon the move, close the popup or cancel — the lead stays in its original stage and nothing is saved.

Removing a requirement

Open Edit & Shuffle and edit the stage.
Turn the Require an attribute toggle off and save. The Requires: chips disappear and the stage no longer blocks moves.

Settings and configuration

Require an attribute (toggle) — Off by default. When on, at least one attribute must be selected.
Attributes required to enter this stage (checkbox list) — The list of the organization's existing lead attributes. Tick each attribute that must be filled before a lead can enter the stage. Multiple attributes per stage are supported.

The stage editor also notes that enforcement applies only to manual single-lead moves: "Enforced only on manual single-lead moves. Bulk moves and AI / automation moves skip this check."

Role-based behavior

Admins: Can add, change, and remove required-attribute rules on stages through Edit & Shuffle.
Members: Work within the existing setup. When they manually move a lead into a stage with a requirement, they are prompted to fill any missing attributes before the move completes.

Common edge cases

A required attribute is only spaces or blank This counts as empty and blocks the move. Enter a real value to continue.
A required number attribute is 0 0 is a valid, filled value — the move is not blocked.
Adding a requirement to a stage that already has leads without the attribute Existing leads stay where they are; they are not moved out. The rule applies only to leads entering the stage afterwards. The stage editor shows an informational count of how many current leads are missing the attribute.
Deleting an attribute that a stage requires Deleting is not blocked. When you delete such an attribute, Kraya shows a warning listing the stages that require it — "Required by stage(s): [names]. The requirement will be removed." — and after you confirm, both the attribute and the stage requirement are removed. (Deleting an attribute also removes it from all leads and permanently loses its data.)
Renaming an attribute that a stage requires The requirement follows the rename. After renaming, moving a lead into the stage shows the attribute under its new name and still enforces the requirement.
Cross-pipeline moves The requirement is checked against the stage the lead is moving into, regardless of which pipeline it came from. Moving a lead from one pipeline into a stage of another pipeline that has requirements shows the popup for that target stage.
Someone else adds a requirement while your page is open (stale page) If you try to move a lead into the stage before your page has picked up the new rule, the move is still blocked by Kraya as a safety net and the popup appears so you can fill the missing values.

Troubleshooting

A lead won't move into a stage and a popup keeps appearing

Cause: The stage has one or more required attributes that are empty on this lead.
Fix: Fill in every field listed in the popup, then click Fill & Move.

"Fill & Move" is greyed out

Cause: At least one required field is still empty, or contains only spaces.
Fix: Enter a real value in every field. The button enables once all are filled.

A bulk move or automation moved a lead into the stage without filling the attributes

Cause: This is expected. The requirement only applies to manual single-lead moves. Bulk updates, Smart Triggers, AI, and integrations intentionally skip the check.
Fix: No action needed. If you need the data on those leads, fill the attribute manually.

I removed the toggle but leads still show old values

Cause: Turning the requirement off only stops future blocking; it does not clear attribute values already saved on leads.
Fix: This is expected. Edit individual leads if you want to change the stored values.

FAQs

Can I require more than one attribute on a stage? Yes. Select as many attributes as you need in the checkbox list; all of them must be filled before a lead can enter the stage.
Will this block my bulk stage updates or Smart Triggers? No. Bulk moves and all automated moves (Smart Triggers, AI qualification / stage shifting, integrations) skip the check. Only manual single-lead moves are enforced.
Does a 0 value satisfy the requirement? Yes. 0 and false count as filled. Only blank or spaces-only values are treated as empty.
What happens to leads already in the stage when I add a requirement? They stay put. The rule only applies to leads entering the stage after you add it.
What happens to the requirement if I delete the attribute? The requirement is removed automatically. You will see a warning naming the affected stages before you confirm the deletion.
Does this work in the Chrome extension? Yes. See the Chrome extension section below.

Chrome extension

The same feature works inside the WhatsApp Chrome extension:

Configure: When editing a stage, turn on the Require an attribute toggle and pick attributes from a scrollable checkbox list, then save.
Enforce: When you move a lead into a stage that has requirements, an inline "Required to move to [stage]" section appears in the stage panel with an input for each attribute, pre-filled from the lead where possible. When more than one attribute is required, a filled/total counter (for example, "1 / 2") shows your progress, and Save stays disabled until every field is filled. Moving a lead into a stage with no requirement works normally with no extra box.

Tips and best practices

Use required attributes to enforce data hygiene at key transitions — a "Lost reason" on your lost stage, or a "Budget" on your qualified stage — so reporting stays complete.
Keep the number of required attributes per stage small; requiring too many fields on a common move adds friction for your team.
Because automated moves skip the check, do not rely on this feature to guarantee data on leads that arrive via imports, integrations, or Smart Triggers.

Dashboard — where pipelines, stages, and lead moves live, including Edit & Shuffle.
Attribute Data Types — the attribute types (text, number, date, date-time, dropdown) that can be required.
Smart Triggers — automated "move to stage" actions, which skip the requirement.
AI Stage Shifting — AI-driven stage moves, which skip the requirement.
Chrome Extension — using Kraya inside WhatsApp Web, including required attributes.