Where to Place a Kiosk in Zoho CRM

A tool that nobody remembers to open is a tool that does not get used. With Kiosk Studio, what a kiosk does and where it appears are two separate decisions, and getting the second one right often decides whether the first one pays off. This is the fourth article in our Kiosk Studio series, based on Zoho's Zoholics 2026 eBook, rewritten in our words, with our own advice marked.

The flow and its placement are independent

Most CRM features are tied to a place. A blueprint lives on a record because it follows that record's state. The data migration tool lives on the Setup page, and the mass email option lives on the list view. A kiosk is not tied to any location. The same flow, unchanged, can sit on a record page, a list view, or a home page, and can be started by a change to a single field, by a blueprint transition, from a setup page, from the mobile app, or in a portal where the person running it is your customer and not your employee.

Zoho's examples include the same repair-request kiosk embedded on the home page of the web app, and launched from a button in the mobile app. The best starting point can therefore be anywhere in the CRM, depending on what the business needs.

How insistent can a placement be?

Every kiosk asks two things of a person: remember it exists, and open it. Zoho describes a spectrum from easy to ignore to impossible to avoid:

Where it sits	What the person has to do	Can they carry on without it?
A command or keyboard shortcut	Know it exists, and call for it.	Yes
A setup page	Go looking for it.	Yes
A button on a record or list view	Notice it when they are in those places.	Yes
A home page or canvas home view	Notice it before picking a task.	Yes
Embedded on the record itself	Notice it. The first screen is already open.	Yes
Opened by a script when something happens	Nothing. An event triggers it.	Yes
Inside a blueprint transition	Nothing. Clicking the transition launches it.	No

Place it where the work already happens

Zoho's guidance is simple. A loan review queue belongs on the home page, because that is where officers start their day. A button for invoiced items belongs beside each invoice, because that is where someone is already looking. Good placement lowers the effort of remembering and of opening. The best placement removes both, so the kiosk is simply there when it is needed.

Compulsion has to be earned

Zoho's advice is to make a kiosk compulsory only once it is already the easiest way to do the job. Before that, you are adding a step for someone who is already stretched. It distinguishes between a demand that replaces work and one that adds to it. A required field sits on top of everything a rep already does. A well-built kiosk takes over the searching and clicking the rep was doing anyway, and leaves only the decisions.

Start with a button.
Watch whether people use it when nobody is making them. If they do, that is your evidence.
Then move it into a blueprint transition, without changing the flow at all.
If they do not use it, the kiosk is not yet faster or more convenient than what it replaced, and making it mandatory would do harm.

Our advice

This section is our own advice, not Zoho's.

Check who can see and run each kiosk. Zoho's eBook does not describe permissions for kiosks, so confirm in a test account which profiles can use a kiosk, especially one placed on a home page or in a portal.
Be careful with customer-facing placement. A kiosk in a portal, where your customer runs it, can read and write data, so test what it exposes before you open it up. Take particular care with personal data.
Record when a kiosk is moved into a blueprint transition, and tell the team beforehand, because it changes the work from optional to unavoidable.
Use the measurement method in the next article to decide when to move from a button to a compulsory step: Measuring Whether a Kiosk Worked in Zoho CRM.