Wizards in Zoho CRM split one long record form into ordered steps
Wizards for guided data entry in Zoho CRM solve a common problem. A long record layout gets saved half-filled. A wizard breaks the form into short screens that staff complete in a set order. Each screen asks for one group of details. The record is saved only at the end.
A wizard in Zoho CRM is a guided create screen. It presents the fields of a module's layout as a sequence of steps instead of one long page. A layout is the set of fields and sections a user sees when they create or edit a record. A module is a section of the CRM that holds one type of record, such as deals or contacts.
The value of a wizard is order and completeness. A salesperson who opens a 60-field page tends to fill the fields they know. They skip the rest. A wizard puts the essential questions first and makes the person deal with each group before moving on. It also hides groups that do not apply to the case in hand.
This guide covers when a wizard is worth building and how to check which modules can use one. It includes a worked example for the Deals module and a checklist of setup choices. It also lists the pitfalls that still let incomplete records through. If you are new to the building blocks, start with our beginner's guide to Zoho CRM.
When a wizard is worth building, and when a plain layout is enough
A wizard is worth building when a record is long, the order of entry matters and different people fill it in. If a record has a dozen fields that everyone understands, a well-arranged layout does the job. Adding steps then only adds clicks.
Look for these signs that a layout has outgrown a single page:
- Reports show the same fields empty on a large share of records.
- Staff ask colleagues which section to fill first.
- Some fields only make sense after an earlier answer, such as a contract type.
- New starters create records that need cleaning by someone senior.
- Service and sales teams share one module but need different questions.
A wizard does not replace good field design. Mandatory fields, picklists and sensible defaults still do most of the work of keeping data clean. A picklist is a field where the user chooses from a fixed list rather than typing free text. The wizard adds sequence and focus on top of that design. It does not stand in for it.
Before you build, tidy the layout itself. Remove fields nobody uses and merge duplicates. Rename labels that mean different things to different teams. Our post on how to customise your CRM covers that groundwork. A wizard built on a cluttered layout simply spreads the clutter across more screens.
Check that your module offers a wizard before you design one
Confirm that the module you want to guide appears in the wizard builder's list in your own Zoho CRM account before you design anything. A wizard plan built for a module the builder does not offer is wasted work. The check takes a few minutes and saves a redesign later.
Do this check early for two reasons. Teams often ask for a wizard on the record that causes them the most trouble, and that record may sit in a module that behaves differently. Activities such as calls, meetings and tasks are also short records by nature. An ordinary layout usually serves them better than a sequence of steps.
Two practical lessons follow from this.
- Do not promise a team a wizard for a module until you have seen that module in the wizard builder's list in your own account.
- Keep short, frequent records such as activities on ordinary layouts.
If the record you want to guide sits in a module the builder does not offer, you have other options. You can tighten the ordinary layout and make key fields mandatory. You can also collect the information earlier in a module where the builder does offer a wizard, and carry it forward. A final option is to capture it outside the CRM in a form, covered later in this guide.
Designing wizard steps: order them the way staff gather information
Order the wizard's steps in the sequence your staff actually learn things, not the sequence fields appear in the database. A salesperson on a first call learns who the customer is before they learn the budget. A service agent learns the fault before the warranty details. The steps should follow that path.
At Svennis we sketch the steps on paper with two or three of the people who will use the wizard before anyone opens the builder. The order an administrator finds logical is rarely the order a salesperson collects answers in during a call.
Rules of thumb for each step
- One step, one theme: customer, opportunity, requirements, commercial terms.
- Put mandatory fields in the earliest step where the user can realistically know them.
- Keep each step short enough to fit one screen without scrolling.
- Use the step title to say what the step is for, such as "Who is the customer".
- End with a review step so the user can check everything before saving.
Where conditional logic helps
Some groups of fields only matter for certain answers. A renewal needs the previous contract reference, and a new business deal does not. Show such groups only when the earlier answer calls for them. Every field a user sees should be one they are expected to fill.
Worked example: a four-step wizard for new deals
The example below shows a wizard for the Deals module of a business-to-business firm. It is an illustration you can adapt. Your field names and stages will differ. The aim is that every new deal arrives with a customer, a value, a close date and a stated need.
Step 1: Customer
Ask for Account Name and Contact Name first, both looked up from existing records. Looking up rather than typing stops the same company appearing three times under slightly different spellings. Make both mandatory here, because the salesperson always knows who they are talking to.
Step 2: Opportunity
Ask for Deal Name, Stage, Amount and Closing Date. Use a naming rule in the field's help text, such as company name plus product. That keeps deal lists readable. Stage should be a picklist, never free text.
Step 3: Requirements
Ask for the need in the customer's words, the product interest and the deal type. If the deal type is a renewal, reveal the fields for the existing contract. If it is new business, reveal the lead source instead.
Step 4: Review
Show a summary of the main answers and let the user go back to any step before saving. Saving at the end, rather than after each step, means an abandoned wizard leaves no half-built record behind.
Test the result with one salesperson creating five real deals. Watch where they hesitate. Hesitation usually means a step title is unclear or a field is in the wrong step.
Setup choices checklist: what to decide before you build a wizard
Most wizard problems come from decisions nobody made explicitly. The table below lists the choices to settle before building, the question behind each and the pitfall when it is skipped.
| Choice | Question to answer | Pitfall if skipped |
|---|---|---|
| Module | Does the module appear in the wizard builder's list? | Designing for a module that cannot have a wizard |
| Layout | Which layout will the wizard draw its fields from? | Clutter from an untidied layout spread across every step |
| Users | Which teams or profiles should see this wizard? | Service staff forced through sales questions |
| Step order | In what order do staff actually learn the answers? | Mandatory fields placed before users can know them |
| Mandatory fields | Which fields must never be empty? | Too many, so staff type placeholder text to get through |
| Conditional groups | Which fields depend on an earlier answer? | Irrelevant questions left visible and skipped |
| Other entry routes | How else do records arrive: import, integration, mobile? | Clean records from the wizard, messy ones from everywhere else |
| Follow-on process | What happens after saving, such as an approval? | A complete record that then waits with nobody alerted |
On the last row, an approval process in Zoho CRM is a process automation tool that automates approvals in your organisation. A wizard that collects discount or contract terms often pairs well with one. The wizard makes sure the approver receives complete information to decide on.
Common wizard pitfalls: records entered outside the wizard, subforms and too many mandatory fields
The biggest pitfall is assuming a wizard cleans all your data. A wizard guides the person filling it in. Records created by other routes do not pass through it. Imports, integrations and automations each need their own checks. If you load data in bulk, follow the steps in importing data into Zoho CRM without breaking your records so imported records meet the same standard.
Subforms need their own plan
A subform is a table of repeating rows inside a record, such as line items or contacts on a project. Decide before you build which wizard step holds each subform and which rows are essential. If row order matters to a later report or document, store the order in a field of its own rather than relying on how rows appear on screen. Test subform entry with real data, because a long table of rows is tiring to fill in on one screen.
Too many mandatory fields
Making every field mandatory feels safe but backfires. Staff who cannot know an answer yet will type a dot or "TBC" to get past the step. Keep mandatory fields to the few that must never be empty. Report on the rest instead.
Wizard-style forms for people outside the CRM: Zoho Forms
Use a web form rather than a CRM wizard when the person entering data is not a CRM user. Examples are a customer filling in an onboarding questionnaire or a supplier registering their details. A CRM wizard guides your own staff. A public form guides everyone else, and Zoho Forms is Zoho's product for building one.
Plan a public form with the same discipline as an internal wizard. Split a long questionnaire into short pages, with one theme on each page and the essential questions first. Show a page only when an earlier answer calls for it. Every question a respondent sees should be one they are expected to answer.
Check what styling and logic your form tool supports against Zoho's own help pages before you promise a design to a customer-facing team. Community answers about what a form tool can or cannot do are useful leads. They are not product documentation, and they date quickly.
When form entries flow into the CRM, map each form field to a CRM field before launch. Test with a handful of real submissions and open the records they create. That way the record arrives as complete as one entered through your internal wizard.
What wizards mean for a UK company's CRM data
For a UK company, a wizard is a simple way to make sure the details your other systems depend on are captured every time. Finance, marketing and support all read from the same CRM records. A missing value at entry becomes a manual fix later, often for someone in another team.
Think about which details a UK business customer record needs before it is useful downstream. Typical candidates are the registered company name, the company registration number, the VAT number where one exists and a full postal address with postcode. Group these into one wizard step for business accounts. Hide that step for private individuals.
Wizards also help teams that work apart. Many UK firms have salespeople on the road, service staff in the field and an office team at a desk. A wizard gives all of them the same sequence of questions. A record created by one person reads the same as a record created by another, whoever picks it up next.
Consistency matters most when people leave or change roles. Records that follow one structure are easier to reassign, report on and hand over. Our guides on territory management in Zoho CRM and offboarding a salesperson in Zoho CRM both depend on records that were entered completely in the first place.
Next steps: build one wizard, test it and measure empty fields
Start with one wizard for the module that causes the most cleaning work, usually Deals or Leads. Do not build wizards for every module at once. One wizard that staff adopt teaches you more than five they work around.
- Run a report of the fields most often left empty in that module, so you have a baseline.
- Check that the module appears in the wizard builder's list in your account.
- Tidy the layout, then sketch the steps with two or three of the people who will use them.
- Build the wizard and have one user create real records while you watch.
- Adjust step titles and field placement, then roll the wizard out to the team.
- Rerun the empty-fields report after a few weeks and compare it with the baseline.
If something behaves unexpectedly, Zoho's support portal, Zoho Cares, lets you search the knowledge base, ask the community or submit a request. For wider layout and automation changes, read our intermediate guide to Zoho CRM. If you would like help planning wizards around your sales and service process, see our Zoho CRM implementation and consulting services.