Wizards in Zoho CRM for long record forms and how to set them up

Wizards in Zoho CRM fix long record forms by splitting one crowded layout into a series of guided screens. Each screen holds only the fields that step needs. A Wizard is a Zoho CRM feature that divides a long form into screens, where users enter data on each screen and move on until the record is complete.

Users move between screens with buttons, and the record is saved at the end. Fields, instructions and searches can appear or disappear depending on what the user has already entered. The result is a record form that follows the order of the real conversation, not the order in which fields were added to the layout over the years.

This guide covers four things:

• which layouts deserve a wizard
• where to cut the form into screens
• how conditional rules and buttons work
• what to test before go-live

The product facts come from Zoho's help pages on creating Wizards in Zoho CRM and the Zoho CRM Wizards FAQ.

One boundary matters from the start. Wizards only apply when someone creates a record by hand inside a CRM module. They solve a data entry problem for your team. They do nothing for records that arrive through integrations.

A Zoho CRM layout is too long when users stop filling it in reliably. The problem is rarely the number of fields alone. It is that every user sees every field, whether or not the field applies to the record in front of them. Zoho's own product page on Wizards makes the same point. Collecting different kinds of customer data becomes complicated when you rely on one standard form for creating records.

You can usually spot an overgrown layout from the records it produces. Watch for these signs:

• Mandatory fields filled with placeholder values just to get past the save button.
• Important optional fields left empty because they sit far down the page.
• Several record types, such as private and business customers, sharing one layout.
• A stack of layout rules that only the administrator who wrote them understands.
• New staff asking colleagues what to say or ask while they fill in the form.

If two or more of these apply to one layout, that layout is a candidate for a wizard. If the records are bad because the data itself is wrong, a wizard will not help. That is a matter of validation and ownership rules, not of screen design.

Zoho CRM Wizards work for manual record creation in most modules, by internal users, with most field types. Before you design anything, check the layout against the limits in Zoho's documentation. Any check in the right-hand column means a wizard is the wrong tool for that part of the process.

Check	Wizard fits	Wizard does not fit
How records are created	Manually, inside the CRM module	Through webform, import or API
Module	Standard and custom modules	Inventory and Activities modules
Who enters the data	Internal CRM users	Portal users, who cannot yet access Wizards
Field types	All other field types	Multi-select lookup and user lookup fields
Layouts covered	Up to 4 layouts in one wizard	Processes spread over more layouts

The first row is the one most often missed. If customers send enquiries through a web form, the form itself needs to be short and guided. A tool such as Zoho Forms with its multi-page form builder handles that side.

The same applies to imports. A wizard does nothing for records loaded in bulk. When you bring records over from an old system, the mapping work described in our guide to migrating into Zoho CRM is still needed.

Cut a long form where the user's task changes, not where the field list happens to be long. A good wizard screen answers one question the user can deal with in one go. Examples are "who is this person" or "what do they need". Four practical rules help you find the cut points.

1. Follow the conversation. Put fields in the order a salesperson or service agent actually learns the answers. Screen one holds what you know at the first contact.
2. Cut at every branch. Where an answer decides which fields come next, end the screen there. A conditional rule or a button can then show the right fields on the following screen.
3. Group by who knows the answer. Fields that only a manager or back-office colleague can fill in belong on a separate, later screen.
4. Finish with a save screen. The last screen holds the button that saves the record, and any final checks.

Inside a screen, use sections to keep related fields together. A section is a drag-and-drop component that groups fields or sub-areas within a single screen, and each screen allows up to 10 of them.

Keep every connection between screens pointing forward. Zoho will not save a wizard whose screens form a loop. An example is screen 1, then 2, then 3, then 4, and then back to screen 2.

A Zoho CRM wizard is built from screens, and each screen is built from fields, sections, buttons and components. You assemble them in a builder by dragging components onto the form and defining the flow between screens. Only users with the Module Customization permission can create, edit and delete Wizards.

