Building a kiosk is the easy part. The skill is knowing which process to build one for. This article, the third in our Kiosk Studio series, sets out three patterns that reveal good candidates, and how to build your first kiosk, including by describing it to Zia. It is based on Zoho's Zoholics 2026 eBook, rewritten in our words, with our own advice marked.

Three patterns that point to a kiosk

Legwork is almost universal, so you probably already have some ideas. These patterns help you find more.

1. Somebody keeps going to get something

A person has to leave the record they are working on to fetch information from somewhere else before they can act. Examples from Zoho:

• A rep preparing a renewal, who checks the billing system for actual spend and the support desk for open tickets before dialling.
• A support agent who checks a vendor portal before raising a claim.
• A credit analyst who looks at the CRM and other systems before scoring an application.
• A recruiter who opens a candidate record and the assessment tool, in separate browser tabs, for scores.

2. Somebody has to know what comes next

When people must memorise a complicated sequence to know the next step, the process breaks. You can see it when they pause often, double-check data repeatedly, or queue at a colleague's desk for answers. Look for places where the path depends on an earlier answer:

• A discount that needs one approval or two, depending on its size and term.
• Onboarding steps that apply to the enterprise plan and not the standard one.
• A return that needs an inspection first in some cases and can be refunded immediately in others.
• Which of eleven document types a particular applicant has to provide.

3. Somebody has to make the updates and send the emails

When reps save status updates, log entries, and handoff notes for the end of the day, details fade and steps get skipped, and reports stop reflecting reality. Look for decisions that need manual updates in several places:

• A won deal that has to reach the finance handoff, the onboarding queue, and the forecast note.
• An escalation that has to reach the account owner, the customer success lead, and the ticket.
• A price exception someone has to remember to record for audit.
• A change of address that lives in three systems but is only updated in one.

A bonus effect: Zoho points out that moving a process into a kiosk lets you cover more complex processes than before. The number of steps, the options at each step, and the updates afterwards were limited by what a person could remember, and a kiosk removes that limit while still executing the process the same way each time.

Three ways to start

Zoho says you do not have to pick one route. Most teams end up with a couple of small retrieval kiosks, one full end-to-end process, and an agent inside whichever flow matters most.

Building your first kiosk with Zia

1. Describe the process in plain language to Zia, and it builds a first version.
2. Walk the generated flow. Zoho is clear that reviewing it is where the real work is. Check that the questions come in the order your process intends, add what is missing, and correct what is wrong.
3. Ask Zia to make changes. Describe a change to an existing kiosk and Zia will make it.

Our advice for a first build

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

• Choose a process that is frequent, annoying, and leaves a record, so you can measure the improvement. See Measuring Whether a Kiosk Worked in Zoho CRM.
• Have the person who actually runs the process review it, not only the administrator who built it. They will spot the missing exception first.
• Test with dummy records in a sandbox before pointing a kiosk at live data, especially if it writes to other systems or sends emails.
• Think about where it appears before you launch. See Where to Place a Kiosk in Zoho CRM.