Buttons

Buttons are mandatory in every wizard. They act as the links to the next screens, and they save the record. A single screen can hold up to 10 buttons. Admins can attach actions to a button, such as email alerts and webhooks, which run when a user clicks it. Buttons can also be hidden, shown, enabled or disabled based on what the user has entered.

Components

A screen can hold three kinds of component besides fields:

• Text component: a block for instructions, disclaimers or a call script, up to five per screen.
• Widget: one custom widget per screen. It passes information back to the wizard with ZOHO.CRM.WIZARD.Post(data) from the widget SDK.
• Query component: a search field with a search parameter and a preset comparator. It is matched against a field in the current or a related module, with predetermined actions based on the results. Only one is allowed per screen.

Zoho states that each wizard can hold up to five query components. It also states that a maximum of three can be created per module, so plan for the lower figure.

Conditional rules are a wizard's own layout rules. They change the form while the user fills it in, based on a set of criteria and actions. Zoho's FAQ says that layout rules are not needed for wizards, because conditional rules take their place. Conditional rules also take priority over map dependency fields.

The consequence is easy to overlook. Validation rules still work when a record is created through a wizard. Existing layout rules do not carry over. A Zoho community user reported exactly this: a field made mandatory by a layout rule was not mandatory inside the wizard. Any logic that lives in a layout rule today must be rebuilt as a conditional rule, or it disappears for wizard users.

At Svennis, we list every layout rule on the original layout before we design the first screen. We rebuild each one as a conditional rule and test it field by field. This is the step where we most often find a conditional mandatory field that would quietly have stopped being mandatory.

A conditional rule can show fields, subforms and text components. Use that to keep each screen short. A business customer sees the company fields. A private customer never does. A call script appears only when the lead source calls for one.

A four-screen wizard on the Leads module shows how the pieces fit together. Leads is a standard module, so wizards are supported there. Assume the existing layout has grown to cover private and business enquiries in one long form.

1. Screen 1, Contact. Name, email, phone and lead source. One button, "Next", leads to screen 2.
2. Screen 2, Qualification. A text component holds the call script your sales manager wrote. A picklist asks whether the lead is a business or a private customer. A conditional rule shows the budget and timing fields only for business leads.
3. Screen 3, Company. A query component searches the company name against your existing accounts. Users can then see whether the company is already a customer. Two buttons lead on to screen 4. A conditional rule hides "Continue as new company" when a match is found.
4. Screen 4, Review and save. A save button creates the lead and sends an email alert to the sales manager.

Notice what the example avoids. There is no button from screen 4 back to screen 2, because that connection would form a loop. In that case Zoho would refuse to save the wizard. Private customers skip the company fields entirely, so the form they see is shorter than the old layout.

If a user stops halfway, the incomplete record becomes a draft. A draft stays in the module's Drafts section until it is submitted, saved or deleted. Later, the same wizard layout is used to edit any record it created.

Wizard limits differ between the Zoho CRM Enterprise and Ultimate plans. The difference shows up mainly in how much one screen's conditional rules can do. If your design depends on many rules per screen, check the numbers against your plan before you build. The plans and add-ons themselves are covered in our Zoho CRM pricing guide.

Zoho's documentation lists these figures, Enterprise first and Ultimate second:

• Conditional rules per screen: 10 on Enterprise, 20 on Ultimate.
• Conditions per criteria in a conditional rule: 25 on both.
• Fields a single rule can show: 15 on Enterprise, 25 on Ultimate.
• Subforms a rule can show: 2 on Enterprise, 5 on Ultimate.
• Text components a rule can show: 5 on Enterprise, 15 on Ultimate.

Some limits apply per screen whatever the plan. A screen takes up to 10 sections, 10 buttons, five text components, one widget and one query component.

In practice, these ceilings are a design signal. If one screen needs more than 10 conditional rules on Enterprise, the screen is probably doing two jobs. Splitting it usually reads better for the user than upgrading the plan to fit more logic on one page.

Test every Zoho CRM wizard in Sandbox with the people who will use it, before it reaches production. Zoho confirms that Wizards are supported in Sandbox. You can therefore build, break and rebuild without touching live records. Ask two or three regular users to enter real enquiries from the past week, and watch where they hesitate.

Check access next. Zoho's documentation notes that layout permission overrides wizard access permission. A user who cannot see the underlying layout will not get the wizard either, whatever you set on the wizard itself.

A Zoho community thread reports several behaviours worth testing directly. The user said they saw them in two different Zoho CRM accounts:

• Lookup search in a wizard did not find a record by words from the middle of its name.
• After a record was created through a wizard, layout rules applied in view mode but not in edit mode.
• A subform hidden by a layout rule appeared as mandatory when editing, which blocked saving.

These are user reports, not confirmed product behaviour, and they may have changed since. Each one takes minutes to test in Sandbox. Build a short test script that covers creating, editing and searching, and run it again after every change.

The main rollout risks of a Zoho CRM wizard concern drafts, approvals and moving the configuration between accounts. None of them shows up in a quick demo, so plan for each one explicitly.

Drafts disappear with the wizard

Drafts have no time limit and stay until someone deletes them. Deactivating a wizard removes all its draft records. Deleting a wizard removes the configuration and any associated drafts, and it cannot be reverted. Before you switch a wizard off, ask users to finish or save their drafts.

Approvals wait for the save

A draft record cannot enter an approval process. The record is only added to the module, and only enters approval, after it has been submitted or saved. If your team relies on approvals, make sure the save button is easy to reach and clearly labelled.

Copy customisation changes buttons

Custom buttons are not supported in copy customisation. When the configuration is copied, a custom save button becomes a regular button. Other custom buttons are removed, which disables the wizard. After any copy, open the wizard in the target account and rebuild its buttons before users see it.

For companies operating in several EU member states, Zoho CRM Wizards mainly help with one long form serving teams whose processes differ. A wizard can span up to 4 layouts. One wizard can therefore guide users through country or business-unit layouts without separate training for each. Conditional rules keep the country-specific fields out of sight for everyone else.

Data protection deserves a specific check. Wizard drafts often hold names, emails and phone numbers, and Zoho keeps drafts until they are deleted. If your GDPR retention policy sets how long you keep personal data, include wizard drafts in that review. Otherwise abandoned entries can sit in the Drafts section indefinitely.

Text components are useful here too. A text component can carry instructions or a disclaimer on the screen where personal data is collected. One example is a short note your data protection lead has approved on how the data will be used. Which wording you need depends on your own legal advice, not on the tool.

Finally, remember that portal users cannot yet access Wizards. If customers or partners in other countries enter data through a portal, that route needs its own guided design.

The practical way to start with Zoho CRM Wizards is to pilot one wizard on the layout that causes the most bad records. Take these steps in order:

1. Pick the layout and check it against the fit table in this guide.
2. List every layout rule and mandatory field on it.
3. Sketch the screens on paper, cutting at each change of task and each branch.
4. Build the wizard in Sandbox and rebuild the layout rules as conditional rules.
5. Run the test script with two or three real users, then fix what they stumble on.
6. Agree how drafts will be cleaned up before you activate it in production.

Keep the first wizard small. Four or five screens on one module will teach your team more than an ambitious design across several layouts. Once users trust the first one, the same method applies to the next layout.

If the layouts themselves need rethinking, the work goes beyond a single wizard. You may also want help with the rest of your setup. Our Zoho CRM implementation service for European companies covers layouts, rules and rollout together.

• Zoho CRM Help: FAQs on Wizards
• Zoho CRM Help: Creating Wizards
• Zoho Community: Wizards, search and conditional layouts bugs
• Zoho CRM: Wizards, een slimmere manier om klantgegevens vast te leggen